-
Notifications
You must be signed in to change notification settings - Fork 193
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
azure: fix BYOCNI install with Cilium >= 1.12 #953
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We introduced support for BYOCNI with the `aks-byocni` datapath mode in 2e1d3b5, and properly guarded the previously existing Service Principal creation to only be done when using Azure IPAM (`azure` datapath mode), however we forgot to do the same for the newly-introduced AKS secrets in the Cilium 1.12 Helm chart. This went undetected during the initial implementation as the Helm chart used was either the stable 1.11.5 or the development version 1.11.90 when directly using the Helm chart from upstream `master` branch, in both cases skipping the existing 1.12 check for creating AKS secrets. Now, after the 1.12 branch was properly created and the development version bumped to 1.12.90, this does not work anymore, and explains why the AKS BYOCNI CI in upstream was initially working but then started to fail after the version bump. Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
Before fix (
After fix:
|
aanm
approved these changes
Jul 1, 2022
tklauser
approved these changes
Jul 4, 2022
nbusseneau
force-pushed
the
pr/fix-aks-byocni-with-1-12
branch
from
July 5, 2022 13:54
93f1747
to
2c9d4bf
Compare
nbusseneau
added
the
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
label
Jul 5, 2022
Fixed typos in git commit message, no changes otherwise, marking as |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We introduced support for BYOCNI with the
aks-byocni
datapath mode in 2e1d3b5, and properly guarded the previously existing Service Principal creation to only be done when using Azure IPAM (azure
datapath mode), however we forgot to do the same for the newly-introduced AKS secrets in the Cilium 1.12 Helm chart.This went undetected during the initial implementation as the Helm chart used was either the stable 1.11.5 or the development version 1.11.90 when directly using the Helm chart from upstream
master
branch, in both cases skipping the existing 1.12 check for creating AKS secrets.Now, after the 1.12 branch was properly created and the development version bumped to 1.12.90, this does not work anymore, and explains why the AKS BYOCNI CI in upstream was initially working but then started to fail after the version bump.