-
Notifications
You must be signed in to change notification settings - Fork 101
implemented the Preemptable field for podgroup api #190
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?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
The protobuf tag for
Preemptableusesbytes, which is incorrect for a boolean type. For protobuf encoding, boolean values should be encoded asvarint.While this might appear to work in some contexts, it's semantically incorrect and can lead to compatibility and serialization issues with other standard Kubernetes tooling or future versions of protobuf.
For reference, standard Kubernetes API types use
varintfor*boolfields (e.g.,core/v1.SecurityContext.AllowPrivilegeEscalation). Using the correct type ensures proper serialization and interoperability.Please change
bytestovarint.