-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.10.z
-
No
-
False
-
This is a clone of issue OCPBUGS-11292. The following is the description of the original issue:
—
Description of problem:
TALM rejects policies with any lookup functions. However, lookup on resources in the cluster namespace should work: data: test: | key1: value1 key2: testing: {{hub (lookup "cluster.open-cluster-management.io/v1" "ManagedCluster" "" .ManagedClusterName).metadata.labels.iantest hub}} If this is allowed, it will enable many cluster specific templating to be done on the hub side for customers who would have to do spoke side templating instead (which is strongly discouraged)
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create a policy with templatized fields with lookup functions like the above 2. Create a CGU to roll it out 3.
Actual results:
Rejected as lookup function in general is not allowed: 1.6806157862255638e+09 ERROR controllers.ClusterGroupUpgrade Failed to resolve hub template {"error": "lookup: template function is not supported in TALM"}
Expected results:
Policy remediated properly
Additional info:
- blocks
-
OCPBUGS-11931 hub side lookup function on managed cluster itself for policy templating should be allowed
-
- Closed
-
- clones
-
OCPBUGS-11292 hub side lookup function on managed cluster itself for policy templating should be allowed
-
- Closed
-
- is blocked by
-
OCPBUGS-11292 hub side lookup function on managed cluster itself for policy templating should be allowed
-
- Closed
-
- is cloned by
-
OCPBUGS-11931 hub side lookup function on managed cluster itself for policy templating should be allowed
-
- Closed
-
- links to
-
RHBA-2023:6257 OpenShift Container Platform 4.13.z bug fix update
- mentioned on