-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Remove incorrect Kubernetes REST API types in proto messages #8746
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 incorrect Kubernetes REST API types in proto messages #8746
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jackfrancis 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 |
|
/assign @liggitt |
.../cloudprovider/externalgrpc/examples/external-grpc-cloud-provider-service/wrapper/wrapper.go
Show resolved
Hide resolved
.../cloudprovider/externalgrpc/examples/external-grpc-cloud-provider-service/wrapper/wrapper.go
Show resolved
Hide resolved
.../cloudprovider/externalgrpc/examples/external-grpc-cloud-provider-service/wrapper/wrapper.go
Show resolved
Hide resolved
cluster-autoscaler/cloudprovider/externalgrpc/protos/externalgrpc.pb.go
Outdated
Show resolved
Hide resolved
| state protoimpl.MessageState `protogen:"open.v1"` | ||
| // nodeInfo is the extracted data from the cloud provider, as a primitive Kubernetes Node type. | ||
| NodeInfo *v11.Node `protobuf:"bytes,1,opt,name=nodeInfo,proto3" json:"nodeInfo,omitempty"` | ||
| NodeInfo *v1.Node `protobuf:"bytes,1,opt,name=nodeInfo,proto3" json:"nodeInfo,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gah... missed this in the earlier PR 🤦
all the REST API types have the identical issue of not being real reliable protomessages since $epoch, and being explicitly not protomessages in 1.35
Need to do the same thing here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sigh... I'll open a PR to master again ... so sorry...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all good, this is distracting me from kubecon prep stress so 🙏
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
opened #8747
| import ( | ||
| protoreflect "google.golang.org/protobuf/reflect/protoreflect" | ||
| protoimpl "google.golang.org/protobuf/runtime/protoimpl" | ||
| v1 "k8s.io/api/core/v1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is good and what I expected to see in the other generated file
87ef157 to
a627ed2
Compare
|
/lgtm |
What type of PR is this?
/kind deprecation
What this PR does / why we need it:
This follows #8660, which introduced replacement fields for Kubernetes REST API types that are being used as proto messages. Those types will not be valid starting w/ Kubernetes 1.35.
These types were removed: Pod/Node/StartTime/EndTime
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: