You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ztp-adding-new-content-to-gitops-ztp.adoc
+26-26Lines changed: 26 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,9 @@ Perform the following procedure to add new content to the {ztp} pipeline.
11
11
12
12
.Procedure
13
13
14
-
. Create a subdirectory, `source-crs`, in the directory containing the `kustomization.yaml` file for the `PolicyGenTemplate` CR.
14
+
. Create a subdirectory named `source-crs`in the directory that contains the `kustomization.yaml` file for the `PolicyGenTemplate` custom resource (CR).
15
15
16
-
. Add your custom CRs to this folder, as shown in the following example:
16
+
. Add your custom CRs to the `source-crs` subdirectory, as shown in the following example:
17
17
+
18
18
[source,text]
19
19
----
@@ -26,17 +26,17 @@ example
26
26
└── source-crs <1>
27
27
├── PaoCatalogSource.yaml
28
28
├── PaoSubscription.yaml
29
-
├── bell
29
+
├── custom-crs
30
30
| ├── apiserver-config.yaml
31
31
| └── disable-nic-lldp.yaml
32
32
└── elasticsearch
33
33
├── ElasticsearchNS.yaml
34
34
└── ElasticsearchOperatorGroup.yaml
35
35
----
36
-
<1> The `sources-crs` subdirectory is in the same directory as the `kustomization.yaml` file.
36
+
<1> The `source-crs` subdirectory must be in the same directory as the `kustomization.yaml` file.
37
37
38
-
. Update the required `PolicyGenTemplate` CRs to include references to the content you added in the `custom-crs` directory.
39
-
+
38
+
. Update the required `PolicyGenTemplate` CRs to include references to the content you added in the `source-crs/custom-crs` and `source-crs/elasticsearch` directories. For example:
39
+
+
40
40
[source,yaml]
41
41
----
42
42
apiVersion: ran.openshift.io/v1
@@ -68,8 +68,9 @@ spec:
68
68
remediationAction: inform
69
69
policyName: "group-dev-lso-operator-group"
70
70
- fileName: StorageSubscription.yaml
71
-
remediationAction: inform
72
-
policyName: "group-dev-lso-sub"
71
+
remediationAction: inform
72
+
policyName: "group-dev-lso-sub"
73
+
#These are custom local polices that come from the source-crs directory in the git repo
73
74
# Performance Addon Operator
74
75
- fileName: PaoSubscriptionNS.yaml
75
76
remediationAction: inform
@@ -78,31 +79,30 @@ spec:
78
79
remediationAction: inform
79
80
policyName: "group-dev-pao-cat-source"
80
81
spec:
81
-
image: <image URL here>
82
+
image: <image_URL_here>
82
83
- fileName: PaoSubscription.yaml
83
-
remediationAction: inform
84
-
policyName: "group-dev-pao-sub"
85
-
#These are custom local polices that come from the source-crs directory in the git repo
<1> Set `fileName` to include the custom CR subfolder from the `/source-crs` parent.
101
+
<1> Set `fileName` to include the relative path to the file from the `/source-crs` parent directory.
102
102
103
-
. Commit the `PolicyGenTemplate` change in Git, and then push to the Git repository being monitored by the GitOps ZTP Argo CD policies application.
103
+
. Commit the `PolicyGenTemplate` change in Git, and then push to the Git repository that is monitored by the GitOps ZTP Argo CD policies application.
104
104
105
-
. Update the `ClusterGroupUpgrade` CR to include the changed `PolicyGenTemplate` and save it as `cgu-test.yaml`.
105
+
. Update the `ClusterGroupUpgrade` CR to include the changed `PolicyGenTemplate` and save it as `cgu-test.yaml`. The following example shows a generated `cgu-test.yaml` file.
106
106
+
107
107
[source,yaml]
108
108
----
@@ -123,26 +123,26 @@ spec:
123
123
----
124
124
125
125
. Apply the updated `ClusterGroupUpgrade` CR by running the following command:
126
-
[source, terminal]
127
126
+
127
+
[source,terminal]
128
128
----
129
129
$ oc apply -f cgu-test.yaml
130
130
----
131
131
132
132
.Verification
133
133
134
-
. Check that the updates have succeeded by running the following command:
134
+
* Check that the updates have succeeded by running the following command:
0 commit comments