Streaming Proxy Redirects [DEPRECATED]

[tallclair]

Enhancement Description

• One-line enhancement description (can be used as a release note): Deprecate & remove StreamingProxyRedirects and redirect-container-streaming
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1558-streaming-proxy-redirects
• Primary contact (assignee): @tallclair
• Responsible SIGs: node, api-machinery
• Enhancement target (which target equals to which milestone):
  • See https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1558-streaming-proxy-redirects#rollout-plan

Deprecation plan:

• release 1.18
  1. Mark the --redirect-container-streaming flag as deprecated. Log a warning on use.
  2. Mark the StreamingProxyRedirects feature as deprecated. Log a warning on use.
• release 1.19 - no changes
• release 1.20
  1. --redirect-container-streaming can no longer be enabled. If the flag is set, log an error
     and continue as though it is unset.
• release 1.22 (previously: 1.21) Default StreamingProxyRedirects to disabled kubernetes#101647
  1. Default StreamingProxyRedirects to disabled. If there is a >= 2 version skew between master
     and nodes, and the old nodes were enabling --redirect-container-streaming, this will break
     them. In this case, the StreamingProxyRedirects can still be manually enabled.
• release 1.24 (previously: 1.22)
  1. Remove the --redirect-container-streaming flag.
  2. Remove the StreamingProxyRedirects feature.

[tallclair]

/sig node

[palnabarun]

Hi @tallclair, -- 1.19 Enhancements Lead here. I see from the KEP that no work is planned for 1.19. I just wanted to confirm if that is still the case?

Thank you!

[tallclair]

Yep, confirmed. I'll paste the rollout plan here to make raise the visibility. We do have an action coming up in
/milestone v1.20

1. [DONE] release 1.18
   1. Mark the --redirect-container-streaming flag as deprecated. Log a warning on use.
   2. Mark the StreamingProxyRedirects feature as deprecated. Log a warning on use.
2. release 1.19 - no changes
3. release 1.20
   1. --redirect-container-streaming can no longer be enabled. If the flag is set, log an error
      and continue as though it is unset.
4. release 1.22 (was: 1.21)
   1. Default StreamingProxyRedirects to disabled. If there is a >= 2 version skew between master
      and nodes, and the old nodes were enabling --redirect-container-streaming, this will break
      them. In this case, the StreamingProxyRedirects can still be manually enabled.
5. release 1.24 (was: 1.22)
   1. Remove the --redirect-container-streaming flag.
   2. Remove the StreamingProxyRedirects feature.

[palnabarun]

@tallclair Thank you for the update. Also, a big shoutout for putting put all future plans in the issue as a comment. ➕

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[palnabarun]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @tallclair

Enhancements Lead here, can you confirm whether this will have work in 1.20? (alpha/beta/GA?)

Thanks!
Kirsten

[tallclair]

Yes, this has some work targeting v1.20. I hoisted the rollout plan to the issue description.

[kikisdeliveryservice]

So I noticed that this is a Deprecation rollout, so I'm wondering how to track this against alpha/beta/stable.. Maybe this could be beta? But I feel like I'm forcing it 🤔

WDYT @tallclair @palnabarun ?

[tallclair]

Yeah, I don't think alpha/beta/ga makes sense here. I don't know enough about the feature tracking process to know what the alternatives are.

[kikisdeliveryservice]

@tallclair let me check on this and i'll report back!

[kikisdeliveryservice]

After discussing, we agree it's important to track & publicize, so we made a new status so that we can track this as a drumroll deprecation! 😄

[kikisdeliveryservice]

Hey @tallclair !

Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates:
Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline <--- Pretty sure you'll want to do this one for the deprecation
Thursday, Nov 12th: Week 9 - Code Freeze

As a reminder, please link all of your k/k PR as well as docs PRs to this issue so we can track them.

Thanks!
Kirsten 😃

[reylejano]

Hello @tallclair , 1.20 Docs shadow here.

Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against the dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th.

Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[tallclair]

No docs changes needed for this one.

[annajung]

Hi @tallclair

Please keep in mind the important upcoming dates:

• Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline Docs Not Required
• Thursday, Nov 12th: Week 9 - Code Freeze
• Monday, Nov 23rd: Week 11 - Docs PR Ready for Review Docs Not Required

As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track.

[kikisdeliveryservice]

Hi @tallclair

Looks like kubernetes/kubernetes#95935 is merged and that was the only PR for 1.20 - correct?

As a note: Code Freeze is coming up in 2 days on Thursday, November 12th. All PRs must be merged by that date, otherwise an Exception is required.

Thanks!
Kirsten

[tallclair]

Correct.

[JamesLaverack]

Hey @tallclair, 1.22 Enhancements Lead here.

While a depreciation doesn't really go through the same criteria as a graduation, there's still a few things I'd like to clarify about your KEP:

• Can you set the latest-milestone key in your kep.yaml to be "v1.22".
• Also in the kep.yaml file, should the state still be implementable?
• Can you update the rollout plan in your KEP to match this issue? (i.e., specify which is coming in 1.22 and which in 1.24)

[pacoxu]

@JamesLaverack I opened #2707.

[pacoxu]

/assign

[JamesLaverack]

Also I see that SIG API Machinery is listed as a participating SIG in your KEP. Will they need to do anything towards this deprecation in 1.22, and if so are they aware of that?

[JamesLaverack]

With #2707 merged we're good for 1.22 enhancements freeze.

[tallclair]

We need to update https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-graduated-or-deprecated-features with the state of StreamingProxyRedirects and ValidateProxyRedirects.

EDIT: kubernetes/website#28065

[pacoxu]

All items for 1.22 are done.

• - PR: Default StreamingProxyRedirects to disabled kubernetes#101647
• - Docs: StreamingProxyRedirects deprecation docs website#28065

[salaxander]

@tallclair @pacoxu - would you be able to do a PR on the KEP.yaml to change the state to implemented? At that point we should be able to close the issue.

Thanks!

[pacoxu]

@salaxander updated the status in #2878.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pacoxu]

/remove-lifecycle stale

[pacoxu]

kubernetes/kubernetes#108531 is a follow up of kubernetes/kubernetes#106830