In order to install Tungsten Dashboard in Kubernetes you will require a staging host to initiate the installation, with a minimum of the following requirements:
kubectl client - Minimum version v1.29.3
kubectl server - Minimum version v1.30.0
helm cient - Minimum version v3.15.0
OPTIONAL: kind should be installed if you wish to host a local kubernetes cluster.
CLI tools such as AWS or GCP cli tools, or equivalent for managing and accessing your cloud environment.
Additionally your cluster must have an access to the docker image file provided in the installation package. Our recommendation is for you to host a private registry of your own in order to manage the images in a centralized manner. This is accepted as the best practice for Kubernetes.
For steps on uploading the images to a Container Registry, see Section 2.3.4, “Upload tungsten-dashboard to Container Registry”
Alternatively you can upload the images as local images directly to the cluster you are using and rely on the local registry of the cluster, please bear in mind how you achieve this depends on the details of your cluster. In addition you should alter the image pull policies in the provided yaml files to match the cluster configuration.
At this time Continuent is not hosting the docker image in any publicly-available registry. Please verify your access to the image before attempting an installation via Helm.
For the kubectl installation steps, latest versions and up to date documentation please follow the official kubectl documentation
To check the installation:
shell> kubectl version --clientFor the helm installation steps, latest versions and up to date documentation please follow the official helm documentation
To check the installation:
shell> helm versionDeploying Tungsten Dashboard via the Kubernetes deployment methods, will, naturally also require access to a Kubernetes Cluster. Tungsten Dashboard will deploy into any Kubernetes Cluster solution such as Amazon EKS or Google GKE. Additionally, you could also deploy into a local kubernetes cluster, such as kind
This documentation does not cover the installation and configuration of a Kubernetes Cluster - for further details should be referred to the consult the Kubernetes Documentation
Once access to a cluster is complete, you will need to set the kubectl context. For example, the following command can be used if you are installing into Amazon EKS using the AWS CLI tools:
shell> aws eks --region <region-code> update-kubeconfig --name <cluster-name>For further information, consult the documentation appropriate for you Kubernetes provider. The links for Google and Amazon are below for convenience.
In order to deploy the Tungsten Dashboard to any remote environment you must have a container registry available and the images that are provided in this installation package uploaded into it.
To upload an image to, for example, Amazon ECR (Elastic Container Registry) you can use a local Docker installation like this:
Load the image into your local Docker daemon
shell> docker load -i images/tungsten-dashboard_{{ version_postfix }}-linux_{{ arch }}.tarThen, login to Amazon Elastic Container Registry:
shell> aws ecr get-login-password --region <region> | docker login --username AWS --password-stdin <registry ID>Finally, tag and push local docker image to remote registry
shell>docker tag tungsten-dashboard:{{ version_postfix }} {{ registry ID }}/tungsten-dashboard:{{ version_postfix }}shell>docker push {{ registry ID }}/tungsten-dashboard:{{ version_postfix }}
Bear in mind that the commands used to achieve this may change depending on the platform you're using. Once the cluster has access to the
image via a registry or some other means, start by modifying the values.yaml file for your environment specific values.
These include: clusters list, application configuration, users list and potentially ingress configuration.
As a docker container registry you can use any from the public service providers. The most popular are: