-
Notifications
You must be signed in to change notification settings - Fork 545
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
helm: add imagePullSecrets for helm charts #3906
Conversation
Thanks! Could you please add support for NFS as well? Also force-push your updated/rebased commit and include your |
260cbd0
to
118c456
Compare
@nixpanic Well, but it seems that it does not provide a helm chart for NFS? Theres only |
Ah, indeed, that seems to be missing 😞 |
@@ -37,6 +37,10 @@ spec: | |||
# to use e.g. Rook orchestrated cluster, and mons' FQDN is | |||
# resolved through k8s service, set dns policy to cluster first | |||
dnsPolicy: ClusterFirstWithHostNet | |||
{{- if .Values.nodeplugin.imagePullSecrets }} | |||
imagePullSecrets: | |||
{{ toYaml .Values.nodeplugin.imagePullSecrets | indent 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 show in an example what value you would pass? I would expect something like this instead:
- name: {{ .Values.nodeplugin.imagePullSecrets }}
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.
Here you should provide an array like:
imagePullSecrets:
- name: my-secret-a
- name: my-secret-b
This part in fact is copied from csi-driver-nfs:
And It is a recommended way rather than:
imagePullSecrets:
- name: {{ .Values.nodeplugin.imagePullSecret }}
In this way you can not provide multiple secrets. And maybe there are other fields (no just name
only).
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.
ok, thanks for the clarification!
@fungaren can you please fix linter errors https://github.com/ceph/ceph-csi/actions/runs/5267388978/jobs/9526493600?pr=3906 and https://github.com/ceph/ceph-csi/pull/3906/checks?check_run_id=14256026729. you can follow https://github.com/ceph/ceph-csi/blob/devel/docs/development-guide.md#code-contribution-workflow to sign the commit. |
I think the failure is because there is no empty line between the subject of the commit, and the Signed-off-by line. |
118c456
to
667beb6
Compare
@megifyio queue |
@Mergifyio queue |
🛑 The pull request has been removed from the queuePull request #3906 has been dequeued due to failing checks or checks timeout. You can take a look at In case of a failure due to a flaky test, you should first retrigger the CI. |
Hi @fungaren, could you login (with your GitHub account) on the Mergify Dashboard? It seems that it is required for some reason before Mergify wants to run tests on this PR. https://dashboard.mergify.com/github/ceph/repo/ceph-csi/queues?branch=devel&pull=3906&queues=default Once done, leave a comment |
@fungaren Can you just rebase on top of devel now |
Currently the Helm chart does not contain a imagePullSecrets option when you are using private container registry, this is very inconvenient. This PR add this option for both CephFS and RBD. Signed-off-by: Garen Fang <fungaren@qq.com>
667beb6
to
c00b48a
Compare
Pull request has been modified.
@Mergifyio queue |
/test ci/centos/k8s-e2e-external-storage/1.24 |
/test ci/centos/k8s-e2e-external-storage/1.25 |
/test ci/centos/k8s-e2e-external-storage/1.26 |
/test ci/centos/k8s-e2e-external-storage/1.27 |
/test ci/centos/mini-e2e-helm/k8s-1.24 |
/test ci/centos/mini-e2e-helm/k8s-1.25 |
/test ci/centos/mini-e2e-helm/k8s-1.26 |
/test ci/centos/mini-e2e-helm/k8s-1.27 |
/test ci/centos/mini-e2e/k8s-1.24 |
/test ci/centos/mini-e2e/k8s-1.25 |
/test ci/centos/mini-e2e/k8s-1.26 |
/test ci/centos/mini-e2e/k8s-1.27 |
/test ci/centos/upgrade-tests-cephfs |
/test ci/centos/upgrade-tests-rbd |
Thanks @fungaren , I think Mergify is finally also ready to accept+merge this PR. |
/retest ci/centos/mini-e2e-helm/k8s-1.26 |
/retest ci/centos/upgrade-tests-rbd |
/retest ci/centos/mini-e2e/k8s-1.27 |
/retest ci/centos/upgrade-tests-cephfs |
@Mergifyio requeue |
☑️ This pull request is already queued |
Describe what this PR does
Currently the Helm chart does not contain a
imagePullSecrets
option when you are using private container registry, this is very inconvenient. This PR add this option for both CephFS and RBD.Provide some context for the reviewer
For example, csi-driver-nfs already support this:
https://github.com/kubernetes-csi/csi-driver-nfs/blob/862cb036e3f0d7c3fe28d2b127a6f96335b15309/charts/v4.3.0/csi-driver-nfs/values.yaml#L127-L131
https://github.com/kubernetes-csi/csi-driver-nfs/blob/862cb036e3f0d7c3fe28d2b127a6f96335b15309/charts/v4.3.0/csi-driver-nfs/templates/csi-nfs-controller.yaml#L20-L23
Is there anything that requires special attention
To test this feature, you can use
helm template
andkubectl apply --dry-run
to examine the YAML result and the syntax. For example:Do you have any questions?
Is the change backward compatible?
Are there concerns around backward compatibility?
Provide any external context for the change, if any.
For example:
Related issues
Mention any github issues relevant to this PR. Adding below line
will help to auto close the issue once the PR is merged.
Fixes: #issue_number
Future concerns
List items that are not part of the PR and do not impact it's
functionality, but are work items that can be taken up subsequently.
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>
: retest the<job-name>
after unrelatedfailure (please report the failure too!)
/retest all
: run this in case the CentOS CI failed to start/report any testprogress or results