-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include system affinity for when ASO runs on AKS #3828
Comments
What do we have set for mem/cpu requirements - are they too low? |
We may need a negative assertion rather than positive: "Don't schedule on the user pool", rather than "must schedule on the system pool" and wahtever we do should probably be put in a Helm "if" block. |
We've discussed this internally and we don't think adding an AKS specific affinity is appropriate, given we want ASO to run well on other kinds of cluster. We will add documentation to make this easier to find, and if/when AKS supports ASO as an extension we'll do this by default. |
- Add AKS installation best practices, fixes Azure#3828. - Add problem diagnostics for Argo Helm installation issues, fixes Azure#4184. - Add FAQ entry around data output from one resource being input to the next.
- Add AKS installation best practices, fixes Azure#3828. - Add problem diagnostics for Argo Helm installation issues, fixes Azure#4184. - Add FAQ entry around data output from one resource being input to the next.
- Add AKS installation best practices, fixes Azure#3828. - Add problem diagnostics for Argo Helm installation issues, fixes Azure#4184. - Add FAQ entry around data output from one resource being input to the next.
Describe the improvement
A suggestion made via email:
According to @matthchr we shouldn't use
required
because it ASO is supported on non AKS clusters, but there's apreferredDuringSchedulingIgnoredDuringExecution
we could use too.The text was updated successfully, but these errors were encountered: