Install Kommander in a Non-air-gapped Environment
Install the Kommander component of DKP in non-air-gapped environments.
Prerequisites
Ensure you have reviewed all Prerequisites for Install.
Ensure you have a default StorageClass.
Note down the name of the cluster, where you want to install Kommander. If you do not know it, use
kubectl get clusters -A
to display it.
Create your Kommander Installer Configuration File
Set the environment variable for your cluster:
CODEexport CLUSTER_NAME=<your-management-cluster-name>
Copy the
kubeconfig
file of your Management cluster to your local directory:CODEdkp get kubeconfig -c ${CLUSTER_NAME} > ${CLUSTER_NAME}.conf
Create a configuration file for the deployment:
CODEdkp install kommander --init > kommander.yaml
If required, customize your
kommander.yaml
.
See Kommander Customizations for customization options. Some of them include:Custom Domains and Certificates
HTTP proxy
External Load Balancer
GPU utilization, etc.
If required: If your cluster uses a custom AWS VPC and requires an internal load-balancer, set the
traefik
annotation to create an internal-facing ELB:CODE... apps: traefik: enabled: true values: | service: annotations: service.beta.kubernetes.io/aws-load-balancer-internal: "true ...
Expand one of the following sets of instructions, depending on your license and application environments:
If your environment uses HTTP/HTTPS proxies, you must include the flags --http-proxy
, --https-proxy
, and --no-proxy
and their related values in this command for it to be successful. More information is available in Configuring an HTTP/HTTPS Proxy.
Tips and recommendations
The --kubeconfig=${CLUSTER_NAME}.conf
flag ensures that you install Kommander on the correct cluster. For alternatives, see Provide Context for Commands with a kubeconfig File.
Applications can take longer to deploy, and time out the installation. Add the --wait-timeout <time to wait>
flag and specify a period of time (for example, 1h
) to allocate more time to the deployment of applications.
If the Kommander installation fails, or you wish to reconfigure applications, rerun the install
command to retry.
Tips and recommendations
The
--kubeconfig=${CLUSTER_NAME}.conf
flag ensures that you install Kommander on the correct cluster. For alternatives, see Provide Context for Commands with a kubeconfig File.Applications can take longer to deploy, and time out the installation. Add the
--wait-timeout <time to wait>
flag and specify a period of time (for example,1h
) to allocate more time to the deployment of applications.If the Kommander installation fails, or you wish to reconfigure applications, rerun the
install
command to retry.
Next Step:
See (2.6) DKP Insights if you want to enable a solution that detects current and future anomalies in workload configurations or Kubernetes clusters.