Allow injecting generic-token-kubeconfig secret name into yawol-cloud-controller #87
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 activegeneric-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.