KEP Issue: Object Storage API

[copejon]

Object Storage API

• An API for managing object store buckets/containers via CRDs and controllers modeled after CSI's central controller and sidecars and communicating to drivers via gRPC.
• Pull Request: object bucket provisioning #1383
• Primary contact (assignee):

@copejon
@jeffvance

• Responsible SIGs: sig-storage

• Enhancement target (which target equals to which milestone):
  TBD, pending initial concept acceptance

  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target (x.y)

[copejon]

/sig storage

[k8s-ci-robot]

@copejon: The label(s) sig/sig-storage cannot be applied, because the repository doesn't have them

In response to this:

/sig sig-storage

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.

[harshanarayana]

Hey there @copejon / @jeffvance -- 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?

In order to have this part of the release:

1. The KEP PR must be merged in an implementable state
2. The KEP must have test plans
3. The KEP must have graduation criteria.

The current release schedule is:

• Monday, April 13: Week 1 - Release cycle begins
• Tuesday, May 19: Week 6 - Enhancements Freeze
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[copejon]

Hi @harshanarayana. I don't anticipate having code finalized by the freeze date.

[harshanarayana]

Thanks @copejon for following up with an update on this issue. I have updated the tracker accordingly.

In case if you are planning to pick this up in one of the upcoming releases, please do let me know so that I can update the tracker accordinly to reflect the same.

Thanks

[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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[palnabarun]

/remove-lifecycle rotten

[kikisdeliveryservice]

I believe this will be closed in favor of #1979 but I will allow @xing-yang to update here first and then update the tracking sheet

[xing-yang]

I'm closing this one. Thanks.