Remove GitOps and Monitoring from the platform reference

[irizzant]

What problem are you facing?

I'd like to adopt this reference platform for AWS but I find it difficult because it's currently addressing not only the creation of EKS clusters but also:

• GitOps management
• Monitoring tools

These, IMHO, should be removed from this Composition and let whoever wants to use this platform reference decide whether they want to use them or not and which tools they want to use.

For example, I'd rather use ArgoCD instead of Flux for GitOps and I found this issue #22 where I agree with this comment:

We could consider doing this in a separate dedicated reference platform, instead of only as part of platform-ref-aws.
@vfarcic may have already done a good example of this work with https://github.com/vfarcic/devops-toolkit-crossplane/blob/master/packages/gitops/argo-cd.yaml.

Having Flux in this reference platform leaves me with no choice but either use Flux or give up using this platform reference.

Same could be for the Monitoring tools.

Instead, other configurations like upbound-configuration-aws-database are still AWS realm and they still fit into this reference platform.

How could Upbound help solve your problem?

It would be great if GitOps and Monitoring could be removed from this platform reference.

[haarchri]

you can use parts of this platform-ref-aws - if you want to focus only on EKS Clusters you can use: https://github.com/upbound/configuration-aws-eks

we have also all gitops toolings seperate:

https://github.com/upbound/configuration-gitops-flux
https://github.com/upbound/configuration-gitops-argocd

an other option is to use caas:
https://github.com/upbound/configuration-caas

[haarchri]

the other option we have is to make it optional to deploy GitOps,Monitoring tooling as Input

[irizzant]

@haarchri as I was writing, other configurations like upbound-configuration-aws-database are still AWS realm and they still fit into this reference platform and could be of intrest for users.

I would use this platform reference if it wasn't for the GitOps and Monitoring tooling so I'd vote for the latter option.