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

Allow injecting generic-token-kubeconfig secret name into yawol-cloud-controller #87

Closed
wants to merge 1 commit into from

Conversation

timebertt
Copy link
Member

With gardener v1.59.0+, there is no secret with the name generic-token-kubeconfig in the shoot control plane anymore (ref gardener/gardener@2d1aa09).
It has been replaced by an immutable secret with a suffix that is managed by the secrets manager (ref gardener/gardener#5510).
Extensions need to use the extensionscontroller.GenericTokenKubeconfigSecretNameFromCluster helper to retrieve the secret name of the currently active generic-token-kubeconfig secret name.
This needs to be injected into the yawol-cloud-controller deployment.

Accordingly, this PR changes the chart's structure and values to allow the injection of the secret name.

volumeMounts:
- mountPath: /var/run/secrets/gardener.cloud/shoot/generic-kubeconfig
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would like to remove the settings related to gardener from here.
Because yawol also works without gardener.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Valid point. In this case, I suggest closing this PR and removing all gardener-related values in a new PR.
The gardener extension should be responsible for injecting all gardener-related values in its controller.

@dergeberl
Copy link
Member

I added a issue for that #88

@dergeberl dergeberl closed this Jan 4, 2023
@timebertt timebertt deleted the generic-token-kubeconfig branch January 5, 2023 07:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants