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
When using secretNamespace in a container volume definition, the driver seems only to be looking for the secret in the same namespace where the container is deployed to. If it is different it will not work.
This might be a deisgn decision to align with K8S scoping of secrets. If that is the case, I believe the docs should be updated. And maybe even the error message improved.
The text was updated successfully, but these errors were encountered:
What happened:
When using secretNamespace in a container volume definition, the driver seems only to be looking for the secret in the same namespace where the container is deployed to. If it is different it will not work.
i.e.
This might be a deisgn decision to align with K8S scoping of secrets. If that is the case, I believe the docs should be updated. And maybe even the error message improved.
The text was updated successfully, but these errors were encountered: