-
Notifications
You must be signed in to change notification settings - Fork 116
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
Use global.imagePullSecrets at solr-operator helm chart #338 #343
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution, this would indeed be very helpful for people!
Before merging would you mind adding a Changelog entry here:
https://github.com/apache/solr-operator/blob/main/helm/solr-operator/Chart.yaml#L56
And adding an entry to the helm chart documentation as well?
https://github.com/apache/solr-operator/blob/main/helm/solr-operator/README.md#running-the-solr-operator
@@ -39,6 +39,10 @@ spec: | |||
spec: | |||
securityContext: | |||
runAsNonRoot: true | |||
{{- if .Values.global.imagePullSecrets }} | |||
imagePullSecrets: | |||
{{- toYaml .Values.global.imagePullSecrets | nindent 8 }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you remove the first -
here? We mainly aren't using that with toYaml
s in this file.
I saw a discrepancy between this "imagePullSecrets" and the one at the zookeeper-operator. I was expecting here a list of objects with "name", but the zookeeper-operator takes a list of strings Also, the operator is adding those to the service account, instead of the deployment itself: Which is more in line with your proposal here: @hossman , do you have any preference on where to add the imagePullSecrets? |
Well if you want to share imagePullSecrets here, you can merely use the same serviceAccount that is created by the Zookeeper Operator with the Solr Operator. That way the imagePullSecrets will be available to both through the same serviceAccount. serviceAccount:
create: false
name: operator-account
zookeeper-operator:
install: true
serviceAccount:
create: true
name: operator-account
imagePullSecrets:
- list
- of
- strings Using the above helm values, the zookeeper-operator helm chart will create the serviceAccount with the listed imagePullSecrets. Then the Solr Operator will merely use the same one, named No need to actually use the global imagePullSecrets. |
Hello there. @j-coll are you willing to do proper changes in this PR? I can also create my own PR about this issue. |
@piotrrybicki Please open your own PR. We'd love to support as many globals as possible, to make setup easy for everyone! As for my comment above it would be great if the helm code could detect a list of strings and convert it to a list of objects where necessary. |
Hi, sorry for the silence. Yes, I'll do the required changes |
Same PR as #339, but against main branch