Health of orphaned resource affects overall app health

[flin-8]

Severity

Low

Version

2026.2.12667

Latest Version

Not applicable

What happened?

When a Kubernetes resource is orphaned (no longer part of the current desired state), its health status was still being included when Octopus summarized the overall health of the application instance / machine. This meant a degraded or unhealthy orphaned resource would drag down the reported health of an otherwise healthy application.

Expected behaviour: orphaned resources are excluded from the summarized health status, since they no longer represent the live state of the deployment.

Reproduction

1. Deploy a Kubernetes deployment resource (using a raw YAML step) so it becomes part of an application instance's live/desired state, with a healthy status.
2. Make the deployment resource degraded by changing the container image to something invalid
3. Cause the resource to become orphaned (e.g. rename the resource or remove it from the raw YAML step), while it still reports a Degraded/unhealthy live status.
4. View the application instance's live status / app health.
5. Observe the orphaned resource's unhealthy status affects the summarized application health, even though the resource is orphaned.

More Information

Workaround

Delete the orphaned resource