Bug: HPA does not work correctly with secondaryWorkload when autoscaling is enabled (Deployment Chart 4.2)

[soolame]

📜 Description

While testing application deployments using Deployment Chart 4.2, I found an issue with Horizontal Pod Autoscaler (HPA) when secondaryWorkload is enabled.

This is not currently impacting our production workloads, but I wanted to report it so others are aware and it can be investigated.

👟 Reproduction steps

Create an application using Deployment Chart 4.2.
Enable secondaryWorkload.
Enable autoscaling (HPA).
Deploy the application.

👍 Expected behavior

Each deployment (primary and secondary) should have its own HPA configured correctly, and both HPAs should function independently according to their respective scaling policies.

👎 Actual Behavior

The HPA configuration becomes invalid and reports an ambiguous warning. As a result, the HPA does not behave as expected for the deployments.

☸ Kubernetes version

EKS 1.36

Cloud provider

Details

AWS

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

Please check the labels for secondary workload resources ,

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct