-
Notifications
You must be signed in to change notification settings - Fork 209
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
dockerfile: include CA certificates #1879
Conversation
Busybox does not include CA certificates by default, which causes https requests to fail during certificate verification. For instance, the Cilium CLI fails to retrieve the hem chart with the following error: looks like "https://helm.cilium.io" is not a valid chart repository or cannot be reached: Get "https://helm.cilium.io/index.yaml": tls: failed to verify certificate: x509: certificate signed by unknown authority Hence, let's propagate the CA certificates from the builder container. Signed-off-by: Marco Iorio <[email protected]>
Previously, the tunneling mode was specified through an extra config, which caused the CLI to override it with the autodetected value, causing a conflict (as the tunnel option is now deprecated). Let's fix this issue explicitly setting the routingMode (cilium#24561). Signed-off-by: Marco Iorio <[email protected]>
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.
fascinating
Successful run for the external workloads workflow: https://github.com/cilium/cilium-cli/actions/runs/5715701135/job/15485617703?pr=1880 (it needed to be tested separately since this PR is from a fork, and the workflow is run as |
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
Reviews are in, the failure is expected as the fix will take effect only once merged. Marking as ready to merge /cc @michi-covalent 🙏 |
Busybox does not include CA certificates by default, which causes https requests to fail during certificate verification. For instance, the Cilium CLI fails to retrieve the hem chart with the following error:
Hence, let's propagate the CA certificates from the builder container.
Note: this error did not show up previously because the helm charts were vendored inside the CLI binary, hence avoiding the need to contact an external website. The v1.14 one, instead, is not vendored (yet?), hence causing all workflows to fail due to the impossibility of reaching
helm.cilium.io
.Additionally, the second commit fixes the external-workloads workflow, which is currently broken due to a conflict in the configured options.