Create Single Node BareOS Cluster

This article describes the creation of a single node on-premises Kubernetes cluster using PMK.

We recommend reading What is BareOS for an understanding of BareOS and BareOS Cluster Architecture before proceeding with this document.

The PMK one-click cluster creation wizard allows you to create a single node PMK cluster very quickly. The single cluster node becomes both the master and worker node for the cluster, and has etcd deployed on that node.

Note that the cluster will not be highly available and should not be used for production workloads. Only use single master single node clusters for dev/test use cases where you can accommodate cluster downtime due to the single node going down.

Pre-requisites

Create BareOS Single Node Cluster Using UI

To create a single node PMK cluster:

  • Navigate to the PMK UI Infrastructure -> Clusters - > Create Cluster and choose 'create cluster' to launch the cluster creation wizard.
  • Select BareOS Virtual Machine or BareOS Physical Servers option depending on where you are creating your BareOS cluster.
  • Click on the 'One-click Cluster' button in the wizard
  • Give the cluster a memorable name like 'my-cluster'
  • Choose your Kubernetes version (if you are unsure which version to pick then always choose the latest)
  • The 'Select a node' section of the wizard will initially be empty. This is because you need to download and install the Platform9 CLI on your node so it can connect to the PMK management plane and show up in your wizard.
  • To achieve this, download and install the PMK CLI on your node by running the following command on the node.
Download CLI Setup Script
Copy
  • The command will install the CLI
  • Now run the config set command to configure the CLI to connect to and use your PMK deployment.
CLI Configuration
Copy
CLI Configuration Example
Copy

Note: The default values for Region and Tenant should suffice for most PMK Free Tier users. PMK Free Tier does not have the feature enabled to create multiple Regions. So the Region field should always be left to the default value. Change the value of the Tenant field only if you created a different Tenant in PMK and you are creating a cluster within that tenant.

For PMK Enterprise users, specify the right value for the Region and Tenant within which you are creating your cluster. (Specified by the drop down selectors at the top right of your PMK UI nav bar)

  • Now run the CLI prep-node command to prepare the node with required pre-requisites.
Prepare Node
Copy
  • The prep-node command will perform prerequisite checks for your node. If any checks fail, you will receive an output similar to the following.
Prepare Node - Pre-Requisite Check(s) Failed
Copy

It is highly recommended that you meet all of the pre-requisites or else you may experience degraded performance among scheduled pods and/or other unforeseen issues.

If you encounter the error: Failure to prepare node, please review the pf9ctl log file for additional context.

Enterprise – Please submit a Support Request with the log attached and our team will review and work with you to onboard the node.

PMK Free Tier – Feel free to reach out to us on Slack or our Community forum to solicit some general advice and guidance with relation to the error you're seeing.

Bash
Copy
  • If the prep-node command succeeds, you are now ready to create your single node cluster using PMK UI.
  • Navigate back to the PMK UI one click cluster creation wizard. Your node should now show up in the wizard.
  • Give you cluster a name. And select Kubernetes version for your cluster. If you are unclear about this, we recommend selecting the highest listed numeric version.
  • ClickComplete to finalize and deploy the cluster!
  • You PMK Cluster is now deployed.
  • Following is a description of the input properties, their default values set as part of the one-click cluster creation wizard, and their meaning, for your information only.
Input parameterDescriptionDefault value
Containers CIDRThe IP range that Kubernetes uses to configure containers (pods) deployed by Kubernetes10.20.0.0/22
Services CIDRThe IP range that Kubernetes uses to configure services deployed by Kubernetes10.21.0.0/22
CNIThe CNI used for this cluster.Calico
IP in IP Encapsulation Mode (Calico)Encapsulation mode for Calico CNI. See Calico CNI for details on the network parameters.Always
NAT Outgoing (Calico)NAT mode for Calico CNIEnabled
Block sizeBlock sized used by Calico CNI26
MTU sizeMTU size used by Calico CNI1440
PrivilegedAllows you to run containers that require privileged mode on this cluster.Enabled
Enable workloads on masterWhether a master node should also run workloads. Enabled so we can create a single node cluster.Enabled
ETCD BackupWhether etcd data will be backed upEnabled
Storage PathLocation on the node where the etcd data will be backed up/etc/pf9/etcd-backup
Backup Interval (Minutes)How often the etcd data will be backed up1440 minutes (1 day)

Create Single Node BareOS Cluster Using REST API

You can also create a single node BareOS Kubernetes cluster using the PMK (Qbert) REST API.

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard