-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.14, 4.15, 4.16, 4.17, 4.18
-
Important
-
None
-
Rejected
-
False
-
-
-
When using the ACM PolicyGenerator for the ClusterLogForwarder.yaml] source-cr, the following template has been recommended in the cnf-features-deploy examples:
pipelines: '{{hub fromConfigMap "" "group-zones-configmap" (printf "%s-cluster-log-fwd-pipelines" (index .ManagedClusterLabels "group-du-sno-zone")) | toLiteral hub}}'
however, with the new change in the ClusterLogForwarder.yaml from
pipelines: $pipelines
to
pipelines: - $pipelines
the following error is seen in ArgoCD or locally, when running the ACM PG directly or as a kustomize plugin:
kustomize build version_4.17.3 --enable-alpha-plugins > output Error: error generating policies from the PolicyGenerator file '/tmp/kust-plugin-config-3494835375': failed to process the manifest at "source-crs/ClusterLogForwarder.yaml": failed to apply the patch(es) to the manifest(s) using Kustomize: wrong node kind: expected SequenceNode but got ScalarNode: node contents: '{{hub fromConfigMap "" (printf "%!s(MISSING)-pg" .ManagedClusterName) "cluster-log-fwd-pipelines" | toLiteral hub}}'
No hub templating option resulted in a correct Policy for the ClusterLogForwarder CR.
Discussion with ACM folks here.