-
Notifications
You must be signed in to change notification settings - Fork 260
Add Cilium on AKS Overlay e2e scenario #1609
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
Conversation
hack/swift/Makefile
Outdated
| --network-plugin azure \ | ||
| --network-plugin-mode overlay \ |
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.
Does this work? I think we will end up with the AKS managed CNS and AzCNI on the nodes.
We were able to use prod AKS clusters for SWIFT because I made sure BYO CNI supported SWIFT from the back-end when a podsubnet was set ("no CNI but SWIFT-capable"). I don't think we have enabled a "no CNI but overlay-capable" mode.
@thatmattlong is BYO+Overlay on something you have considered? Will we need to build an AKS standalone to run Overlay E2Es in, again?
|
Lets hold on to this PR until we have BYO cni overlay support |
|
@camrynl Given @tamilmani1989 's comment above, please mark this as a draft until it's ready to merge. |
* add hack overlay make target and e2e templates * update pipeline.yaml with new overlay stage * use dropgz/overlay-byocni in acn pr and submodule pipeline * name overlay clusters for submodule pipeline * modify dropgz setup * test ipam + overlay * use azilium conflist * add overlay configmap * add deployment of ip-masq-agent to cluster * set flag in ip-masq-agent deployment * update deployment * configmap creation
Reason for Change:
-Adding new target to hack/swift/Makefile to build byocni overlay cluster.
-Creating e2e tests for Cilium on AKS Overlay
Issue Fixed:
Requirements:
Notes: