-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for AWS TransitGateway and TransitGatewayAttachment #363
Comments
@HerrmannHinz Thank you for describing your request in detail! 0.13 will be released this week, so I believe we can discuss this feature for 0.14. Though if you'd like to, you can contribute by implementing them by following our guides. We'd be more than happy to guide you along and merge the PR to upstream.
|
@muvaf wow nice, good news and thanks for the heads up. |
@HerrmannHinz please look at #831 tgw & tgw-vpc-attachment currently working in my PR - one open point with code-gen but in general it is working ;) |
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:
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.
The text was updated successfully, but these errors were encountered: