Customer Use Case:

The customer uses multi-cluster Helm deployments where passive clusters are defined with replicas: 0 to keep them scaled down until needed. After a successful deployment, they expect the Service Dashboard to show the latest artifact version even when no pods are running.

Current Limitation:

When replicas: 0 is specified, no active instances are created. As a result, the instance sync task is not triggered, and the Service Dashboard continues to display the previous artifact version.

Enhancement Request:

Enable the Service Dashboard to update artifact information for deployments with replicas: 0, ensuring artifact version tracking works even when no active instances are present