<p>kubectl switches the context the moment we create a new cluster. since I'm trying to mimic a client server architecture, I need to view rolling logs (<code>kubectl logs pod-id</code>) from both sides (server cluster and agents cluster). Right now, I'm switching context using <code>kubectl config use-context</code> between them, is that right method? is there a way to keep more than one context active at the same time?</p>

<p>You can only have one active context at a time. But kubectl accepts a <code>--context</code> argument (see <a href="https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/#define-clusters-users-and-contexts" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/#define-clusters-users-and-contexts</a>) with every command so that you can explicitly pass in the context for each command. </p>
