-
Bug
-
Resolution: Done
-
Major
-
ACM 2.8.0
-
None
-
2
-
False
-
None
-
False
-
ACM-1228 - ACM PolicyGenerator Improvements
-
-
-
ACM Sprint 26, ACM Sprint 27, GRC Sprint 2023-01
-
Moderate
-
No
Description of problem:
Is it possible to specify multiple clusters in a ClusterSelectors field?
According to https://github.com/stolostron/policy-generator-plugin/blob/ae7f23cf32f056670c3626d1a47962e08c6ed8b3/docs/policygenerator-reference.yaml#L116 you should be able to specify several selectors, but this works, for example, with lists ("-" in front of the key ) Not.
Are there any working examples?
Some investigation so far:
It looks like the behavior of the generator is to create a MatchExpression for each key:value pair given:
spec:
predicates:
- requiredClusterSelector:
labelSelector:
matchExpressions:
- key: cloud
operator: In
values:
- red hat
- key: this-other
operator: In
values:
- label
a possible workaround is to provide a placement manifest.
Version-Release number of selected component (if applicable):
ACM 2.6
How reproducible:
Steps to Reproduce:
- ...
Actual results:
Expected results:
Additional info:
- is cloned by
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
ACM-1664 [ACM] Allow directly providing match labels and match expressions for the generated placement rule in the Policy Generator without requiring the placementRulePath option.
-
- Closed
-
