Change headless svc name #903
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Change the Headless Service Name to Template-Generated Name
Fix headless svc regexp
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change the Headless Service Name to Template-Generated Name
Overview:
This pull request introduces a modification to the project that updates the naming convention of the Headless Service (SVC). Currently, the Headless Service name is hardcoded using a constant-defined name, which can lead to naming conflicts and limitations in certain scenarios. To address this issue and improve flexibility, this PR proposes changing the Headless Service name to be dynamically generated using a template.
Motivation:
The primary motivation behind this change is to enhance the scalability and maintainability of the project by removing the constraints imposed by a static, constant-defined name. The template-generated name will allow for more dynamic and context-aware naming of the Headless Service, making it easier to manage in various deployment environments and configurations.