Querying Toolset and Confidential Pod versions
Querying versions of the Anjuna Kubernetes Toolset for AWS EKS and Confidential Pods is essential for tracking deployments, planning upgrades, ensuring compliance, and troubleshooting issues. This page shows how to find the versions of the relevant Anjuna components.
Inspecting the version of the Anjuna Toolset
To retrieve the version of the Anjuna Toolset that is globally installed to a cluster and its components, inspect the toolset deployment using Helm.
In the example below, the Anjuna Toolset is installed in the namespace anjuna-system.
Change accordingly to match your own cluster:
$ helm list --namespace anjuna-system
The output will resemble the following:
NAME NAMESPACE STATUS VERSION APP VERSION
anjuna-tools anjuna-system deployed anjuna-tools-1.55.0001 1.55.0001
As observed in the output above,
the Anjuna Toolset was installed with the name anjuna-tools and is of version 1.55.0001.
Inspecting the version of a running Confidential Pod
There are two versions that are relevant for a currently running Confidential Pod:
-
The version of the Anjuna Launcher Pod that launches the Anjuna Nitro Enclave. It corresponds to the version of the Anjuna tools used to launch the EIF. It usually matches the version of the Anjuna Toolset globally installed to the cluster, but can also differ in existing Confidential Pods after a Toolset upgrade.
-
The version of the Anjuna Runtime running inside the enclave. This Runtime version is set when building the EIF using the Anjuna CLI.
To query the version of the Anjuna Launcher of a Confidential Pod, use kubectl:
$ kubectl logs my-confidential-pod | grep anjuna-k8s-launcher | grep -oP 'version \K[\d.-]+(?:\w+)?'
1.55.0001
The version of the Anjuna Runtime running inside the enclave can also be retrieved using kubectl:
$ kubectl logs my-confidential-pod | grep run-container-process | grep -oP 'version \K[\d.-]+(?:\w+)?'
1.51.0002