search

davidfox87 / crossplane-eks-argocd-mlops

Sets up AWS EKS cluster and installs aws-load-balancer-controller so we can go ahead and install argocd and let it manage our applications
2 stars 0 forks source link

Fix helm provider config #2

Open davidfox87 opened 2 years ago

davidfox87 commented 2 years ago

See

https://github.com/crossplane-contrib/provider-helm/blob/master/examples/in-composition/composition.yaml#L147

davidfox87 commented 2 years ago

https://github.com/crossplane-contrib/provider-helm/tree/master/examples

davidfox87 commented 2 years ago

Basically the helm release does not need the provider and provider config ref girls. All you need to do is add the helm provider config ref and pass it the kubeconfig from the newly created cluster

davidfox87 commented 2 years ago

In management cluster

  1. Deploy the core Crossplane controller as well as CRDs

  2. Deploy Crossplane AWS provider-specific controller as well as CRDs

  3. Build an OCI image that represents a Crossplane configuration package that comprises the CompositeResourceDefinition and Composition types needed for provisioning an EKS cluster with a managed node group.

  4. Push this OCI image into a registry.

  5. Create an OCI image that represents a Crossplane configuration package that comprises the definition and composition for argocd and kubernetes application manifest for pointing to the GitHub repos.

  6. Deploy the Crossplane configuration packages using the OCI images.

  7. Finally, deploy an XR claims that triggers the provisioning of an EKS cluster and argocd.

davidfox87 commented 2 years ago

Specify actual application (front end, backend, mongodb/dynamodb) using kubevela