-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Bug 1931974: Prefer IPv6 hostIP on bootstrap IPv6 deployments #4756
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
|
@celebdor: This pull request references Bugzilla bug 1931974, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (vvoronko@redhat.com), skipping review request. DetailsIn response to this:
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. |
|
still need to test it out |
|
@staebler that makes it simpler, thanks, It renders well |
|
After rebase: |
|
Moved the kubelet.sh to only be rendered with the ipv6 check on the batemetal platform. Still rendering well: |
|
/retest |
|
/lgtm |
|
I just tested it, it seems to fix the problem |
|
/retest |
I don't think it is a good idea to have a completely separate Note that the code creating the bootstrap ignition config adds both the regular kubelet.sh file and the baremetal-specific kubelet.sh file. You are getting the bootstrap-specific one only because the code happens to add that one second: That is not guaranteed. |
|
/hold for concerns over duplicate kubelet.sh file |
9304c8e to
ba84d3a
Compare
|
Correctly rendered with the new approach: |
pkg/types/installconfig.go
Outdated
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.
Keep this function in pkg/asset/ignition/bootstrap for now since that is the only place where it is used.
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.
Would it make sense to make the name of this variable more specific to its use rather than specific to its source?
| {{- if .APIVIPIPv6 }} | |
| {{- if .UseIPv6ForNodeIP }} |
|
Applied the suggestions. Still renders right: |
|
/retest |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: staebler The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
\unhold as e2e-metal-ipi-ovn-ipv6 passes |
|
/unhold |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@celebdor: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
@celebdor: All pull requests linked via external trackers have merged: Bugzilla bug 1931974 has been moved to the MODIFIED state. DetailsIn response to this:
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. |
|
@sadasu: #4756 failed to apply on top of branch "release-4.7": DetailsIn response to this:
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. |
|
@sadasu: #4756 failed to apply on top of branch "release-4.7": DetailsIn response to this:
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. |
This PR addressed issue similar to [1] for the None platform, since API VIP isn't used for None platform, the UseIPv6ForNodeIP parameter should be calculated based on the content of service CIDR. [1] openshift#4756
Kubelet can end up choosing IPv4 addresses as its hostIP, which after:
https://github.com/openshift/cluster-kube-apiserver-operator/pull/1042/files
mean that the kubernetes API service ends up with an endpoint being an
IPv4 address. This breaks the kubernetes API loadbalancer in the
service network and prevent the deployment from succeeding.