Kubernetes Object Status shows steps that are not applicable for the current deployment

[APErebus]

Severity

3

Version

2024.1.12760

Latest Version

I could reproduce the problem in the latest build

What happened?

The Kubernetes Object status tab shows steps that aren't scoped or aren't applicable to the current deployment. It erroneously suggests that the step is queued and you'll see the status when the step starts running.

The KOS process doesn't run and the deployment completely successfully, this is purely a UI issue.

Reproduction

1. Create a deployment process with 1 kubernetes raw yaml step and 1 script step
2. Scope the raw yaml step to a specific environment, don't scope the script step
3. Create a release and deploy to a different environment than the scoped one in step 2
4. Note the Kubernetes Object Status tab is visible in the deployment details page and shows that the scoped step is queued (when it isn't)

Error and Stacktrace

No response

More Information

Workaround

No response