Skip to content
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

Terraform removal for infrastructure controller #357

Open
dkistner opened this issue Dec 2, 2021 · 0 comments
Open

Terraform removal for infrastructure controller #357

dkistner opened this issue Dec 2, 2021 · 0 comments
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/gcp Google cloud platform/infrastructure priority/2 Priority (lower number equals higher priority)
Milestone

Comments

@dkistner
Copy link
Member

dkistner commented Dec 2, 2021

How to categorize this issue?
/kind technical-debt
/priority 2
/platform gcp

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:

  • Less control over the Infrastructure creation and deletion process
  • Therefore inflexibility to create infrastructure remedies if they are required (depend on upstream Terraform fixes)
  • Inability to import resources in the Terraform state in the Gardener context (Terraformer does not support this)
  • Terraform provider version incompatibilities
  • State lost issues

Therefore 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
/milestone 2022-Q1

@dkistner dkistner added the kind/enhancement Enhancement, improvement, extension label Dec 2, 2021
@gardener-robot gardener-robot added this to the 2022-Q1 milestone Dec 2, 2021
@gardener-robot gardener-robot added kind/technical-debt Something that is only solved on the surface, but requires more (re)work to be done properly platform/gcp Google cloud platform/infrastructure priority/2 Priority (lower number equals higher priority) roadmap/cloud labels Dec 2, 2021
@dkistner dkistner modified the milestones: 2022-Q1, 2022-Q3 May 24, 2022
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Nov 21, 2022
@gardener-robot gardener-robot added kind/roadmap Roadmap BLI and removed roadmap/cloud labels Mar 23, 2023
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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/gcp Google cloud platform/infrastructure priority/2 Priority (lower number equals higher priority)
Projects
None yet
Development

No branches or pull requests

2 participants