-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
Remove deprecated NodeLegacyHostIP #44830
Remove deprecated NodeLegacyHostIP #44830
Conversation
df93f6a
to
7d00e5c
Compare
The changes lgtm. @liggitt could you also take a look? Thanks. |
@NickrenREN why is the PR marked "WIP"? |
@caesarxuchao Sorry. I added 'WIP' at the beginning and forgot to remove it. |
/lgtm |
@k8s-bot kops aws e2e test this |
@smarterclayton This pr needs your approval |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: NickrenREN, liggitt, smarterclayton
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue |
Automatic merge from submit-queue Add NodeInternalIP as a fallback to federation api-server nodeport service Previously NodeLegacyHostIP was used as a fallback (see #41243) but in 1.7 it was removed (#44830) Now clusters where nodes have not set ExternalIP can not be used by kubefed to setup federation. cc @shashidharatd ```release-note kubefed will now configure NodeInternalIP as the federation API server endpoint when NodeExternalIP is unavailable for federation API servers exposed as NodePort services ```
Release note:
ref #44807