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

Feature Request: Add nameOverride Variable to Helm Chart #2951

Open
2 tasks done
Harishpp opened this issue Sep 24, 2024 · 0 comments
Open
2 tasks done

Feature Request: Add nameOverride Variable to Helm Chart #2951

Harishpp opened this issue Sep 24, 2024 · 0 comments
Labels
kind/enhancement This improves or streamlines existing functionality

Comments

@Harishpp
Copy link

Harishpp commented Sep 24, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem?

I am using the Tetragon Helm chart and noticed that there is no nameOverride variable available in the chart's values.yaml file, unlike many other public Helm charts. The nameOverride variable is useful for customizing the name of the Helm release, especially when deploying multiple releases of the same chart in different environments or namespaces.

Describe the feature you would like

Would it be possible to add a nameOverride variable to the values.yaml file to allow more flexibility in release naming? This would make it easier to manage deployments in various environments without affecting other configurations.

Describe your proposed solution

Add a variable nameOverride in values.yaml file and update the template files to name the deployment with the override value from values.yaml

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Harishpp Harishpp added the kind/enhancement This improves or streamlines existing functionality label Sep 24, 2024
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

No branches or pull requests

1 participant