You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
Right now, when using provider-env to login to the Cloud provider CLI, gardenctl fetches the credentials based on the shoot's secretBindingName
However, with GEP-26, a new way of authenticating using CredentialsBindings has been added. The end goal of CredentialsBindings is to enable thrust based authentication (which would probably break the provider-env feature anyway), however it also supports secrets referencing (similar to the way secretBindings works, but the format is a bit different, see https://github.com/gardener/gardener/blob/master/example/80-credentialsbinding.yaml)
Why is this needed:
Support the case where we are using CredentialsBindings that is still referencing a secret, aka not break the feature.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
Right now, when using
provider-env
to login to the Cloud provider CLI, gardenctl fetches the credentials based on the shoot'ssecretBindingName
gardenctl-v2/pkg/cmd/providerenv/options.go
Lines 169 to 186 in 41e47d4
However, with GEP-26, a new way of authenticating using
CredentialsBindings
has been added. The end goal ofCredentialsBindings
is to enable thrust based authentication (which would probably break the provider-env feature anyway), however it also supportssecrets
referencing (similar to the waysecretBindings
works, but the format is a bit different, see https://github.com/gardener/gardener/blob/master/example/80-credentialsbinding.yaml)Why is this needed:
Support the case where we are using
CredentialsBindings
that is still referencing a secret, aka not break the feature.The text was updated successfully, but these errors were encountered: