Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

⚠️ refactor: split awsmanagedcontrolplane into new manager #1949

Merged
merged 3 commits into from Sep 23, 2020
Merged

⚠️ refactor: split awsmanagedcontrolplane into new manager #1949

merged 3 commits into from Sep 23, 2020

Conversation

richardcase
Copy link
Member

What this PR does / why we need it:
The AWSManagedControlPlane and associated controller has been split out of the core managed into a separate control plane manager. This is so ultimately users can optionally install the control plane and also it could have separate IAM role.

The AWSManagedCluster stays in the main controller as AWSManagedMachinePool will be in there.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1945

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Sep 16, 2020
The AWSManagedControlPlane and associated controller has been split out
of the core managed into a separate control plane manager.
Small number of changes as a result of testing, mainly ensuring the
api group name as been updated and the correct schemes are imported
into the various managers (core, boostratp, control-plane).

The `eks` template has been updated to use the new control plane.
@richardcase richardcase changed the title WIP: ⚠️ refactor: split awsmanagedcontrolplane into new manager ⚠️ refactor: split awsmanagedcontrolplane into new manager Sep 18, 2020
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 18, 2020
@randomvariable
Copy link
Member

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 23, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: randomvariable

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 23, 2020
@k8s-ci-robot k8s-ci-robot merged commit 9f95d2f into kubernetes-sigs:master Sep 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Refactor the AWSManagedControlPlane out of the main controller
3 participants