Resources from gitrepo are reported as existing with targetCustomizations
and doNotDeploy: true
#2411
Labels
targetCustomizations
and doNotDeploy: true
#2411
Is there an existing issue for this?
Current Behavior
With following
fleet.yaml
from gitrepo its resources are reported as existing even if these resources are actually not deployed on any cluster. After clicking on the resource name Rancher errors out.Sample
deployment.yaml
used together with fleet.yaml:The
clusterSelector
matches to a cluster (withenv: dev
label) where the resources are actually not deployed. The target cluster is correctly ignored but non-existing resources are actually reported:On attempt to click on the non-existing resource name on cluster dhcp12:
Rancher errors out:
The issue was found when validating #2245 and it is present in Rancher 2.7.7, 2.8.3 and in 2.9-head.
Expected Behavior
Resources that are not deployed on any cluster should not be reported as
Ready
, esp. for a cluster specified intargetCustomizations
and withdoNotDeploy: true
entry set. AnywaytargetCustomizations
anddoNotDeploy
keys are working as expected.It would be nice if the non-existing resources are not reported as
Ready
.Steps To Reproduce
env: dev
to your downstream clusterfleet-default
namespace with mentioned resourcesReady
Environment
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: