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
Bug 1805445: [release-4.4] baremetal: Explicitly advertise the host IP chosen by kubelet #773
Bug 1805445: [release-4.4] baremetal: Explicitly advertise the host IP chosen by kubelet #773
Conversation
We've updated MCO to ensure IPv6 VIPs are not accidentally used by kubelet. Make use of that value and set it as the address kube-apiserver should advertise. Otherwise, it uses the same broken default behavior that kubelet does and will incorrectly choose IPv6 VIPs, breaking the cluster. The change to specify the correct IP to kubelet is: openshift/machine-config-operator#1444
@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request. In 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. |
/retitle Bug 1805445: [release-4.4] baremetal: Explicitly advertise the host IP chosen by kubelet |
@openshift-cherrypick-robot: This pull request references Bugzilla bug 1805445, which is invalid:
Comment In 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. |
/lgtm |
/bugzilla refresh |
@russellb: This pull request references Bugzilla bug 1805445, which is invalid:
Comment In 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. |
/bugzilla refresh |
@russellb: This pull request references Bugzilla bug 1805445, which is invalid:
Comment In 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. |
/bugzilla refresh |
@russellb: This pull request references Bugzilla bug 1805445, 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. In 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. |
need for ipv6 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, openshift-cherrypick-robot 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 |
/retest Please review the full test history for this PR and help us cut down flakes. |
@openshift-cherrypick-robot: All pull requests linked via external trackers have merged. Bugzilla bug 1805445 has been moved to the MODIFIED state. In 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. |
/cherry-pick release-4.3 |
@russellb: new pull request created: #777 In 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 is an automated cherry-pick of #760
/assign russellb