-
Notifications
You must be signed in to change notification settings - Fork 3k
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
daemon: ignore CILIUM_CUSTOM_CNI_CONF when writing cni configuration #23743
Conversation
This file was overly-cautious when mimicking cni-install.sh's behavior. It turns out we want to be able to disable cni-install.sh but still have the daemon write the configuration file. This preserves existing behavior in 1.12. Thus, we need to remove the bit that bails out if the environment variable is set. Fixes: 12b7b11 Signed-off-by: Casey Callendrello <cdc@isovalent.com>
/test Job 'Cilium-PR-K8s-1.25-kernel-4.19' failed: Click to show.Test Name
Failure Output
If it is a flake and a GitHub issue doesn't already exist to track it, comment |
Test failure seems like a flake; Cilium was installed correctly but Kafka failed to go ready. One test failed, Cilium was successfully installed many times over the course of this CI run.
|
/test-1.25-4.19 |
All green except ci-verifier. (is that supposed to run with /test? |
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 🚀
/ci-verifier |
This file was overly-cautious when mimicking cni-install.sh's behavior. It turns out we want to be able to disable cni-install.sh but still have the daemon write the configuration file. This preserves existing behavior in 1.12.
Thus, we need to remove the bit that bails out if the environment variable is set.
Fixes: 12b7b11
Signed-off-by: Casey Callendrello cdc@isovalent.com