Enhancements: Support Out-of-Tree IBM Cloud Provider

[andrewsykim]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Support Out-of-Tree IBM Cloud Provider by running the cloud-controller-manager
• Primary contact (assignee):
  @rtheis @spzala
• Responsible SIGs:
  SIG IBM, SIG Cloud Provider
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
  @rtheis @spzala @andrewsykim
• Approver (likely from SIG/area to which enhancement belongs):
  @rtheis @spzala @andrewsykim
• Enhancement target (which target equals to which milestone):
  
  
  
  • Alpha release target (x.y)
  
  
  • Beta release target (x.y)
  
  
  • Stable release target (x.y)
  
  

Ref https://github.com/kubernetes/enhancements/issues/88

/sig ibm-cloud cloud-provider

[rtheis]

We have started investigating this enhancement and are working on the initial design.

[rtheis]

/sig ibm-cloud

[rtheis]

/sig ibmcloud

[rtheis]

/assign @rtheis

[k8s-ci-robot]

@rtheis: GitHub didn't allow me to assign the following users: rtheis.

Note that only kubernetes members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @rtheis

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.

[andrewsykim]

/sig ibmcloud

[andrewsykim]

@rtheis can we expect this to be alpha for v1.14?

[rtheis]

@andrewsykim that's my goal.

[andrewsykim]

Thanks, going to apply the stage/milestone labels for now, feel free to ping me if it needs to change for v1.14.

/stage alpha
/milestone v1.14

[claurence]

@rtheis @spzala does this issue have a KEP associated with it yet? We want all issues to have a KEP.

[andrewsykim]

@claurence I'm writing a draft KEP for all the out-of-tree providers that are alpha/beta for v1.14. Just blocked on https://github.com/kubernetes/enhancements/pull/703 at the moment.

[andrewsykim]

FYI put together the boiler plate for this KEP here https://github.com/kubernetes/enhancements/pull/735

[spzala]

@andrewsykim thanks!! Please let's know if you need us to provide any info or review.

[andrewsykim]

@spzala there are TODOs in the IBM KEP proposed in that PR. Will need you to fill it out after the PR is merged :)

[spzala]

@spzala there are TODOs in the IBM KEP proposed in that PR. Will need you to fill it out after the PR is merged :)

:) thanks @andrewsykim and that sounds good.

[claurence]

@rtheis @spzala since the KEP for this issue hasn't been merged yet we will be removing it from the 1.14 milestone. To have it added back in please file an exception - information on the exception process can be found here: https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

[rtheis]

@claurence will do.

[spzala]

@claurence sounds good, thanks!

[kacole2]

Hello @rtheis @andrewsykim , I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet.

Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly.

[rtheis]

@kacole2 sorry for the slow response. At most, we are targeting alpha in 1.15. I don't think there will be any k/k PRs. This work will primarily be around creating a new out-of-tree IBM cloud provider based on the current IBM cloud provider used by IBM's managed Kubernetes service.

[rtheis]

KEP PR: https://github.com/kubernetes/enhancements/pull/983

[mrbobbytables]

/milestone v1.15

[justaugustus]

/assign @rtheis @spzala

[k8s-ci-robot]

@justaugustus: GitHub didn't allow me to assign the following users: rtheis.

Note that only kubernetes members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @rtheis @spzala

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.

[kacole2]

/milestone clear

[evillgenius75]

Hi @rtheis @spzala, I'm a 1.16 Enhancement Shadow. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheet.

Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.

I notice there is aKEP for this Enhancement but it is still in provisional state. As a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

[rtheis]

@evillgenius75 This feature won't be graduating in 1.16. We have some additional steps necessary on IBM side before we can get started.

[jeremyrickard]

Hey there @rtheis -- 1.17 Enhancements shadow here 👋 . I wanted to check in and see if you think this Enhancement will be graduating to alpha 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, I'll add it to the 1.17 tracking sheet (https://bit.ly/k8s117-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[rtheis]

@jeremyrickard We don't have any plans for 1.17. Thanks for checking.

[posix4e]

I was curious what the status is here?

[johnbelamaric]

Hey there @rtheis and @spzala -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha in 1.18?

The current release schedule is:
Monday, January 6th - Release Cycle Begins
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

To be included in the release, this enhancement must have a merged KEP in the implementable status. The KEP must also have graduation criteria and a Test Plan defined.

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

We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements
Thanks!

[rtheis]

@johnbelamaric this enhancement won't be graduating to alpha in 1.18.

[rtheis]

@posix4e We are actively working on transitioning the IBM cloud provider to the new cloud-controller-manager (CCM) based architecture. This will be used in the IBM Cloud Kubernetes Service and Red Hat OpenShift on IBM Cloud offerings. Once this transition is completed, we'll hopefully be able to get back to this issue.

[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

[rtheis]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @rtheis @andrewsykim

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:

The KEP PR must be merged in an implementable state
The KEP must have test plans
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

Please let me know and 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!

[rtheis]

@kikisdeliveryservice This enhancement will not be graduating in 1.19. Thanks.

[kikisdeliveryservice]

thank you for the update @rtheis !

[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

[kikisdeliveryservice]

Hi @rtheis

Enhancements Lead here. Are there any plans for this 1.20?

Thanks!
Kirsten

[rtheis]

@kikisdeliveryservice There are no 1.20 plans. Thank you.