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

Allow Multiple Installations of the Tetragon Helm Chart #1399

Closed
2 tasks done
ashishkurmi opened this issue Aug 28, 2023 · 0 comments · Fixed by #1400
Closed
2 tasks done

Allow Multiple Installations of the Tetragon Helm Chart #1399

ashishkurmi opened this issue Aug 28, 2023 · 0 comments · Fixed by #1400
Labels
kind/enhancement This improves or streamlines existing functionality

Comments

@ashishkurmi
Copy link
Contributor

ashishkurmi commented Aug 28, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem?

In a heterogeneous Kubernetes environment, one may want to have different Tetragon configurations (e.g., different tetragon.extraArgs Helm parameter for different node sizes) for different node groups. The current Helm chart can only be installed once as it creates several Kubernetes resources such as cluster roles based on "Charts.Name".

Describe the feature you would like

One should be able to install the Tetragon Helm chart multiple times within the same cluster. By utilizing nodeSelectors, tolerations, and affinity, users can establish mutually exclusive groups of Kubernetes nodes. This enables multiple deployments of Tetragon to encompass all relevant nodes in the cluster

Describe your proposed solution

#1400 describes a potential fix.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@ashishkurmi ashishkurmi added the kind/enhancement This improves or streamlines existing functionality label Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement This improves or streamlines existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant