KEP-2338 Graduate API gzip compression to GA

[pacoxu]

• One-line PR description: update GA version to v1.33 and add some history PRs and issues.

• Issue link: API gzip compression support #2338

• Other comments:

[pacoxu]

/cc @smarterclayton @ilackarms
/assign @liggitt

@jpbetz does this need a PRR review?

[k8s-ci-robot]

@pacoxu: GitHub didn't allow me to request PR reviews from the following users: ilackarms.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @smarterclayton @ilackarms
/assign @liggitt

@jpbetz does this need a PRR review?

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.

[sftim]

Can we split this into two PRs?

1. Tidy up what we have for beta (eg, record the feature gate)
2. Graduate to GA. This can still target v1.33, right?

It feels odd to go from "feature gate not recorded properly" to "stable".

[sftim]

This doesn't look right, because all KEPs have a goal of general feature availability.

For GA, can we clean up the path? Maybe it's set and we have to live with it, but keps/sig-api-machinery/2338-API-gzip-compression-support/README.md would make more sense if feasible.

[sftim]

Typo; should be “revisit“

[sftim]

/retitle KEP-2338 Graduate API gzip compression to GA

[liggitt]

I'm in favor of graduating this... the client opt-out bits and compression level reduction in the 1.25/1.26 timeframe seem to have addressed the concerns.

@jpbetz, can you review or delegate for PRR bits?

[jpbetz]

@pacoxu Looks like this KEP pre-dates the PRR review sections. Would you copy them in from the template and fill in the sections that apply to this GA promotion? (and double check that we didn't miss anything from the alpha/beta sections that should be considered?)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pacoxu
Once this PR has been reviewed and has the lgtm label, please ask for approval from jpbetz. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• keps/prod-readiness/OWNERS
• keps/sig-api-machinery/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pacoxu]

@pacoxu Looks like this KEP pre-dates the PRR review sections. Would you copy them in from the template and fill in the sections that apply to this GA promotion? (and double check that we didn't miss anything from the alpha/beta sections that should be considered?)

I tried to add some comments for those questions.

[wojtek-t]

Please copy and answer all questions from the template.