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 overriding of naming created by the helm chart #40

Open
MaxRink opened this issue Jan 11, 2022 · 2 comments
Open

Allow overriding of naming created by the helm chart #40

MaxRink opened this issue Jan 11, 2022 · 2 comments
Assignees
Labels

Comments

@MaxRink
Copy link
Contributor

MaxRink commented Jan 11, 2022

Currently a lot of resources have hardcoded names.
It would be nice to have naming based upon the release name.
For implementation bitnamis common library and templates are a good place to start with, as they offer functions that automatically handle naming for you

@FabianKramm
Copy link
Member

@MaxRink thanks for the issue! What would be the benefit of making the naming dynamic? Since jspolicy shouldn't be deployed multiple times as it would clash with reconciling the crds I'm not entirely sure what the use case would be for this.

@ghost
Copy link

ghost commented Mar 8, 2022

Many companies have naming conventions already in place with where they put things. It makes streamlining their technical support cost-effective when software can flex to their already established standards.

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

No branches or pull requests

4 participants