|
1 | 1 | +++
|
2 |
| -title = "Install Kubermatic Virtualization" |
| 2 | +title = "Installation" |
3 | 3 | date = 2025-06-28T12:07:15+02:00
|
4 | 4 | weight = 15
|
5 | 5 | +++
|
6 | 6 |
|
| 7 | +This chapter offers guidance on how to install Kubermatic Virtualization |
| 8 | + |
| 9 | +## Installing Kubermatic Virtualization with CLI |
| 10 | + |
| 11 | +Kubermatic Virtualization comes with an interactive installer, a CLI tool that helps administrators and users provision the entire platform easily. With just a few inputs, you can deploy and configure the stack in no time. |
| 12 | + |
| 13 | +{{% notice note %}} |
| 14 | +To get started with the CLI, you will first need a Kubermatic Virtualization license. This license grants you access to the necessary resources, including the CLI. Please [contact sales ](mailto:[email protected]) to obtain your license. |
| 15 | +{{% /notice %}} |
| 16 | + |
| 17 | +### **1. Navigating the Interactive CLI Installer** |
| 18 | + |
| 19 | +The Kubermatic Virtualization installer is an interactive CLI that guides you through the installation process with clear instructions and prompts for user input. Each page contains important information and features a help bar at the bottom to assist with navigation. |
| 20 | + |
| 21 | + |
| 22 | + |
| 23 | +--- |
| 24 | + |
| 25 | +### **2. Configuring the Network Stack** |
| 26 | + |
| 27 | +One of the foundational steps in setting up Kubermatic Virtualization is defining the network configuration. This step ensures that your virtual machines and containerized workloads have a dedicated IP range to operate within, similar to a default VPC. Proper network configuration is crucial for seamless communication and resource management. |
| 28 | + |
| 29 | + |
| 30 | +#### **Key Components** |
| 31 | +- **Network (CIDR)**: Specify the IP range where your virtual machines and containerized workloads will reside. This defines the subnet they will use by default. |
| 32 | +- **DNS Server**: Provide the DNS server address to ensure proper name resolution for your workloads. |
| 33 | +- **Gateway IP**: Define the gateway IP to facilitate network routing and connectivity. |
| 34 | + |
| 35 | + |
| 36 | + |
| 37 | +--- |
| 38 | + |
| 39 | +### **3. Configuring the Load Balancer Service** |
| 40 | + |
| 41 | +In this step, you can enable Kubermatic Virtualization’s default Load Balancer service, **MetalLB**, to simplify the creation of load balancers for your workloads. MetalLB is ideal for evaluation and non-production environments but should not be used in production scenarios without proper enterprise-grade solutions. |
| 42 | + |
| 43 | +#### **Key Steps** |
| 44 | +- **Enable MetalLB**: Toggle the checkbox to enable the Load Balancer service. |
| 45 | +- **Define IP Range**: If MetalLB is enabled, specify the IP range that will be used by the Load Balancer. |
| 46 | + |
| 47 | + |
| 48 | + |
| 49 | +By configuring these settings, you ensure that your workloads have access to a simple yet effective Load Balancer solution for testing and development purposes. Let’s move on to the next configuration step! |
| 50 | + |
| 51 | +--- |
| 52 | + |
| 53 | +### **4. Configuring Nodes** |
| 54 | + |
| 55 | +In this section, you will define the number of nodes in your Kubermatic Virtualization cluster and provide detailed information about each node, including their IP addresses, usernames, and SSH key paths. Accurate configuration is crucial for ensuring smooth communication and management of your cluster. |
| 56 | + |
| 57 | +#### **Step 1: Specify the Number of Nodes** |
| 58 | + |
| 59 | +The first step is to determine how many nodes you want in your cluster. This number will dictate the scale of your infrastructure and influence the subsequent configuration steps. |
| 60 | + |
| 61 | +- **Input**: Enter the total number of nodes you plan to use. |
| 62 | + |
| 63 | + |
| 64 | + |
| 65 | + |
| 66 | +#### **Step 2: Configure Each Node** |
| 67 | + |
| 68 | +After specifying the number of nodes, you will be prompted to configure each node individually. For each node, you need to provide the following details: |
| 69 | + |
| 70 | +1. **Node Address**: The IP address of the node. |
| 71 | +2. **Username**: The username used to access the node via SSH. |
| 72 | +3. **SSH Key Path**: The path to the SSH private key file used to authenticate with the node. |
| 73 | + |
| 74 | + |
| 75 | + |
| 76 | +Repeat this process for each node until all nodes are configured. |
| 77 | + |
| 78 | +#### **Why Accurate Configuration Matters** |
| 79 | +- **Node Addresses**: Ensure that the IP addresses are correct and reachable within your network. |
| 80 | +- **Usernames and SSH Keys**: Provide secure access to the nodes, enabling proper communication and management. |
| 81 | + |
| 82 | +By carefully configuring the number of nodes and providing accurate details for each node, you lay the foundation for a robust and manageable Kubermatic Virtualization environment. Let’s proceed to the next configuration step! |
| 83 | + |
| 84 | +--- |
| 85 | +### **5. Configuring the Storage CSI Driver** |
| 86 | + |
| 87 | +In this step, you will decide whether to use the default Container Storage Interface (CSI) driver provided by Kubermatic Virtualization. The default CSI driver is designed for evaluation and staging environments and is not recommended for production use. |
| 88 | + |
| 89 | + |
| 90 | + |
| 91 | +#### **Key Information** |
| 92 | +- **Default CSI Driver**: The default CSI driver (e.g., Longhorn) is included for testing purposes only. |
| 93 | +- **Purpose**: It provides baseline storage functionality during evaluation and staging phases. |
| 94 | +- **Recommendation**: For production environments, it is strongly advised to use a fully supported and robust storage solution. |
| 95 | + |
| 96 | +#### **Disclaimer** |
| 97 | +Please be advised: |
| 98 | +- The default CSI driver is **not intended or supported** for production environments. |
| 99 | +- Its use in production is at your own risk and is not recommended. |
| 100 | +- Kubermatic does not guarantee ongoing maintenance, reliability, or performance of the default CSI driver. |
| 101 | + |
| 102 | + |
| 103 | + |
| 104 | +By making an informed decision about the CSI driver, you ensure that your environment is configured appropriately for its intended purpose—whether it’s for testing or production. Let’s proceed to the next configuration step! |
| 105 | + |
| 106 | +--- |
| 107 | + |
| 108 | +### **6. Reviewing the Configuration** |
| 109 | + |
| 110 | +Before proceeding with the installation, it is crucial to review the full configuration to ensure all settings are correct. This step allows you to verify details such as Control Plane nodes, Worker nodes, network configurations, and other critical parameters. Once confirmed, the installation process will begin, and you will not be able to go back. |
| 111 | + |
| 112 | +#### **Key Information** |
| 113 | +- **Purpose**: Confirm that all configurations are accurate before applying them. |
| 114 | +- **Irreversible Step**: After confirming this page, the installation process will start, and changes cannot be made without restarting the entire setup. |
| 115 | + |
| 116 | +#### **What to Review** |
| 117 | +- **Cluster Nodes**: |
| 118 | + - Addresses |
| 119 | + - Usernames |
| 120 | + - SSH key file paths |
| 121 | + |
| 122 | +- **Other Configurations**: |
| 123 | + - Network settings (CIDR, DNS server, Gateway IP) |
| 124 | + - Load Balancer configuration (if enabled) |
| 125 | + - Storage CSI driver selection |
| 126 | + |
| 127 | + |
| 128 | + |
| 129 | + |
| 130 | +{{% notice warning %}} |
| 131 | +**No Going Back**: Once you confirm this page, the installation process will begin, and you cannot modify the configuration without starting over. |
| 132 | +By carefully reviewing the configuration, you ensure that your Kubermatic Virtualization environment is set up correctly from the start. Proceed with confidence when you’re ready! |
| 133 | + |
| 134 | +{{% /notice %}} |
| 135 | + |
| 136 | +--- |
| 137 | + |
| 138 | +### **8. Finalizing the Installation** |
| 139 | + |
| 140 | +Once you confirm the configuration, the installation process will begin, and you’ll be able to monitor its progress in real-time through detailed logs displayed on the screen. These logs provide transparency into each step of the deployment, ensuring you stay informed throughout the process. |
| 141 | + |
| 142 | +#### **What Happens During Installation** |
| 143 | +- **Progress Monitoring**: Watch as the installer provisions the Control Plane, Worker Nodes, and other components. |
| 144 | +- **Health Checks**: After deployment, the installer verifies that all parts of the stack are healthy and running as expected. |
| 145 | +- **Completion**: Upon successful installation, the installer will generate and display the **kubeconfig** file for your Kubermatic Virtualization cluster. |
| 146 | + |
| 147 | +### **Congratulations!** |
| 148 | +Your Kubermatic Virtualization environment is now up and running. With the kubeconfig file in hand, you’re ready to start managing your cluster and deploying workloads. Enjoy the power of seamless virtualization on Kubernetes! 🚀 |
0 commit comments