The Uniskai Kubernetes Agent Updater is an automated component designed to keep Uniskai Agent installations inside Kubernetes clusters up to date with the latest features, security enhancements, and improvements. It removes the need for manual maintenance by continuously monitoring for new agent versions and applying updates when available.

The Uniskai Agent installation includes a single Custom Resource Definition (CRD) that is applied to the cluster during the initial Helm deployment. Because Helm does not manage CRD upgrades after the first installation, updating the agent requires upgrading both the CRD and the Helm release whenever a new version is available. These updates can be performed manually by checking the Uniskai platform for new releases, or they can be fully automated by installing the Uniskai Kubernetes Agent Updater, which handles updates for both the CRD and the Helm release.

The updater itself changes infrequently and does not introduce any additional CRDs. Since it is installed using Helm, continuous deployment tools such as Argo CD or Flux CD can be used to automatically detect and apply new versions of the updater, enabling a completely automated workflow for maintaining both the agent and the updater.

The Uniskai Kubernetes Agent Updater operates through Kubernetes CronJobs that periodically query the Uniskai platform for available updates. By default, it checks for new agent versions every hour, although this interval can be customized or the CronJob can be disabled entirely when updates are meant to be triggered manually.

The updater can be uninstalled at any time without affecting the functionality of the Uniskai Agent. If removed, the agent continues to operate normally, but all future updates must be applied manually.

Select the Cloudk8s tab on the left menu.

Click on the "Show only connected" switcher to filter out not-connected clusters.

A blue information icon may appear next to the cluster’s connection status. This icon indicates that the Uniskai Agent is up to date on the platform side, but it is not installed in the cluster.

Hover over the notification icon to display a pop-up containing the “Install Agent Updater” button. Click this button to proceed.

Copy the Helm command, then move on to the next step.

Go to AWS CloudShell and run the command:

Replace "region-code" with the AWS region code where your cluster is located and "cluster-name" with the name of your cluster.

When the cluster is connected, run the command from the modal window (Step 4).

Return to Uniskai and click on "I ran the script" button.

If the Uniskai Kubernetes Agent Updater was installed correctly, the loader next to the cluster’s connection status will disappear after a short time, and the blue information icon will no longer appear.

If the Helm installation command for the Uniskai Kubernetes Agent Updater got stuck for an extended period, cancel it and run the following command:

Check the Completions column in the output. If it shows 0/1, this indicates an issue with the current Uniskai Kubernetes Agent installation, preventing the Updater from completing its initial validation.

To investigate the root cause, run:

From the returned list of pods, select the oldest one, copy its name, and retrieve the logs:

Review the last log messages to identify the issue.

If you see an error message beginning with "Old Uniskai Agent resources found...", it means an older version of the Uniskai Agent was previously installed manually (not via Helm). To resolve this, remove the manually deployed resources and reinstall the Uniskai Agent in the cluster.

If you see an error message beginning with "No Uniskai Agent resources were found...", it means that the Uniskai Agent is not installed in the cluster. Install the Uniskai Agent first and then repeat the Updater installation.

After identifying the root cause, remove the failed Uniskai Kubernetes Agent Updater installation before proceeding with any further actions by running: