Skip to content

Commit

Permalink
Draft KEPs for out-of-tree cloud providers
Browse files Browse the repository at this point in the history
  • Loading branch information
andrewsykim committed Jan 29, 2019
1 parent eeccd18 commit c35f81e
Show file tree
Hide file tree
Showing 8 changed files with 594 additions and 0 deletions.
99 changes: 99 additions & 0 deletions keps/sig-cloud-provider/20190125-out-of-tree-aws.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,99 @@
---
title: Support Out-of-Tree AWS Cloud Provider
authors:
- @andrewsykim
owning-sig: sig-cloud-provider
participating-sigs:
- sig-aws
reviewers:
- TBD
approvers:
- TBD
editor: TBD
creation-date: 2019-01-25
last-updated: 2019-01-25
status: provisional

---

# Supporting Out-of-Tree AWS Cloud Provider

## Table of Contents

* [Table of Contents](#table-of-contents)
* [Release Signoff Checklist](#release-signoff-checklist)
* [Summary](#summary)
* [Motivation](#motivation)
* [Goals](#goals)
* [Non-Goals](#non-goals)
* [Proposal](#proposal)
* [Implementation Details/Notes/Constraints [optional]](#implementation-detailsnotesconstraints-optional)
* [Risks and Mitigations](#risks-and-mitigations)
* [Design Details](#design-details)
* [Test Plan](#test-plan)
* [Graduation Criteria](#graduation-criteria)
* [Upgrade / Downgrade Strategy](#upgrade--downgrade-strategy)
* [Version Skew Strategy](#version-skew-strategy)
* [Implementation History](#implementation-history)

## Release Signoff Checklist

- [X] k/enhancements issue in release milestone and linked to KEP (https://github.com/kubernetes/enhancements/issues/631)
- [ ] KEP approvers have set the KEP status to `implementable`
- [ ] Design details are appropriately documentedbs
- [ ] Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
- [ ] Graduation criteria is in place
- [ ] "Implementation History" section is up-to-date for milestone
- [ ] Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

## Summary

Build support for the out-of-tree AWS cloud provider. This involves a well-tested version of the cloud-controller-manager
that has feature parity to the kube-controller-manager.

## Motivation

Motivation for supporting out-of-tree providers can be found in [KEP-0002](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/0002-cloud-controller-manager.md).
This KEP is specifically tracking progress for the AWS cloud provider.

### Goals

* Develop/test/release the AWS cloud-controller-manager
* Kubernetes clusters running on AWS should be running the cloud-controller-manager.

### Non-Goals

* Removing in-tree AWS cloud provider code, this effort falls under the [KEP for removing in-tree providers](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/2019-01-25-removing-in-tree-providers.md).

## Proposal

### Implementation Details/Notes/Constraints [optional]

TODO for SIG-AWS

### Risks and Mitigations

TODO for SIG-AWS

## Design Details

### Test Plan

TODO for SIG-AWS

### Graduation Criteria

TODO for SIG-AWS

### Upgrade / Downgrade Strategy

TODO for SIG-AWS

### Version Skew Strategy

TODO for SIG-AWS

## Implementation History

TODO for SIG-AWS

99 changes: 99 additions & 0 deletions keps/sig-cloud-provider/20190125-out-of-tree-azure.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,99 @@
---
title: Support Out-of-Tree Azure Cloud Provider
authors:
- @andrewsykim
owning-sig: sig-cloud-provider
participating-sigs:
- sig-azure
reviewers:
- TBD
approvers:
- TBD
editor: TBD
creation-date: 2019-01-25
last-updated: 2019-01-25
status: provisional

---

# Supporting Out-of-Tree Azure Cloud Provider

## Table of Contents

* [Table of Contents](#table-of-contents)
* [Release Signoff Checklist](#release-signoff-checklist)
* [Summary](#summary)
* [Motivation](#motivation)
* [Goals](#goals)
* [Non-Goals](#non-goals)
* [Proposal](#proposal)
* [Implementation Details/Notes/Constraints [optional]](#implementation-detailsnotesconstraints-optional)
* [Risks and Mitigations](#risks-and-mitigations)
* [Design Details](#design-details)
* [Test Plan](#test-plan)
* [Graduation Criteria](#graduation-criteria)
* [Upgrade / Downgrade Strategy](#upgrade--downgrade-strategy)
* [Version Skew Strategy](#version-skew-strategy)
* [Implementation History](#implementation-history)

## Release Signoff Checklist

- [X] k/enhancements issue in release milestone and linked to KEP (https://github.com/kubernetes/enhancements/issues/667)
- [ ] KEP approvers have set the KEP status to `implementable`
- [ ] Design details are appropriately documentedbs
- [ ] Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
- [ ] Graduation criteria is in place
- [ ] "Implementation History" section is up-to-date for milestone
- [ ] Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

## Summary

Build support for the out-of-tree Azure cloud provider. This involves a well-tested version of the cloud-controller-manager
that has feature parity to the kube-controller-manager.

## Motivation

Motivation for supporting out-of-tree providers can be found in [KEP-0002](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/0002-cloud-controller-manager.md).
This KEP is specifically tracking progress for the Azure cloud provider.

### Goals

* Develop/test/release the Azure cloud-controller-manager
* Kubernetes clusters running on Azure should be running the cloud-controller-manager.

### Non-Goals

* Removing in-tree Azure cloud provider code, this effort falls under the [KEP for removing in-tree providers](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/2019-01-25-removing-in-tree-providers.md).

## Proposal

### Implementation Details/Notes/Constraints [optional]

TODO for SIG-Azure

### Risks and Mitigations

TODO for SIG-Azure

## Design Details

### Test Plan

TODO for SIG-Azure

### Graduation Criteria

TODO for SIG-Azure

### Upgrade / Downgrade Strategy

TODO for SIG-Azure

### Version Skew Strategy

TODO for SIG-Azure

## Implementation History

TODO for SIG-Azure

99 changes: 99 additions & 0 deletions keps/sig-cloud-provider/20190125-out-of-tree-gce.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,99 @@
---
title: Support Out-of-Tree GCE Cloud Provider
authors:
- @andrewsykim
owning-sig: sig-cloud-provider
participating-sigs:
- sig-gcp
reviewers:
- TBD
approvers:
- TBD
editor: TBD
creation-date: 2019-01-25
last-updated: 2019-01-25
status: provisional

---

# Supporting Out-of-Tree GCE Cloud Provider

## Table of Contents

* [Table of Contents](#table-of-contents)
* [Release Signoff Checklist](#release-signoff-checklist)
* [Summary](#summary)
* [Motivation](#motivation)
* [Goals](#goals)
* [Non-Goals](#non-goals)
* [Proposal](#proposal)
* [Implementation Details/Notes/Constraints [optional]](#implementation-detailsnotesconstraints-optional)
* [Risks and Mitigations](#risks-and-mitigations)
* [Design Details](#design-details)
* [Test Plan](#test-plan)
* [Graduation Criteria](#graduation-criteria)
* [Upgrade / Downgrade Strategy](#upgrade--downgrade-strategy)
* [Version Skew Strategy](#version-skew-strategy)
* [Implementation History](#implementation-history)

## Release Signoff Checklist

- [X] k/enhancements issue in release milestone and linked to KEP (https://github.com/kubernetes/enhancements/issues/668)
- [ ] KEP approvers have set the KEP status to `implementable`
- [ ] Design details are appropriately documentedbs
- [ ] Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
- [ ] Graduation criteria is in place
- [ ] "Implementation History" section is up-to-date for milestone
- [ ] Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

## Summary

Build support for the out-of-tree GCE cloud provider. This involves a well-tested version of the cloud-controller-manager
that has feature parity to the kube-controller-manager.

## Motivation

Motivation for supporting out-of-tree providers can be found in [KEP-0002](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/0002-cloud-controller-manager.md).
This KEP is specifically tracking progress for the GCE cloud provider.

### Goals

* Develop/test/release the GCE cloud-controller-manager
* Kubernetes clusters running on GCE should be running the cloud-controller-manager.

### Non-Goals

* Removing in-tree GCE cloud provider code, this effort falls under the [KEP for removing in-tree providers](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/2019-01-25-removing-in-tree-providers.md).

## Proposal

### Implementation Details/Notes/Constraints [optional]

TODO for SIG-GCP

### Risks and Mitigations

TODO for SIG-GCP

## Design Details

### Test Plan

TODO for SIG-GCP

### Graduation Criteria

TODO for SIG-GCP

### Upgrade / Downgrade Strategy

TODO for SIG-GCP

### Version Skew Strategy

TODO for SIG-GCP

## Implementation History

TODO for SIG-GCP

99 changes: 99 additions & 0 deletions keps/sig-cloud-provider/20190125-out-of-tree-ibm.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,99 @@
---
title: Support Out-of-Tree IBM Cloud Provider
authors:
- @andrewsykim
owning-sig: sig-cloud-provider
participating-sigs:
- sig-ibm
reviewers:
- TBD
approvers:
- TBD
editor: TBD
creation-date: 2019-01-25
last-updated: 2019-01-25
status: provisional

---

# Supporting Out-of-Tree IBM Cloud Provider

## Table of Contents

* [Table of Contents](#table-of-contents)
* [Release Signoff Checklist](#release-signoff-checklist)
* [Summary](#summary)
* [Motivation](#motivation)
* [Goals](#goals)
* [Non-Goals](#non-goals)
* [Proposal](#proposal)
* [Implementation Details/Notes/Constraints [optional]](#implementation-detailsnotesconstraints-optional)
* [Risks and Mitigations](#risks-and-mitigations)
* [Design Details](#design-details)
* [Test Plan](#test-plan)
* [Graduation Criteria](#graduation-criteria)
* [Upgrade / Downgrade Strategy](#upgrade--downgrade-strategy)
* [Version Skew Strategy](#version-skew-strategy)
* [Implementation History](#implementation-history)

## Release Signoff Checklist

- [X] k/enhancements issue in release milestone and linked to KEP (https://github.com/kubernetes/enhancements/issues/671)
- [ ] KEP approvers have set the KEP status to `implementable`
- [ ] Design details are appropriately documentedbs
- [ ] Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
- [ ] Graduation criteria is in place
- [ ] "Implementation History" section is up-to-date for milestone
- [ ] Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

## Summary

Build support for the out-of-tree IBM cloud provider. This involves a well-tested version of the cloud-controller-manager
that has feature parity to the kube-controller-manager.

## Motivation

Motivation for supporting out-of-tree providers can be found in [KEP-0002](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/0002-cloud-controller-manager.md).
This KEP is specifically tracking progress for the IBM cloud provider.

### Goals

* Develop/test/release the IBM cloud-controller-manager
* Kubernetes clusters running on IBM should be running the cloud-controller-manager.

### Non-Goals

* Removing in-tree IBM cloud provider code, this effort falls under the [KEP for removing in-tree providers](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/2019-01-25-removing-in-tree-providers.md).

## Proposal

### Implementation Details/Notes/Constraints [optional]

TODO for SIG-IBM

### Risks and Mitigations

TODO for SIG-IBM

## Design Details

### Test Plan

TODO for SIG-IBM

### Graduation Criteria

TODO for SIG-IBM

### Upgrade / Downgrade Strategy

TODO for SIG-IBM

### Version Skew Strategy

TODO for SIG-IBM

## Implementation History

TODO for SIG-IBM

Loading

0 comments on commit c35f81e

Please sign in to comment.