Skip to content

Support Out-of-Tree IBM Cloud Provider #671

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom
Closed
andrewsykim opened this issue Jan 2, 2019 · 56 comments
Closed

Support Out-of-Tree IBM Cloud Provider #671

andrewsykim opened this issue Jan 2, 2019 · 56 comments
Assignees
@spzala
Labels
area/provider/ibmcloud Issues or PRs related to ibmcloud provider sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team

Comments

@andrewsykim
Copy link
Member

andrewsykim commented Jan 2, 2019 •
edited
Loading

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 #88

/sig ibm-cloud cloud-provider
@k8s-ci-robot k8s-ci-robot added the sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. label Jan 2, 2019
@andrewsykim andrewsykim mentioned this issue Jan 2, 2019
Closed
@rtheis
Copy link

rtheis commented Jan 22, 2019

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

@rtheis
Copy link

rtheis commented Jan 23, 2019

/sig ibm-cloud

@rtheis
Copy link

rtheis commented Jan 23, 2019

/sig ibmcloud

@rtheis
Copy link

rtheis commented Jan 23, 2019

/assign @rtheis

@k8s-ci-robot
Copy link
Contributor

@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
Copy link
Member Author

/sig ibmcloud

@k8s-ci-robot k8s-ci-robot added the area/provider/ibmcloud Issues or PRs related to ibmcloud provider label Jan 23, 2019
@andrewsykim
Copy link
Member Author

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

@rtheis
Copy link

rtheis commented Jan 25, 2019

@andrewsykim that's my goal.

@andrewsykim
Copy link
Member Author

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

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Jan 25, 2019
@k8s-ci-robot k8s-ci-robot added this to the v1.14 milestone Jan 25, 2019
@claurence claurence added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jan 25, 2019
@claurence
Copy link

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

@andrewsykim
Copy link
Member Author

@claurence I'm writing a draft KEP for all the out-of-tree providers that are alpha/beta for v1.14. Just blocked on #703 at the moment.

@andrewsykim andrewsykim mentioned this issue Jan 28, 2019
Merged
@andrewsykim
Copy link
Member Author

FYI put together the boiler plate for this KEP here #735

@spzala
Copy link
Member

spzala commented Jan 29, 2019

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

@andrewsykim
Copy link
Member Author

@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
Copy link
Member

spzala commented Jan 29, 2019

@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
Copy link

@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

@claurence claurence removed this from the v1.14 milestone Jan 30, 2019
@claurence claurence added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Jan 30, 2019
@rtheis
Copy link

rtheis commented Jan 30, 2019

@claurence will do.

@spzala
Copy link
Member

spzala commented Jan 30, 2019

@claurence sounds good, thanks!

@kacole2
Copy link

kacole2 commented Apr 12, 2019

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
Copy link

rtheis commented Apr 17, 2019

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

@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 9, 2020
@palnabarun
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 1, 2020
@kikisdeliveryservice
Copy link
Member

Hi @rtheis

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

Thanks!
Kirsten

@rtheis
Copy link

rtheis commented Sep 14, 2020

@kikisdeliveryservice There are no 1.20 plans. Thank you.

@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 Dec 13, 2020
@rtheis
Copy link

rtheis commented Dec 14, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 14, 2020
@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-contributor-experience at kubernetes/community.
/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 Mar 14, 2021
@rtheis
Copy link

rtheis commented Mar 15, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 15, 2021
@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-contributor-experience at kubernetes/community.
/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 Jun 13, 2021
@rtheis
Copy link

rtheis commented Jun 14, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 14, 2021
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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 Sep 12, 2021
@rtheis
Copy link

rtheis commented Sep 13, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 13, 2021
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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 Dec 12, 2021
@rtheis
Copy link

rtheis commented Dec 12, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 12, 2021
@andrewsykim
Copy link
Member Author

@rtheis any objections to closing this issue? The original intention was to track efforts for externalizing providers back when we had provider-specific SIGs. I think this can be tracked separate from the Kubernetes KEP process now

@rtheis
Copy link

rtheis commented Jan 31, 2022

@andrewsykim no objections. You can close it.

@andrewsykim
Copy link
Member Author

/close

@k8s-ci-robot
Copy link
Contributor

@andrewsykim: Closing this issue.

In response to this:

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

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@spzala spzala

Labels
area/provider/ibmcloud Issues or PRs related to ibmcloud provider sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests