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
kcp has a unit of isolation called "workspace", which is essentially a virtual Kubernetes API sever on a specific subpath of the URL.
Support for it could do a couple of things that kubectl-workspace, the current official kubectl plugin, can't do yet:
keep track of the "base url" as metadata.
allow to list and switch workspaces.
have better context naming than kubectl-workspace, which uses the context name as a marker for "current" and "previous" contexts.
Some of this I'd expect to upstream into the plugin at some point (if other maintainers agree), but kubeconfig-bikeshed can be a second implementation and/or playground to try things out.
The text was updated successfully, but these errors were encountered:
kcp has a unit of isolation called "workspace", which is essentially a virtual Kubernetes API sever on a specific subpath of the URL.
Support for it could do a couple of things that
kubectl-workspace
, the current official kubectl plugin, can't do yet:kubectl-workspace
, which uses the context name as a marker for "current" and "previous" contexts.Some of this I'd expect to upstream into the plugin at some point (if other maintainers agree), but kubeconfig-bikeshed can be a second implementation and/or playground to try things out.
The text was updated successfully, but these errors were encountered: