Execution containers are being used for Kubernetes agent

[APErebus]

Severity

No response

Version

2024.3+

Latest Version

I could reproduce the problem in the latest build

What happened?

When a Kubernetes agent is executing Kubernetes steps, any defined Execution container details (defined under the Kubernetes API target section) are used as the host container for the script pods, as opposed to the predefined tooling containers bundled with the Kubernetes agent.

For all Kubernete steps except for the Run a kubectl script step, the defined execution container details should not be used.

Reproduction

1. Install a Kubernetes agent deployment target
2. Configure a simple Deploy YAML Kubernetes step targeting the kubernetes agent target tag
3. Configure a execution container under the Kubernetes API target details section
4. Run deployment
5. Observe (using 3rd party tooling) that the script pod being spun up is the defined execution container, not the default octopusdeploy/kubernetes-agent-tools-base image

Error and Stacktrace

No response

More Information

No response

Workaround

The workaround is to set the execution container option to "Run directly on the worker"

[octoreleasebot]

Release Note: Resolved an issue where the Kubernetes agent was erroneously using step-configured execution container details as the script pod container image for certain Kubernetes steps

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2024.3	2024.3.7669
2024.4+	all releases