Terraform removal for infrastructure controller #411
Labels
kind/enhancement
Enhancement, improvement, extension
kind/roadmap
Roadmap BLI
kind/technical-debt
Something that is only solved on the surface, but requires more (re)work to be done properly
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
platform/azure
Microsoft Azure platform/infrastructure
priority/2
Priority (lower number equals higher priority)
How to categorize this issue?
/kind technical-debt
/priority 2
/platform azure
What would you like to be added:
Project Gardener is using Terraform since beginning to create, manage and delete the underlying infrastructure for Shoot clusters (e.g. VPCs, subnets, nat gateways etc.).
As Terraform was great in the beginning to get started, we today experience more and more issues with it.
For example:
Infrastructure
creation and deletion processTherefore we wanted to start dismantling the Terraform usage in this extension and start to adopt provider specific Go SDKs as replacement.
Ideally all Terraform managed resources should be already tracked in the status section of the
Infrastructure
resource.In case there are resources not tracked in the status then it need to be populated first before the Go SDK clients can take over.
This issue is meant to track progress of the Terraform removal on this extension.
Why is this needed:
See above.
/roadmap cloud
The text was updated successfully, but these errors were encountered: