-
Notifications
You must be signed in to change notification settings - Fork 40.9k
Convert k8s.io/kms/apis
from gogo to protoc
#132833
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
base: master
Are you sure you want to change the base?
Conversation
k8s.io/kms/apis
from gogo to protock8s.io/kms/apis
from gogo to protoc
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
k8s.io/kms/apis
from gogo to protock8s.io/kms/apis
from gogo to protoc
ba15451
to
eb3f591
Compare
/retest |
k8s.io/kms/apis
from gogo to protock8s.io/kms/apis
from gogo to protoc
bc3ffca
to
0c21b28
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: saschagrunert The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Use standard protoc for the kms APIs instead of gogo. Part of kubernetes#96564 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
k8s.io/kms/apis
from gogo to protock8s.io/kms/apis
from gogo to protoc
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Use standard protoc for the kms APIs instead of gogo.
Which issue(s) this PR is related to:
Part of #96564
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: