You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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.
The text was updated successfully, but these errors were encountered:
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:
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. AKustomization
has to be added under flux folder of the management clusterrepos/gitops-system/cluster/mgmt/
for reconciling the installation manifests.repos/gitops-system/tools-config/crossplane-eks-composition/
; the interface (XRD) should be kept the same.The text was updated successfully, but these errors were encountered: