-
Notifications
You must be signed in to change notification settings - Fork 430
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
docs: adding crucial informations regarding Azure CNI usage with CAPZ #4238
Conversation
Welcome @MadJlzz! |
Hi @MadJlzz. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@MadJlzz do we still need to document this since kubernetes-sigs/image-builder#1090 merged? That should mean all recently published CAPZ reference images already have this |
From what I understood ; yes, the change is now included when using image-builder but we are not using it. |
docs/book/src/topics/addons.md
Outdated
|
||
By default, Azure's images are coming with a `cloud-init` configuration that enables automatic network discovery mechanism that interferes with the Azure CNI. | ||
|
||
In fact, it assigns secondary IP Configurations to the host os, which we do not want. The Azure CNI needs those free to allocate them to pod netns's/veth's) |
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.
It assigns secondary IP Configurations to the host OS, which causes problems because the Azure CNI needs those free to allocate them to pod netns's/veth's.
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.
Done!
docs/book/src/topics/addons.md
Outdated
@@ -279,6 +279,22 @@ The following resources need to be updated when using `capi-quickstart.yaml` (th | |||
. | |||
``` | |||
|
|||
### Disable Azure network discovery (if using custom images) | |||
|
|||
By default, Azure's images are coming with a `cloud-init` configuration that enables automatic network discovery mechanism that interferes with the Azure CNI. |
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.
Please more clarity on what is custom image versus what is provided since the fix is baked into the default ones.
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.
Done!
docs/book/src/topics/addons.md
Outdated
@@ -279,6 +279,22 @@ The following resources need to be updated when using `capi-quickstart.yaml` (th | |||
. | |||
``` | |||
|
|||
### Disable Azure network discovery (if using custom images) |
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.
If this block of section (### Disable Azure network discovery (if using custom images)
) is for users not using image-builder to build their custom images (as per your comment #4238 (comment)), would it be better to specify that in the title?
Would you be able to add something like the one below? @MadJlzz
### Disable Azure network discovery (if using custom images without image-builder)
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.
Done!
I am a bit short in time atm, I am gonna tackle all reviews point this week end, after working hours. Sorry about the delay 😅 |
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
@MadJlzz please squash the commits, and thanks!
LGTM label has been added. Git tree hash: c2b188ab456582901a3c65156a363b1b84af7ca7
|
/ok-to-test |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4238 +/- ##
==========================================
- Coverage 60.90% 60.89% -0.02%
==========================================
Files 190 190
Lines 18991 18983 -8
==========================================
- Hits 11567 11559 -8
Misses 6787 6787
Partials 637 637 ☔ View full report in Codecov by Sentry. |
@mboersma done! |
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
/approve
LGTM label has been added. Git tree hash: 7c3bf1165d46e678bfa494aaf3f3527a75f7b9dc
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mboersma The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
latm |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Adding some information regarding the usage of Azure CNI with custom images.