Add instructions to install Antrea in encap mode in AKS #5901
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
antoninbas
added
kind/documentation
jianjuns
previously approved these changes
Jan 23, 2024
|
|
||
| AKS now officially supports [Bring your own Container Network Interface (BYOCNI)](https://learn.microsoft.com/en-us/azure/aks/use-byo-cni). | ||
| Thanks to this, you can deploy Antrea on EKS in `encap` mode, and you will not | ||
| lose access to any functionality. Check the AKS BYOCNI documentation for |
There was a problem hiding this comment.
any Antrea functionality?
There was a problem hiding this comment.
actually I meant it in a more general way, since when deploying Antrea on EKS in encap mode, K8s API aggregation will stop working for example
luolanzone
reviewed
Jan 23, 2024
AKS has supported a "Bring Your Own CNI" mode for a while now: https://learn.microsoft.com/en-us/azure/aks/use-byo-cni?tabs=azure-cli With this support, Antrea can easily be installed in encap mode in AKS clusters, with no limitation (unlike for EKS where there is no more connectivity from the control-plane to the Nodes). The only requirement is to enable Antrea NodeIPAM. This support relies on the [Konnectivity Service](https://kubernetes.io/docs/tasks/extend-kubernetes/setup-konnectivity/), which is deployed by default in "recent" AKS versions, and guarantees connectivity from the control-plane to the Nodes, regardless of which CNI is used. Fixes antrea-io#5817 Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
antoninbas
force-pushed
the
aks-encap-mode-installation
branch
from
2de3dd4
to
5ead7b4
Compare
luolanzone
approved these changes
Jan 23, 2024
|
/skip-all |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
AKS has supported a "Bring Your Own CNI" mode for a while now: https://learn.microsoft.com/en-us/azure/aks/use-byo-cni?tabs=azure-cli
With this support, Antrea can easily be installed in encap mode in AKS clusters, with no limitation (unlike for EKS where there is no more connectivity from the control-plane to the Nodes). The only requirement is to enable Antrea NodeIPAM.
This support relies on the
Konnectivity Service, which is deployed by default in "recent" AKS versions, and guarantees connectivity from the control-plane to the Nodes, regardless of which CNI is used.
Fixes #5817