-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 metadata-proxy from GCE Clusters from 1.29+ onwards #15885
Remove metadata-proxy from GCE Clusters from 1.29+ onwards #15885
Conversation
1bbefc9
to
28631f0
Compare
upup/pkg/fi/cloudup/bootstrapchannelbuilder/bootstrapchannelbuilder.go
Outdated
Show resolved
Hide resolved
Changing the PR to remove the feature entirely as discussed during the office hours. GCP deprecated this product a long time ago from GKE and the source code for it isn't around. |
5957e00
to
8f0fcd0
Compare
8f0fcd0
to
712064e
Compare
The Office Hours decision was to remove it as of Kubernetes 1.29. If the Kubernetes version is 1.28 or earlier then it should still be installed. Do we need to add any code to get it removed upon upgrade over the 1.29 boundary? |
712064e
to
3902e91
Compare
Fixed |
7f0e21c
to
7ee84a7
Compare
/test pull-kops-e2e-k8s-gce-ci |
Verified the changes in the |
/retest |
/retest |
These jobs should have focus_regex to Conformance |
We can debate this at the next kOps Office Hours. 😆 |
/lgtm |
/test pull-kops-e2e-k8s-gce-ci |
@upodroid: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
7ee84a7
to
20e7a5a
Compare
Fixed the docs |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman 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 |
/cc @justinsb
More details for why: https://kubernetes.slack.com/archives/C8MKE2G5P/p1694044152804789