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

fix(shield): add default host shield tolerations and affinity #1968

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

aroberts87
Copy link
Collaborator

What this PR does / why we need it:

The Shield chart was not defining a default set of node affinity and toleration settings which resulted in the Host Shield not being installed on expected nodes.

Checklist

  • Title of the PR starts with type and scope, (e.g. feat(agent,node-analyzer,sysdig-deploy):)
  • Chart Version bumped for the respective charts
  • Check GithubAction checks (like lint) to avoid merge-check stoppers
  • All test files are added in the tests folder of their respective chart and have a "_test" suffix

@aroberts87 aroberts87 self-assigned this Oct 7, 2024
@aroberts87 aroberts87 requested a review from a team as a code owner October 7, 2024 18:32
{{- with $affinity -}}
{{- . | toYaml -}}
{{- end -}}
{{- else -}}
nodeAffinity:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why don't we set this as default in the values for host.affinity?

@@ -206,7 +206,23 @@ host:
# The node selector for the host shield
node_selector: {}
# The tolerations for the host shield
tolerations: []
tolerations:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
tolerations:
tolerations: # +doc-gen:break

And re-run make docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants