cluster-context-manager

Pass distributes and merges kubeconfigs and talosconfigs across workstations by acting as the cross-device distribution mechanism for context configurations. It enables secure sharing of kubectl and talosctl contexts between multiple machines.

Yes, you can synchronize talosctl contexts with kubectl contexts using unified context management. This coordination allows you to list, switch, and export both context types together, maintaining consistency across your Kubernetes and Talos OS environments.

The safest way to switch kubectl contexts is using a system that enforces auto-execute read-only tasks for listing and confirm-before-run for mutations. This ensures destructive context switches require explicit approval before execution.

You can clean up stale Kubernetes contexts using stale-context cleanup workflows that maintain configuration hygiene. This removes outdated entries from your kubeconfig, keeping your context list accurate and manageable across workstations.

Yes, kubecm supports exporting kubeconfigs for cross-workstation distribution by integrating with pass. This allows you to export, merge, and share kubectl and talosctl configurations securely across multiple devices.