Support and Troubleshooting¶
If you have questions or need support, please send an email to our support team.
Supported Kubernetes Versions¶
K10 currently supports the following certified Kubernetes distributions and OpenShift versions:
Kubernetes (including managed services)¶
Snapshots created using the v1alpha1 Snapshot CRDs are incompatible with the v1beta1 Snapshot CRD. Please contact your CSI storage provider for an upgrade path. However, any backups taken using the v1alpha1 CRD functionality will still be available for restore.
K10 4.0.5 or earlier may still run on older, unsupported versions of Kubernetes and OpenShift. Please install K10 4.0.5 on OpenShift 4.2 or earlier and Kubernetes 1.15 or earlier.
Gathering Debugging Information¶
If you run into problems with K10, please run these commands on your
cluster as a first step to get information to support. The script
assumes that your default
kubectl context is pointed to the
cluster you have installed K10 on and that K10 is installed in
$ curl -s https://docs.kasten.io/tools/k10_debug.sh | \ bash;
By default, the debug script will generate a compressed archive file
k10_debug_logs.tar.gz which will have separate log files
for K10 services.
To gather K10's Prometheus statistics the script will create a port forward
using the port
9090 in the host where the script is executed.
If you installed K10 in a different namespace, want to log to a different file or want to use a different local host port to gather statistics, the options to the debug script are:
$ curl -s https://docs.kasten.io/tools/k10_debug.sh | \ bash -s <k10-namespace> <logfile-name> <localhost port>;
Application Debug Information¶
If you are having issues with a particular application, please also gather the following information.
# Get Application Information $ kubectl get pvc -oyaml --namespace <APP NAMESPACE> $ kubectl api-resources --verbs=list --namespaced -o name | \ xargs -n 1 kubectl get --show-kind --ignore-not-found --namespace <APP NAMESPACE>
Please also get the Helm status:
# If deployed via Helm $ helm status <RELEASE NAME> --namespace=<APP NAMESPACE>
k10tools binary has commands that can help with validating
if a cluster is setup correctly before installing K10 and for
debugging K10's micro services.
The latest version of
k10tools can be found
It has binaries that are compatible with both
To learn more about this, see K10 Tools.