Installing K10 on Other Kubernetes Distributions
Prerequisites
Before installing K10 on any other certified Kubernetes distributions not explicitly covered, please ensure that the install prerequisites are met.
Installing K10
To use K10 with a certified Kubernetes distribution installed on-premises or in another environment you can follow the general instructions below. This includes running K10 on distributions such as Rancher, PKS, and OKD (OpenShift Origin). Depending on your underlying infrastructure, you might also need to provide access credentials as specified elsewhere for public cloud providers.
$ helm install k10 kasten/k10 --namespace=kasten-io
Note
When using Cilium as the Container Network Interface (CNI), make sure to refer to the Kubernetes distribution's specific documentation for implementation details.
Validating the Install
To validate that K10 has been installed properly, the following
command can be run in K10's namespace (the install default is
kasten-io
) to watch for the status of all K10 pods:
$ kubectl get pods --namespace kasten-io --watch
It may take a couple of minutes for all pods to come up but all pods
should ultimately display the status of Running
.
$ kubectl get pods --namespace kasten-io
NAMESPACE NAME READY STATUS RESTARTS AGE
kasten-io aggregatedapis-svc-b45d98bb5-w54pr 1/1 Running 0 1m26s
kasten-io auth-svc-8549fc9c59-9c9fb 1/1 Running 0 1m26s
kasten-io catalog-svc-f64666fdf-5t5tv 2/2 Running 0 1m26s
...
In the unlikely scenario that pods that are stuck in any other state, please follow the support documentation to debug further.
Validate Dashboard Access
By default, the K10 dashboard will not be exposed externally.
To establish a connection to it, use the following kubectl
command
to forward a local port to the K10 ingress port:
$ kubectl --namespace kasten-io port-forward service/gateway 8080:80
The K10 dashboard will be available at http://127.0.0.1:8080/k10/#/.
For a complete list of options for accessing the Kasten K10 dashboard through a LoadBalancer, Ingress or OpenShift Route you can use the instructions here.