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
there is no need for gci-docker-version and gci-ensure-gke-docker - t… #108195
there is no need for gci-docker-version and gci-ensure-gke-docker - t… #108195
Conversation
…hose are not used by COS or any of scripts Change-Id: I317c95d8fd2f51598cfa3e710380552d8fc07d2d
/lgtm |
@rkolchmeyer: changing LGTM is restricted to collaborators 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. |
/test pull-kubernetes-unit |
/unassign @bsdnet since @rkolchmeyer lgtm-ed |
/priority backlog |
/assign @cheftako |
/lgtm |
I do not think COS uses those metadata attributes |
/lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cheftako, mrunalp, SergeyKanzhelev 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 |
…hose are not used by COS or any of scripts
/kind cleanup
/sig node
/assign @bsdnet
The only reference to one of these is being removed here: #108192
@bsdnet to re-confirm those are not real COS metadata keys.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: