Object Storage Support (COSI)

[wlan0]

Enhancement Description

• One-line enhancement description (can be used as a release note): Natively support object storage in Kubernetes alongside file and block storage
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1979-object-storage-support
• Primary contact (assignee): @wlan0
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone):
  • Alpha release target (1.25)
  • Beta release target (1.32?)
• [x] Alpha
  • [x] KEP (k/enhancements) update PR(s):
    • 1.20 https://github.com/kubernetes/enhancements/pull/1383
    • 1.20 https://github.com/kubernetes/enhancements/pull/2100
    • 1.25 https://github.com/kubernetes/enhancements/pull/2813
  • [x] Code (k/k) update PR(s): code is out tree in https://github.com/kubernetes-sigs/container-object-storage-interface-spec/releases/tag/v0.1.0
  • [x] Docs (k/website) update(s): https://github.com/kubernetes/website/pull/35454
• [ ] Beta
  • [ ] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/4599
  • [ ] Code (k/k) update PR(s):
  • [ ] Docs (k/website) update(s):

[wlan0]

/sig storage

[wlan0]

/assign wlan0

[k8s-ci-robot]

@wlan0: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone 1.20

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/test-infra repository.

[xing-yang]

I see there's already another issue opened here: https://github.com/kubernetes/enhancements/issues/1593 Can we close one of them?

[wlan0]

Could you please close the other one: https://github.com/kubernetes/enhancements/issues/1593

Looks like john created that project before he left the group

[xing-yang]

Sure. I closed the other issue.

[kikisdeliveryservice]

@xing-yang @wlan0

Just confirming this is indeed for 1.21 not 1.20?

Thanks! Kirsten

[xing-yang]

@kikisdeliveryservice,

Yes, we are targeting Alpha in 1.21. In 1.20, we are planning to get the KEP merged as Provisional status and coding will happen in repos under kubernetes-sigs. That's why we still have 1.20 as milestone for the KEP.

[kikisdeliveryservice]

@xing-yang understood - thank you for the clarification! I'll update the sheet to reflect the alpha in 1.21 goal so we don't start pinging you for the 1.20 cycle on this issue :smile:

[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

[xing-yang]

/remove-lifecycle stale

[jrsapi]

Greetings @wlan0 @xing-yang,

This is Joseph v 1.21 enhancement shadow. For the enhancement to be included in the 1.21 milestone, it must meet the following criteria:

The KEP must be merged in an implementable state ~~The KEP must have test plans~~ Done ~~The KEP must have graduation criteria~~ Done The KEP must have a production readiness review

Also starting 1.21, all KEPs must include a production readiness review. Please make sure to take follow all the instructions and update the KEP to include this.

Thank you!

[jrsapi]

@wlan0 @xing-yang

Enhancements Freeze is 2 days away, Feb 9th EOD PST

Please make sure to work on PRR questionnaires and requirements and get it merged before the freeze. For PRR related questions or to boost the PR for PRR review, please reach out in slack #prod-readiness

Any enhancements that do not complete the following requirements by the freeze will require an exception.

[DONE] ~~The KEP must be merged in an implementable state~~ [IN PROGRESS] The KEP must have test plans [DONE] ~~The KEP must have graduation criteria~~ [IN PROGRESS] The KEP must have a production readiness review

[annajung]

Hi @wlan0 ,

Enhancements Freeze is now in effect.

Unfortunately, KEP for this enhancement does not meet all the required criteria. If you wish to be included in the 1.21 Release, please submit an Exception Request as soon as possible.

/milestone clear

[JamesLaverack]

/milestone v1.22

[supriya-premkumar]

Hello @wlan0 @xing-yang,

This is Supriya v1.22 enhancement shadow here. For the enhancement to be included in the 1.22 milestone, it must meet the following criteria:

The KEP must be merged in an implementable state The KEP must have a stage(alpha), state, latest-milestone, target milestones, and feature-gates in kep.yaml The KEP must have a production readiness review

Please make sure to take follow all the instructions and update the KEP to include this.

Thank you!

[supriya-premkumar]

Also, please make sure to update the KEP README and kep.yaml to match the latest templates.

[johnbelamaric]

Please assign me as PRR approver. Thanks.

[JamesLaverack]

Hi @wlan0, 1.22 Enhancements Lead here. :wave: With enhancements freeze now in effect we are removing this enhancement from the 1.22 release.

Feel free to file an exception to add this back to the release. If you plan to do so, please file this as early as possible.

Thanks! /milestone clear

[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

[xing-yang]

/remove-lifecycle stale

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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:

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

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active 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:

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

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

/close

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/test-infra repository.

[xing-yang]

/remove-lifecycle rotten

[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

[xing-yang]

/remove-lifecycle stale

[xing-yang]

/remove-lifecycle stale

[xing-yang]

Updated KEP for v1.25 is merged: https://github.com/kubernetes/enhancements/pull/2813