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
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
The text was updated successfully, but these errors were encountered:
@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.
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.
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
The text was updated successfully, but these errors were encountered: