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

aws-custom-route-controller gets enabled on Shoot creation and gets removed in the subsequent Shoot reconciliation #619

Closed
ialidzhikov opened this issue Sep 26, 2022 · 0 comments · Fixed by #622
Labels
area/control-plane Control plane related kind/bug Bug platform/aws Amazon web services platform/infrastructure priority/1 Priority (lower number equals higher priority) status/closed Issue is closed (either delivered or triaged)

Comments

@ialidzhikov
Copy link
Member

How to categorize this issue?

/area control-plane
/kind bug
/platform aws
/priority 1

What happened:
On Shoot creation the ControlPlane gets mutated with:

    providerConfig:
      apiVersion: aws.provider.extensions.gardener.cloud/v1alpha1
      cloudControllerManager:
        useCustomRouteController: true

On a subsequent Shoot reconciliation, the gardenlet sets again the providerConfig field and the ControlPlane is reverted to:

    providerConfig:
      apiVersion: aws.provider.extensions.gardener.cloud/v1alpha1
      kind: ControlPlaneConfig

and the aws-custom-route-controller gets disabled again.

The issue is also described in gardener/gardener#6703 (comment).

What you expected to happen:
Not the above one.

How to reproduce it (as minimally and precisely as possible):
See above.

Anything else we need to know?:

Environment:

  • Gardener version (if relevant): v1.38.1
  • Extension version:
  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration:
  • Others:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/control-plane Control plane related kind/bug Bug platform/aws Amazon web services platform/infrastructure priority/1 Priority (lower number equals higher priority) status/closed Issue is closed (either delivered or triaged)
Projects
None yet
2 participants