Skip to content
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

Object Storage Support (COSI) #1979

Open
wlan0 opened this issue Sep 10, 2020 · 35 comments
Open

Object Storage Support (COSI) #1979

wlan0 opened this issue Sep 10, 2020 · 35 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team

Comments

@wlan0
Copy link
Member

wlan0 commented Sep 10, 2020

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: object bucket provisioning #1383
  • Primary contact (assignee): @wlan0
  • Responsible SIGs: sig-storage
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (1.25)

https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1979-object-storage-support

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 10, 2020
@wlan0
Copy link
Member Author

wlan0 commented Sep 10, 2020

/sig storage

@k8s-ci-robot k8s-ci-robot added sig/storage Categorizes an issue or PR as relevant to SIG Storage. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 10, 2020
@wlan0
Copy link
Member Author

wlan0 commented Sep 10, 2020

/assign wlan0

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Sep 10, 2020

@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
Copy link
Contributor

xing-yang commented Sep 11, 2020

I see there's already another issue opened here: #1593
Can we close one of them?

@wlan0
Copy link
Member Author

wlan0 commented Sep 11, 2020

Could you please close the other one: #1593

Looks like john created that project before he left the group

@xing-yang
Copy link
Contributor

xing-yang commented Sep 12, 2020

Sure. I closed the other issue.

@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 12, 2020

@xing-yang @wlan0

Just confirming this is indeed for 1.21 not 1.20?

Thanks!
Kirsten

@xing-yang
Copy link
Contributor

xing-yang commented Sep 12, 2020

@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
Copy link
Member

kikisdeliveryservice commented Sep 12, 2020

@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 😄

@kikisdeliveryservice kikisdeliveryservice added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Sep 24, 2020
@kikisdeliveryservice kikisdeliveryservice added this to the v1.21 milestone Sep 24, 2020
@kikisdeliveryservice kikisdeliveryservice added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Sep 28, 2020
@fejta-bot
Copy link

fejta-bot commented Dec 27, 2020

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 27, 2020
@xing-yang
Copy link
Contributor

xing-yang commented Jan 13, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 13, 2021
@annajung annajung added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Jan 14, 2021
@jrsapi
Copy link

jrsapi commented Jan 28, 2021

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
Copy link

jrsapi commented Feb 8, 2021

@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
Copy link
Member

annajung commented Feb 10, 2021

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

@k8s-ci-robot k8s-ci-robot removed this from the v1.21 milestone Feb 10, 2021
@annajung annajung added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Feb 10, 2021
@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 30, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Nov 28, 2021

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 28, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Dec 28, 2021

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-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 28, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Jan 27, 2022

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
Copy link
Contributor

k8s-ci-robot commented Jan 27, 2022

@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
Copy link
Contributor

xing-yang commented Feb 11, 2022

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Feb 11, 2022
@xing-yang xing-yang reopened this Feb 11, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented May 12, 2022

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2022
@xing-yang
Copy link
Contributor

xing-yang commented May 23, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 23, 2022
@xing-yang
Copy link
Contributor

xing-yang commented Jun 2, 2022

/remove-lifecycle stale

@xing-yang
Copy link
Contributor

xing-yang commented Jun 14, 2022

Updated KEP for v1.25 is merged: #2813

@sftim
Copy link
Contributor

sftim commented Jul 17, 2022

/retitle Object Storage Support (COSI)

to aid discovery

@k8s-ci-robot k8s-ci-robot changed the title Object Storage Support Object Storage Support (COSI) Jul 17, 2022
@sftim
Copy link
Contributor

sftim commented Jul 17, 2022

@wlan0 would you be willing to edit the issue description so that it links to https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1979-object-storage-support ?

@wlan0
Copy link
Member Author

wlan0 commented Jul 18, 2022

Done @sftim!

wlan0 added a commit to wlan0/enhancements that referenced this issue Aug 4, 2022
k8s-ci-robot added a commit that referenced this issue Aug 4, 2022
update object storage (#1979) alpha milestone to v1.25
pacoxu pushed a commit to pacoxu/enhancements that referenced this issue Oct 12, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Oct 16, 2022

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 16, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Nov 15, 2022

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-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team
Projects
None yet
Development

No branches or pull requests