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
Describe the bug
When using Bridge to Kubernetes to debug a service on k8s locally, the secrets are not resolved. So appsettings have a literal value of 'my-secret@azurekeyvault'.
A work-around is to disable the loading of environment variables in the program.cs and use local appsettings/usersecret instead.
To Reproduce
Use Bridge to Kubernetes with a service that has a deployment which depends on akv2k8s secrets.
Expected behavior
It would be nice if the secrets were populated, though I can imagine it's not that straightforward.
The text was updated successfully, but these errors were encountered:
Components and versions
Select which component(s) the bug relates to with [X].
[ ] Controller, version:
x.x.x
(docker image tag)[X] Env-Injector (webhook), version:
1.3.0
(docker image tag)[ ] Other
Describe the bug
When using Bridge to Kubernetes to debug a service on k8s locally, the secrets are not resolved. So appsettings have a literal value of 'my-secret@azurekeyvault'.
A work-around is to disable the loading of environment variables in the program.cs and use local appsettings/usersecret instead.
To Reproduce
Use Bridge to Kubernetes with a service that has a deployment which depends on akv2k8s secrets.
Expected behavior
It would be nice if the secrets were populated, though I can imagine it's not that straightforward.
The text was updated successfully, but these errors were encountered: