-
Notifications
You must be signed in to change notification settings - Fork 208
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 mode: Add external workloads test coverage #1640
Conversation
it's failing in helm mode because cilium-cli/clustermesh/certs.go Line 139 in 64bd65c
need to look into whether this is configurable via helm 👀 |
4683483
to
537ee2b
Compare
✅ https://github.com/cilium/cilium-cli/actions/runs/5009483637/jobs/8978707657?pr=1640 removing the temporary commit and marking it ready for review |
fab997f
to
7c301c3
Compare
7c301c3
to
3204aec
Compare
✅ successful run: https://github.com/cilium/cilium-cli/actions/runs/5018586743?pr=1640 removing the temporary commit. |
3204aec
to
978287c
Compare
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.
/lgtm
Add --enable-external-workloads flag to "clustermesh enable" command to set externalWorkloads.enabled to true. With this Helm value set to true, clustermesh-apiserver-client-cert secret gets created. This certificate is used by external workloads. The certificate name is clustermesh-apiserver-external-workload-cert in classic mode for some reason. Add getExternalWorkloadCertName() function that returns the correct cert name depending on which mode the CLI is in. Co-authored-by: Marco Iorio <[email protected]> Signed-off-by: Michi Mutsuzaki <[email protected]>
Ref: #1625 Signed-off-by: Michi Mutsuzaki <[email protected]>
430139b
to
3f70b4e
Compare
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 updates
Ref: #1625