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.

Sign up for GitHub

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

Jump to bottom

[kube-enforcer] Add nodeSelector to Trivy deployment #785

Closed
Toqn opened this issue Oct 10, 2023 · 2 comments · Fixed by #786
Closed

[kube-enforcer] Add nodeSelector to Trivy deployment #785

Toqn opened this issue Oct 10, 2023 · 2 comments · Fixed by #786

Comments

@Toqn
Copy link
Contributor

Toqn commented Oct 10, 2023 •
edited

The Trivy deployment template within the kube-enforcer templates lacks a nodeSelector field. This poses a problem, as we're not able to specify which node the trivy-operator should be scheduled on.

This can be fixed by adding the following:

kube-enforcer/values.yaml

trivy:
  nodeSelector: {}

kube-enforcer/templates/trivy-deployment.yaml

{{- with .Values.trivy.nodeSelector }}
nodeSelector:
    {{ toYaml . | nindent 8 }}
{{- end }}
@Toqn Toqn mentioned this issue Oct 10, 2023
Merged
@Toqn
Copy link
Contributor Author

Toqn commented Oct 12, 2023

Opened PR: #786

@Toqn Toqn changed the title Add nodeSelector to Trivy deployment [kube-enforcer] Add nodeSelector to Trivy deployment Oct 25, 2023
@Toqn
Copy link
Contributor Author

Toqn commented Oct 25, 2023

Rendering the template locally confirmed the nodeSelector being set as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add nodeSelector to trivy operator Toqn/aqua-helm
1 participant
@Toqn