> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/frequently-asked-questions/can-i-add-a-second-master-to-an-existing-single-master-cluster.md).

# Can One Add a Second Master Node to an Already Configured Single Master Node Cluster?

## Problem

Cluster is running with only 1 master and 3 workers nodes. Is it possible to add another Master Node to this cluster?

## Environment

* Platform9 Managed Kubernetes - All Versions
* BareOS

## Answer

* You *cannot* add more master nodes to a cluster that's created with a single master node today without having a VIP (Virtual IP Address) associated to it. If cluster is created via U/I, this is achieved when using the `One-Click Cluster` or `Single Master Cluster` workflow.

<figure><img src="https://978681485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzyQCMA9ICq40g4F8hWJi%2Fuploads%2Fgit-blob-ebb2a6cc0d136e9e69b5a736c83d82f7e872221c%2F1643755895.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://978681485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzyQCMA9ICq40g4F8hWJi%2Fuploads%2Fgit-blob-9c2b6f769d5ebb2993c5451df4c443ab4fc917e3%2F1643756644.png?alt=media" alt=""><figcaption></figcaption></figure>

* You *can* scale up/down master nodes in a cluster having a single master node if it was created via U/I with the `Multi-Master Cluster` workflow where a VIP was provided at cluster creation time.

<figure><img src="https://978681485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzyQCMA9ICq40g4F8hWJi%2Fuploads%2Fgit-blob-27cbaed264b58c1cf6152480303101a7a0920eba%2F1643755945.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://978681485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzyQCMA9ICq40g4F8hWJi%2Fuploads%2Fgit-blob-6de665e44f3b1c120d5525216922b729e178e97c%2F1643757126.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://978681485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzyQCMA9ICq40g4F8hWJi%2Fuploads%2Fgit-blob-aaf1bed1427db855af9811e2b39a5b7775bfff53%2F1643757142.png?alt=media" alt=""><figcaption></figcaption></figure>

## Additional Information

* [Multimaster Architecture Platform9 Managed Kubernetes](https://docs.platform9.com/kubernetes/multimaster-architecture-platform9-managed-kubernetes/)
* If cluster is created using API, the `masterVipIpv4` and `masterVipIface` options will need to be passed to enable the option to scale master nodes later.
* Idea: [PMK8-I-260](https://ideas.platform9.com/ideas/PMK8-I-260)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmk/frequently-asked-questions/can-i-add-a-second-master-to-an-existing-single-master-cluster.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.