You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
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
The text was updated successfully, but these errors were encountered: