2A Installation
Requirements#
Project 2A requires a Kubernetes cluster. It can be of any type and will become the 2A management cluster.
If you don't have a Kubernetes cluster yet, consider using k0s.
The following instructions assume:
- Your
kubeconfig
points to the correct Kubernetes cluster. - You have Helm installed.
- You have kubectl installed.
Helpful Tools#
It may be helpful to have the following tools installed:
Installation via Helm#
helm install hmc oci://ghcr.io/mirantis/hmc/charts/hmc --version 0.0.4 -n hmc-system --create-namespace
Verification#
The installation takes a couple of minutes until 2A and its subcomponents are fully installed and configured.
Verify the installation by checking all the pods in the hmc-system
namespace
with the following command:
kubectl get pods -n hmc-system
The output is similar to:
NAME READY STATUS
azureserviceoperator-controller-manager-86d566cdbc-rqkt9 1/1 Running
capa-controller-manager-7cd699df45-28hth 1/1 Running
capi-controller-manager-6bc5fc5f88-hd8pv 1/1 Running
capv-controller-manager-bb5ff9bd5-7dsr9 1/1 Running
capz-controller-manager-5dd988768-qjdbl 1/1 Running
helm-controller-76f675f6b7-4d47l 1/1 Running
hmc-cert-manager-7c8bd964b4-nhxnq 1/1 Running
hmc-cert-manager-cainjector-56476c46f9-xvqhh 1/1 Running
hmc-cert-manager-webhook-69d7fccf68-s46w8 1/1 Running
hmc-cluster-api-operator-79459d8575-2s9jc 1/1 Running
hmc-controller-manager-64869d9f9d-zktgw 1/1 Running
k0smotron-controller-manager-bootstrap-6c5f6c7884-d2fqs 2/2 Running
k0smotron-controller-manager-control-plane-857b8bffd4-zxkx2 2/2 Running
k0smotron-controller-manager-infrastructure-7f77f55675-tv8vb 2/2 Running
source-controller-5f648d6f5d-7mhz5 1/1 Running
If you have fewer pods, give 2A more time to reconcile all the pods.
As a second verification, check that the example ClusterTemplate
objects have
been installed and are valid:
kubectl get clustertemplate -n hmc-system
The output is similar to:
NAME VALID
aws-eks-0-0-2 true
aws-hosted-cp-0-0-3 true
aws-standalone-cp-0-0-3 true
azure-hosted-cp-0-0-3 true
azure-standalone-cp-0-0-3 true
vsphere-hosted-cp-0-0-3 true
vsphere-standalone-cp-0-0-3 true
Next Step#
Now you can configure your Infrastructure Provider of choice and create your first Managed Cluster.
Jump to any of the following Infrastructure Providers for specific instructions: