Skip to content

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

@iamahgoub

Description

@iamahgoub

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions