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
Starting with Kubernetes v1.30, the feature flag for Structured Authentication Configuration is activated by default. We are currently doing a PoC at our company, as we have the need to use several audiences and would of course like to provide the result upstream as PR again.
As described in the blog entry, the previous kube-apiserver config flags --oidc-* are still supported but not at the same time as the config file. As also described in the blog entry, it is recommended to rely more on the structured config file in the future and it is also possible to configure the same behaviour with the new variant as with the existing (--oidc-*) flags.
Hence my question:
Should we implement the implementation completely on the structured config file right away or wait and currently offer 2 configuration paths, namely either via the existing -oidc-* flags and alternatively if the user activates it on structured config?
The text was updated successfully, but these errors were encountered:
What would you like to be added
I want to add structured authentication configuration as described here:
Why is this needed
Starting with Kubernetes v1.30, the feature flag for Structured Authentication Configuration is activated by default. We are currently doing a PoC at our company, as we have the need to use several audiences and would of course like to provide the result upstream as PR again.
As described in the blog entry, the previous kube-apiserver config flags --oidc-* are still supported but not at the same time as the config file. As also described in the blog entry, it is recommended to rely more on the structured config file in the future and it is also possible to configure the same behaviour with the new variant as with the existing (--oidc-*) flags.
Hence my question:
Should we implement the implementation completely on the structured config file right away or wait and currently offer 2 configuration paths, namely either via the existing -oidc-* flags and alternatively if the user activates it on structured config?
The text was updated successfully, but these errors were encountered: