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

Jump to bottom

Versioning Policy for External Cloud Providers #1771

Closed
andrewsykim opened this issue May 13, 2020 · 5 comments
Closed

Versioning Policy for External Cloud Providers #1771

andrewsykim opened this issue May 13, 2020 · 5 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider.

Comments

@andrewsykim
Copy link
Member

Enhancement Description

  • One-line enhancement description (can be used as a release note):

Propose a versioning policy that all external cloud providers should follow.

  • Kubernetes Enhancement Proposal: (link to kubernetes/enhancements file, if none yet, link to PR)

#1727

  • Primary contact (assignee): @andrewsykim
  • Responsible SIGs: Cloud Provider
  • Enhancement target (which target equals to which milestone):
    • Stable release target 1.19

Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label May 13, 2020
@andrewsykim
Copy link
Member Author

/sig cloud-provider

@k8s-ci-robot k8s-ci-robot added sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 13, 2020
@palnabarun
Copy link
Member

Hi @andrewsykim -- 1.19 Enhancements Lead here.

Looking at the KEP, it seems that it is an out-of-tree change. Can you please confirm the same?

Thanks! 🙂

@fejta-bot
Copy link

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 Aug 13, 2020
@andrewsykim
Copy link
Member Author

Looking at the KEP, it seems that it is an out-of-tree change. Can you please confirm the same?

Yes this is for out-of-tree providers consuming the in-tree cloud provider libs.

Closing since the KEP has been approved / implemented.

/close

@k8s-ci-robot
Copy link
Contributor

@andrewsykim: Closing this issue.

In response to this:

Looking at the KEP, it seems that it is an out-of-tree change. Can you please confirm the same?

Yes this is for out-of-tree providers consuming the in-tree cloud provider libs.

Closing since the KEP has been approved / implemented.

/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@palnabarun @andrewsykim @k8s-ci-robot @fejta-bot