-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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 legacy insecure port options from genericapiserver #42835
remove legacy insecure port options from genericapiserver #42835
Conversation
[APPROVALNOTIFIER] This PR is APPROVED The following people have approved this PR: deads2k Needs approval from an approver in each of these OWNERS Files:
We suggest the following people: |
5b2c053
to
a4d2fc1
Compare
/release-note-none |
LGTM 👍 |
@k8s-bot kops aws e2e test this |
a4d2fc1
to
b25aa67
Compare
b25aa67
to
cd29754
Compare
waiting for #43383 to merge before re-tagging. |
Automatic merge from submit-queue (batch tested with PRs 42835, 42974) |
The insecure port has been a source of problems and it will prevent proper aggregation into a cluster, so the genericapiserver has no need for it. In addition, there's no reason for it to be in the main kube-apiserver flow either. This pull removes it from genericapiserver and removes it from the shared kube-apiserver code. It's still wired up in the command, but its no longer possible for someone to mess up and start using in mainline code.
@kubernetes/sig-api-machinery-misc @ncdc