Skip to content
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

Closed
theunrepentantgeek opened this issue Feb 27, 2024 · 3 comments · Fixed by #4202
Closed

Include system affinity for when ASO runs on AKS #3828

theunrepentantgeek opened this issue Feb 27, 2024 · 3 comments · Fixed by #4202
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@theunrepentantgeek
Copy link
Member

Describe the improvement

A suggestion made via email:

My suggestion to improve ASO would be to include the following node affinity block that would target system nodepools on any AKS cluster:

affinity:
    nodeAffinity:
        requiredDuringSchedulingIgnoredDuringExecution:
          nodeSelectorTerms:
          - matchExpressions:
            - key: kubernetes.azure.com/mode
              operator: In
              values:
                - system

According to @matthchr we shouldn't use required because it ASO is supported on non AKS clusters, but there's a preferredDuringSchedulingIgnoredDuringExecution we could use too.

@matthchr
Copy link
Member

matthchr commented Mar 4, 2024

What do we have set for mem/cpu requirements - are they too low?

@matthchr
Copy link
Member

matthchr commented Mar 4, 2024

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.

@theunrepentantgeek theunrepentantgeek added the documentation Improvements or additions to documentation label Aug 19, 2024
@theunrepentantgeek
Copy link
Member Author

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.

matthchr added a commit to matthchr/azure-service-operator that referenced this issue Aug 20, 2024
- 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.
@matthchr matthchr mentioned this issue Aug 20, 2024
3 tasks
matthchr added a commit to matthchr/azure-service-operator that referenced this issue Aug 21, 2024
- 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.
matthchr added a commit to matthchr/azure-service-operator that referenced this issue Aug 21, 2024
- 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.
github-merge-queue bot pushed a commit that referenced this issue Aug 22, 2024
- Add AKS installation best practices, fixes #3828.
- Add problem diagnostics for Argo Helm installation issues, fixes
  #4184.
- Add FAQ entry around data output from one resource being input to the
  next.
@github-project-automation github-project-automation bot moved this from Backlog to Recently Completed in Azure Service Operator Roadmap Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Development

Successfully merging a pull request may close this issue.

2 participants