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
We shouldn't update the default namespace. I wonder if there is a way to influence the default namespace with an environment variable? Then we would be able to not append it in every single statement over and over which was the reason I opted to update the default namespace.
In case there isn't such feature, then perhaps we can create an alias or similar for kubectl to be kubectl -n <namespace> and solve it like that?
I'd very much like to avoid a massive cluttering of -n <namespace>.
We shouldn't update the default namespace. I wonder if there is a way to influence the default namespace with an environment variable? Then we would be able to not append it in every single statement over and over which was the reason I opted to update the default namespace.
In case there isn't such feature, then perhaps we can create an alias or similar for
kubectl
to bekubectl -n <namespace>
and solve it like that?I'd very much like to avoid a massive cluttering of
-n <namespace>
.Related
kubectl
respect KUBECTL_{CONTEXT,NAMESPACE} environment variables kubernetes/kubernetes#27308The text was updated successfully, but these errors were encountered: