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
Sealed-secrets need to know the namespace of the secret it's sealing.
It can get the namespace in 3 ways (in order of precedence)
from the -n|--namespace flag.
from the input secret's metadata.
from the kubeconfig file.
when the kubeconfig file is missing, we currently report a low-level error message from the k8s client library that doesn't help the user know what to do (and gets mistaken for #101)
The text was updated successfully, but these errors were encountered:
314: Improve error reporting in case of missing kubeconfig when inferring namespace r=mkmik a=mkmik
Closes#313
Co-authored-by: Marko Mikulicic <mkm@bitnami.com>
Sealed-secrets need to know the namespace of the secret it's sealing.
It can get the namespace in 3 ways (in order of precedence)
-n
|--namespace
flag.when the kubeconfig file is missing, we currently report a low-level error message from the k8s client library that doesn't help the user know what to do (and gets mistaken for #101)
The text was updated successfully, but these errors were encountered: