Is your feature request related to a problem? Please describe.
The webhook currently requires either auth-token or auth-key-path. This prevents using it on STACKIT Kubernetes Engine (SKE) with Workload Identity, where credentials are provided through a projected service-account token rather than a static token or key file.
Describe the solution you'd like
Support Workload Identity Federation similar to how stackit-cli and the terraform provider are already doing it.
Describe alternatives you've considered
As our DNS zone is deployed in a different project than the SKE cluster, we cannot use the SKE DNS extension.
Search
Code of Conduct
Additional context
No response
Is your feature request related to a problem? Please describe.
The webhook currently requires either
auth-tokenorauth-key-path. This prevents using it on STACKIT Kubernetes Engine (SKE) with Workload Identity, where credentials are provided through a projected service-account token rather than a static token or key file.Describe the solution you'd like
Support Workload Identity Federation similar to how
stackit-cliand the terraform provider are already doing it.Describe alternatives you've considered
As our DNS zone is deployed in a different project than the SKE cluster, we cannot use the SKE DNS extension.
Search
Code of Conduct
Additional context
No response