Versioning Policy for External Cloud Providers

[andrewsykim]

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

[andrewsykim]

/sig cloud-provider

[palnabarun]

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]

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

[andrewsykim]

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]

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