Priority
(Medium) I'm annoyed but I'll live
Description
When a PR includes changes to a plugin that's also declared as a dependency for another plugin in the same PR, our CI pipeline fails with pod scheduling issues due to port conflicts.
Reproduction steps
Make changes to plugin A (e.g., kube-monitoring)
This same plugin is already declared as a dependency in another plugin's test-dependencies.yaml (e.g., perses depends on kube-monitoring)
The helm-lint-test workflow fails with errors like:
Warning FailedScheduling pod/charts-yp8i1mk5od-node-exporter-5xc7q
default-scheduler 0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports.
preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod.
Root Cause
The workflow is trying to install the same plugin twice:
Once as a direct change being tested
Again as a dependency of another plugin
This creates port conflicts as both instances try to use the same network resources in our Kind cluster.
Screenshots
Priority
(Medium) I'm annoyed but I'll live
Description
When a PR includes changes to a plugin that's also declared as a dependency for another plugin in the same PR, our CI pipeline fails with pod scheduling issues due to port conflicts.
Reproduction steps
Make changes to plugin A (e.g., kube-monitoring)
This same plugin is already declared as a dependency in another plugin's test-dependencies.yaml (e.g., perses depends on kube-monitoring)
The helm-lint-test workflow fails with errors like:
Root Cause
The workflow is trying to install the same plugin twice:
Once as a direct change being tested
Again as a dependency of another plugin
This creates port conflicts as both instances try to use the same network resources in our Kind cluster.
Screenshots
