> For the complete documentation index, see [llms.txt](https://learn.farizizwan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.farizizwan.com/devops-and-devsecops/kubernetes/poc-lab/high-availability-portable-mini-kubernetes-data-center-with-k3s/lab-3-multi-master-k3s-kubeconfig-files-for-smooth-accessibility.md).

# Lab 3: Multi Master K3s kubeconfig files for smooth accessibility

Scenario:

We have multiple master nodes and we want to ensure that our operation using `kubectl` in our local machine is smooth and uninterrupted.

First, create the necessary kubeconfig files and add the configuration data into it like the following:

<figure><img src="/files/imnuzcUgGoqg4Qvzxya3" alt=""><figcaption><p>k3s-master-node0* is the file that contains the configuration data required to access the Kubernetes clusters</p></figcaption></figure>

Then we modify our shell profile. Depending on your setup, as for me, I'm using [zsh](https://ohmyz.sh/) as my shell. Therefore, I will modify the `.zshrc` file as below:

<pre class="language-bash"><code class="lang-bash"><strong>#My Onprem K8s master nodes
</strong><strong>export CONFIG_K3S_MASTER_NODE01=$HOME/.kube/k3s-master-node01
</strong>export CONFIG_K3S_MASTER_NODE02=$HOME/.kube/k3s-master-node02
export CONFIG_K3S_MASTER_NODE03=$HOME/.kube/k3s-master-node03

#Merge all the configs
export KUBECONFIG=$CONFIG_K3S_MASTER_NODE01:$CONFIG_K3S_MASTER_NODE02:$CONFIG_K3S_MASTER_NODE03:$CONFIG_MINIKUBE
</code></pre>

Finally, you may get the results just like below:

<figure><img src="/files/6qh0eB5Oq8Tznb0UVgdH" alt=""><figcaption><p>Notice there were multiple context displayed for my master nodes</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.farizizwan.com/devops-and-devsecops/kubernetes/poc-lab/high-availability-portable-mini-kubernetes-data-center-with-k3s/lab-3-multi-master-k3s-kubeconfig-files-for-smooth-accessibility.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.