-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[WIP] 🌱 remove separate eks providers and update quick start #5073
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Until CAPA 0.7.0 is available: /hold |
Signed-off-by: Richard Case <[email protected]>
5b6ca8b
to
a7f23b8
Compare
@richardcase: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
@@ -175,6 +175,8 @@ Download the latest binary of `clusterawsadm` from the [AWS provider releases] a | |||
|
|||
The [clusterawsadm] command line utility assists with identity and access management (IAM) for [Cluster API Provider AWS][capa]. | |||
|
|||
> The AWS provider additionaly allows you to create EKS based clusters. If you don't plan to use EKS then please see the [disabling EKS documentation](https://cluster-api-aws.sigs.k8s.io/topics/eks/disabling.html) before proceeding. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this link returns 404
I don't think removing the providers is sufficient. Users may use It feels like we need the ability to specify a provider is only available until a specific version and then its deprecated. If a user tries to install a provider that is deprecated then it should be a no-op with a warning? |
Not sure if it helps, but clusterctl v0.4.0+ is unable to install v1alpha3 providers (you'll get an error). It can only upgrade v1alpha3 providers which have been previously installed with clusterctl v0.3.x |
Created #5152 to cover provider deprecation |
Does this need to be updated? |
@richardcase is this PR still required? |
@fabriziopandini - it is still required. I completely forgot about it. I will get it updated in the next few days. |
@richardcase friendly reminder :) |
@richardcase: PR needs rebase. 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. |
I'll get this updated today |
Closing in favour of #6344 |
What this PR does / why we need it:
With the graduation of the EKS functionality of CAPA, the controllers have been combined into the main AWS infrastructure provider. This change removed the separate
aws-eks
controlplane and bootstrap providers from clusterctl.Also the quick start docs have been updated with a note mentioning how to disable eks support.
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 kubernetes-sigs/cluster-api-provider-aws#2656