Normal Description of problem:
We don't document where user must put the custom CRs for PolicyGenTemplate
Version-Release number of selected component (if applicable):
4.14
How reproducible:
N/A
Steps to Reproduce:
N/A
Actual results:
├── policygentemplates
│ ├── kustomization.yaml
│ ├── version_4.13
│ │ ├── common-ranGen.yaml
│ │ ├── group-du-sno-ranGen.yaml
│ │ ├── group-du-sno-validator-ranGen.yaml
│ │ ├── helix56-v413.yaml
│ │ ├── kustomization.yaml
│ │ ├── ns.yaml
│ │ └── source-crs/
│ └── version_4.14
│ ├── common-ranGen.yaml
│ ├── group-du-sno-ranGen.yaml
│ ├── group-du-sno-validator-ranGen.yaml
│ ├── helix56-v414.yaml
│ ├── kustomization.yaml
│ ├── ns.yaml
│ └── source-crs/
Expected results:
├── policygentemplates
│ ├── kustomization.yaml
│ ├── version_4.13
│ │ ├── common-ranGen.yaml
│ │ ├── group-du-sno-ranGen.yaml
│ │ ├── group-du-sno-validator-ranGen.yaml
│ │ ├── helix56-v413.yaml
│ │ ├── kustomization.yaml
│ │ ├── ns.yaml
│ │ └── source-crs/
| | └── reference-crs/ <-- reference policy CRs extracted from ZTP container
| | └── custom-crs/ <-- user’s custom CRs
│ └── version_4.14
│ ├── common-ranGen.yaml
│ ├── group-du-sno-ranGen.yaml
│ ├── group-du-sno-validator-ranGen.yaml
│ ├── helix56-v414.yaml
│ ├── kustomization.yaml
│ ├── ns.yaml
│ └── source-crs/
| └── reference-crs/ <-- reference policy CRs extracted from ZTP container
| └── custom-crs/ <-- user’s custom CRs
Additional info:
We must point out that under source-crs if user want to add custom crs which will be applied to the cluster on day-2, they need to create a custom-crs directory and populate CRs over there