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

[FEATURE] Migrate to the official Upbound AWS provider (EKS cluster) #91

Open
iamahgoub opened this issue May 20, 2024 · 0 comments
Open

Comments

@iamahgoub
Copy link
Contributor

iamahgoub commented May 20, 2024

This issue is for migrating from community AWS provider to the official Upbound AWS provider. The scope of this issue is the EKS cluster composition.

Changes:

  1. Install the official Upbound AWS provider -- this requires changes at repos/gitops-system/tools/crossplane/ i.e. adding the providers installation manifests. Note that the Upbound provider is broken down into service-level providers, and given that EKS cluster creation involves creating several cloud resources, several providers will be required -- this include: provider-aws-eks, provider-aws-vpc, provider-aws-ec2, and provider-aws-iam. A Kustomization has to be added under flux folder of the management cluster repos/gitops-system/cluster/mgmt/ for reconciling the installation manifests.
  2. Updating EKS composition to use the MRs of the new providers -- this requires changes at repos/gitops-system/tools-config/crossplane-eks-composition/; the interface (XRD) should be kept the same.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant