We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This can cause outages if the node goes down
The text was updated successfully, but these errors were encountered:
Hey @sidewinder12s the deployment template actually has the affinity, we just don't have a placeholder in the values.yaml.
https://github.com/anchore/anchore-charts/blob/main/stable/anchore-admission-controller/templates/deployment.yaml#L81C7-L81C32
https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#more-practical-use-cases
You should be able to assign antiAffinity with something like the following in your values.yaml:
affinity: podAntiAffinity: requiredDuringSchedulingIgnoredDuringExecution: - labelSelector: matchExpressions: - key: app operator: In values: - store topologyKey: "kubernetes.io/hostname"
Sorry, something went wrong.
TopologySpreadConstraint is the Kubernetes recommended configuration for this type requirement.
No branches or pull requests
This can cause outages if the node goes down
The text was updated successfully, but these errors were encountered: