You can connect your GKE cluster to Uniskai by installing the Uniskai agent.
Configuring Read-Only Access
The Uniskai Agent brings platform features to Kubernetes clusters without compromising security. With the “Read-only” connection you can get:
K8s architecture view in Cloudmap and Cloudnet;
View Cloudsitter recommendations;
Step 1 - Navigate to Cloudk8s tab
Select the Cloudk8s tab on the left menu.
Step 2 - Open cluster connection modal
Click on the switcher of the desired cluster.
The modal window appears.
Step 3 - Select connection type
Click on "Read only" button.
Step 4 - Copy connection command
The modal window with the connection command appears. The mode reader corresponds to Read-only access. Copy the command. Alongside the Uniskai Kubernetes Agent, we recommend installing the Uniskai Kubernetes Agent Updater, which automatically manages upgrades for the Uniskai Agent and its associated CRD. You can read more about the Uniskai Kubernetes Agent Updater here. If you prefer not to install the Updater together with the Agent, you can simply uncheck the corresponding option beneath the provided command. You may skip it for now and add the Updater later whenever needed.
Copy the Helm command, then move on to the next step.
Step 5 - Open Cloud Shell
Go to the GCP console and open the Cloud Shell console.
Use the offictial documentation to connect to configure access to your cluster.
When the cluster is connected, paste and run the command from the modal window (Step 4). Once the command completes, ensure that all pods in the uniskai namespace are in the Running state before proceeding.
If you encounter any issues during command execution, check the Troubleshooting.
Step 6 - Confirm cluster connection
Return to Uniskai. Click on the button "I ran the command".
If the Uniskai Kubernetes Agent was installed correctly and successfully connected to the Uniskai platform, you will see a green pop-up notification confirming the connection and reflecting the updated cluster state.
Step 7 - Refresh account
Configuring Read/Write Access for Uniskai Agent
With a “Read/write” connection you can get:
K8s architecture view in Cloudmap and Cloudnet;
K8s Cloudsitter;
Step 1 - Navigate to Cloudk8s tab
Select the Cloudk8s tab on the left menu.
Step 2 - Open cluster connection modal
Click on the switcher of the desired cluster.
The modal window appears.
Step 3 - Select connection type
Click on "Read Write" button.
Step 4 - Copy connection command
The modal window with the connection command appears. The mode reader corresponds to Read-write access. Copy the command. Alongside the Uniskai Kubernetes Agent, we recommend installing the Uniskai Kubernetes Agent Updater, which automatically manages upgrades for the Uniskai Agent and its associated CRD. You can read more about the Uniskai Kubernetes Agent Updater here. If you prefer not to install the Updater together with the Agent, you can simply uncheck the corresponding option beneath the provided command. You may skip it for now and add the Updater later whenever needed.
Copy the Helm command, then move on to the next step.
Step 3 - Open Cloud Shell
Go to the GCP console and open the Cloud Shell console.
Use the official documentation to connect to configure access to your cluster.
When the cluster is connected, paste and run the command from the modal window (Step 2). Once the command completes, ensure that all pods in the uniskai namespace are in the Running state before proceeding.
If you encounter any issues during command execution, check the Troubleshooting.
Step 4 - Confirm cluster connection
When you are completely sure that all pods in the Uniskai namespace are running return to Uniskai and click on "I ran the script" button.
If the Uniskai Kubernetes Agent was installed correctly and successfully connected to the Uniskai platform, you will see a green pop-up notification confirming the connection and reflecting the updated cluster state.
Step 5 - Refresh account
Refresh your account on the platform.
Switch from Read-Write connection to Read only connection
Step 1 - Select cluster
Go to cluster with Read-Write connection and click on the blue button "Switch to read-only".
Step 2 - Refresh account
Refresh your account on the platform
The state is changed to the read-only.
Switch cluster from Read only to Read/Write connection
Step 1 - Select Cloudk8s tab
Step 2 - Select cluster
Step 3 - Run the command
The modal window with the connection script appears. Make sure that Helm is installed and that it can access your cluster. Copy the script below and run it in your cloud shell or terminal and then click next.
Step 4 - Confirm that you ran the script
Return to Uniskai wait several minutes and click on "I ran the script".
If the Uniskai Kubernetes Agent was upgraded correctly and successfully connected to the Uniskai platform, you will see a green pop-up notification confirming the connection and reflecting the updated cluster state.
Step 5 - Refresh the account
Refresh your account in Uniskai.
Troubleshooting
Error: INSTALLATION FAILED: Unable to continue with install
If you encounter an error similar to the following during the Helm installation:
Error: INSTALLATION FAILED: Unable to continue with install: ServiceAccount "uniskai-agent" in namespace "uniskai" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "uniskai-agent"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "uniskai"
This typically happens when the Uniskai Agent manifests were previously installed manually (not via Helm), and Helm cannot take ownership of those existing Kubernetes resources. To resolve the issue, remove the previously deployed resources and retry the Helm installation:
curl https://uniskai-eu-templates.s3.eu-central-1.amazonaws.com/kubernetes-agent/deployment.yaml | kubectl delete -f -
Error: INSTALLATION FAILED: Kubernetes cluster unreachable
This error appears when Helm cannot connect to your Kubernetes cluster. Before retrying the installation, check the following:
Verify cluster connectivity.
Refresh cluster credentials from your cloud provider.
Ensure VPN or network access to the cluster is available.
Once the connection is restored, rerun the Helm installation command.
Error: helm install response status code 403: denied: Your authorization token has expired
This error means your authentication token for Amazon ECR Public has expired, which prevents Helm from pulling the chart.
To fix the issue, log out from the registry to remove outdated credentials by running the following commands:
docker logout public.ecr.aws
helm registry logout public.ecr.aws