Building Kubernetes Without In-Tree Cloud Providers

[BenTheElder]

Enhancement Description

• One-line enhancement description (can be used as a release note): Enable building Kubernetes without the in-tree (legacy) cloud providers.
• Kubernetes Enhancement Proposal: 20190729-building-without-in-tree-providers.md
• Primary contact (assignee): @BenTheElder
• Responsible SIGs: Cloud-Provider, Release
• Enhancement target (which target equals to which milestone):
  • Alpha release target (1.16)
  • Beta release target (x.y)
  • Stable release target (x.y)

Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement

[BenTheElder]

/sig cloud-provider
/sig release

[kacole2]

@BenTheElder I'm sure you know Enhancement Freeze is tomorrow so this is your notice that #1180 needs to be merged by then. Thanks!

/milestone v1.16
/stage alpha

[BenTheElder]

Hi @kacole2, yes, @justaugustus suggested that we should probably file an extension for this since it:

• isn't user facing
• shouldn't be a risk to the release
• already has a partially reviewed implementation of the github.com/kubernetes/kubernetes changes

I will go look into that now, as I suspect the addition of a KEP to cover at this point this means review will go into tomorrow at minimum, but the details now captured there were previously discussed with the owning parties and implemented successfully so I think we should be able to get this in 😅

[kacole2]

@BenTheElder @justaugustus

Enhancement Freeze has passed for 1.16. The KEP at #1180 was never merged and now this is being removed from the 1.16 milestone. If this would like to be re-added, please file an exception and it will require approval from the release lead.

/milestone clear

[BenTheElder]

Thanks @kacole2, I've filed an exception request 🤞

[BenTheElder]

KEP is merged and implementable in #1180

[simplytunde]

@BenTheElder I am 1.16 Doc Lead. We need a placeholder PR against k/website(dev-1.16 branch) for this enhancement before Friday, Aug 23rd. Let me know how I can help to make this happen or if doc is not required.

[BenTheElder]

Hi @simplytunde, this is not user facing and will not have any documentation on k/website.

[kacole2]

@BenTheElder will this have any K/K PRs that need to be tracked?

[BenTheElder]

I thought I'd linked these here but seems I didn't! D'oh.

kubernetes/kubernetes#80353 pretty much implemented this and merged in K/K already.

We will probably want to do some follow ups eventually but I think we probably don't need to track them and some of them might hold until 1.17+ (CSI migration testing having integration with this will probably slip until at least 1.17..).

[mrbobbytables]

Hey there @BenTheElder -- 1.17 Enhancements lead here. I wanted to check in and see if you think this Enhancement will be graduating to beta in 1.17?

The current release schedule is:

• Monday, September 23 - Release Cycle Begins
• Tuesday, October 15, EOD PST - Enhancements Freeze
• Thursday, November 14, EOD PST - Code Freeze
• Tuesday, November 19 - Docs must be completed and reviewed
• Monday, December 9 - Kubernetes 1.17.0 Released

If you do, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

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

[palnabarun]

/remove-lifecycle stale

[helayoty]

Hey there @BenTheElder -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to beta in 1.18 or having a major change in its current level?

The current release schedule is:

Tuesday, January 28th EOD PST - Enhancements Freeze
Thursday, March 5th, EOD PST - Code Freeze
Monday, March 16th - Docs must be completed and reviewed
Tuesday, March 24th - Kubernetes 1.18.0 Released

If you would like to include this enhancement, please list all relevant k/k PRs in this issue so they can be tracked properly.

Thanks!

[BenTheElder]

cc @liggitt I think maybe we can call this one done actually ...?
we decided to add some tests to prevent regressions, those landed in 1.17.

[liggitt]

sounds good

/close

[k8s-ci-robot]

@liggitt: Closing this issue.

In response to this:

sounds good

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

[palnabarun]

Hi @liggitt @BenTheElder -- 1.19 Enhancements Lead here. Since, this enhancement graduated to stable, can you please also mark the KEP implemented? 🙂

/reopen
(Reopening in the interim until the KEP is marked implemented)

[k8s-ci-robot]

@palnabarun: Reopened this issue.

In response to this:

Hi @liggitt @BenTheElder -- 1.19 Enhancements Lead here. Since, this enhancement graduated to stable, can you please also mark the KEP implemented? 🙂

/reopen
(Reopening in the interim until the KEP is marked implemented)

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.

[palnabarun]

/milestone v1.17

(since the enhancement was implemented in v1.17 cycle)

[BenTheElder]

/assign

[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

[BenTheElder]

/remove-lifecycle stale

[BenTheElder]

Sorry for the delay, this is actually fixed now!