-
Notifications
You must be signed in to change notification settings - Fork 40.4k
KEP-4222: Add CBOR feature gates. #128539
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
Conversation
/triage accepted |
/lgtm /hold |
LGTM label has been added. Git tree hash: 357fa09dcef6ca40568361ab83c31dc73ad8a5ea
|
aba1a32
to
66b59c9
Compare
Is there a (placeholder) PR to the website for this feature gate? |
|
/retest-required |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: benluddy, deads2k, jpbetz 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 |
For alpha, there is one apiserver feature gate and two client-go feature gates controlling CBOR. They were initially wired to separate test-only feature gate instances in order to prevent them from being configurable at runtime via command-line flags or environment variables (for client-go feature gates outside of Kubernetes components). All of the integration tests required by the KEP as alpha criteria have been implemented. This adds the feature gates to the usual feature gate instances and removes the temporary code to support separate test-only feature gate instances.
ebe7370
to
c42de7f
Compare
/hold cancel #128462 has merged. |
/lgtm |
LGTM label has been added. Git tree hash: 2515126a01b5be807c9db9c03a732dd99f6a825e
|
Setting AllAlpha=true in integration tests changes the dynamic client request encoding and the custom resource storage encoding to CBOR. The etcd storage path is updated to accept either JSON or CBOR as storage encoding. The client feature gate controlling the dynamic client request encoding is temporarily disabled until the serving codecs for builtin APIs are wired to the CBOR apiserver feature gate.
c42de7f
to
88c9dd7
Compare
/lgtm |
LGTM label has been added. Git tree hash: 5d5110cd09b6ac6eecb01023a98393c28a1bde3c
|
// If enabled, and only if ClientsAllowCBOR is also enabled, the default request content | ||
// type (if not explicitly configured) and the dynamic client's request content type both | ||
// become "application/cbor" instead of "application/json". The default content type for | ||
// apply patch requests becomes "application/apply-patch+cbor" instead of | ||
// "application/apply-patch+yaml". | ||
ClientsPreferCBOR Feature = "ClientsPreferCBOR" |
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 seems to cause the issues here #128600
What type of PR is this?
/kind feature
/sig api-machinery
What this PR does / why we need it:
For alpha, there is one apiserver feature gate and two client-go feature gates controlling CBOR. They were initially wired to separate test-only feature gate instances in order to prevent them from being configurable at runtime via command-line flags or environment variables (for client-go feature gates outside of Kubernetes components). All of the integration tests required by the KEP as alpha criteria have been implemented. This adds the feature gates to the usual feature gate instances and removes the temporary code to support separate test-only feature gate instances.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
This PR excludes wiring the codecs used for serving built-in API resources (by request from @deads2k). That will follow before 1.32 code freeze.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: