Support for AWS TransitGateway and TransitGatewayAttachment #363
Description
What problem are you facing?
in my team we spin up clusters per default with internal load balancers + we have multiple clusters in different AWS accounts.
to make them available to the corp intranet + to VPN users etc. we are doing some transit gateway peering afterwards to make a cluster:
- availability to the internal network/routing
- ensure visibility to other parts of the infrastructure(CI/CID) in different AWS accounts
- enable the new cluster to also reach other pieces of infra. like CI/CD, services in other clusters or RDS instances
- also: we create a 2nd VPC in the same account which contains only RDS instances for better separation of concerns(well, that may not matter)
currently we need to run dedicated pipeline tasks after the cluster creation to apply terraform code which is doing the necessary TGW peering.
we are currently using SAP gardener as our cluster lifecycle management tool. gardener provides CRD's to CRUD the clusters.
argoCD is our tool to apply those manifests against a management(seed) cluster.
argoCD is also our tool of choice for applying additional landscape deployments like prometheus-operator, nginx etc.
now if we want to do the TGW peering we need to go one step back and involve some tooling(tekton pipelines) to apply the terraform code against the AWS account.
How could Crossplane help solve your problem?
would be super cool to also deploy those infrastructure changes/resources via argoCD and kubernetes manifests.
see: https://crossplane.slack.com/archives/C01718T2476/p1601571788009400
and: https://kubernetes.slack.com/archives/CD6U2V71N/p1601564676059800
i think you get the idea. :)
thanks in ahead for considering this feature request.