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

Add the ability to override names in the helm chart. #232

Merged
merged 5 commits into from
Jul 20, 2022

Conversation

spilchen
Copy link
Collaborator

A new helm chart parameter was added that allows you to control the prefix of all of the k8s objects created by the helm chart. If this is omitted, all of the objects have the name of the chart (verticadb-operator).

For example, to force all objects created by the operator deployment to start with "special" you can use the nameOverride parameter.

helm install vdb-op vertica-charts/verticadb-operator --set nameOverride=special

Matt Spilchen added 3 commits July 17, 2022 08:49
A new helm chart parameter was added (nameOverride) that allows you to control
the prefix of all of the k8s objects created by the helm chart.  If this is
omitted, all of the objects have the name of the chart (verticadb-operator).
@spilchen spilchen requested a review from roypaulin July 17, 2022 22:45
@spilchen spilchen self-assigned this Jul 17, 2022
@@ -21,6 +21,9 @@
# with the default values.
# -------------------------------------------------------------------------------

# To control the name of all of the objects created in the helm chart.
# nameOverride: verticadb-operator
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it mean we are not using it yet?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The override is an optional parm. If you don't set it, then the k8s objects will use the chart name of verticadb-operator. I just a put a comment here as a indication that this parm exists if you want to control the object names.

@@ -118,6 +119,7 @@ func (fc *FlagConfig) setFlagArgs() {
"with the path /debug/pprof. See https://golang.org/pkg/net/http/pprof/ for more info.")
flag.StringVar(&fc.ServiceAccountName, "service-account-name", "verticadb-operator-controller-manager",
"The name of the serviceAccount to use.")
flag.StringVar(&fc.PrefixName, "prefix-name", "", "The common prefix for all objects created during the operator deployment")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know it does not change anything but why not set the default value to "verticadb-operator" as done with ServiceAccountName?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I will set this.

@spilchen spilchen requested a review from roypaulin July 19, 2022 16:36
@spilchen spilchen merged commit eaf2940 into vertica:main Jul 20, 2022
@spilchen spilchen deleted the configmap-name branch July 20, 2022 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants