-
Feature
-
Resolution: Done
-
Critical
-
None
-
False
-
None
-
False
-
Not Selected
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
When it comes to use predefined function (fromSecret, fromConfigMap...) as well as the lookup, the hub ... hub annotation limits the usage of these feature to the namespace where the Policy is being created.
Since ArgoCD is used to manage the cluster fleet every components (policy-sets, placementrule and placementbindings) are created in the openshift-gitops namespace. Doing that we aren't able to use such feature of getting resources from a particular namespace and to push it on a managed cluster.
Will then it be mandatory to create all our dynamic replication process in another namespaces when we need to use fromSecret... functions?
Why is this important?
...
Scenarios
...The current workaround is to have a Policy applied on the Hub that uses managed cluster templates ({{ ... }} ) that copies the content to namespace with the Policy.
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
