Octopus Kubernetes agent fails to upgrade via Octopus Server

[scme0]

Severity

No response

Version

Introduced in 2024.2.6908

Latest Version

I could reproduce the problem in the latest build

What happened?

When attempting to upgrade the Kubernetes agent via Octopus, it shows a message saying that it can't be upgraded because it's running in a container.

This change introduced the issue: https://github.com/OctopusDeploy/OctopusDeploy/pull/24318

Reproduction

1. Installed a version of the Kubernetes agent that is not the latest version
2. Perform a health check
3. Navigate to the Connectivity tab on the agent target
4. Click "Upgrade to latest"
5. The task will show the following message:

Error and Stacktrace

No response

More Information

No response

Workaround

You can upgrade your Kubernetes agent manually by running the following helm command in a terminal with the appropriate Kubernetes context set:
helm upgrade --atomic --version '1.*.*' --namespace <namespace> <helm-release-name> oci://registry-1.docker.io/octopusdeploy/kubernetes-agent

[octoreleasebot]

Release Note: Fix Kubernetes agents being unable to be updated

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2024.2	2024.2.7550
2024.3+	all releases