@@ -136,15 +136,15 @@ Sample output:
136
136
137
137
| NAME | STATUS | ROLES | AGE | VERSION | INTERNAL-IP | EXTERNAL-IP | OS-IMAGE | KERNEL-VERSION | CONTAINER-RUNTIME |
138
138
| -------------------| --------| --------------| -------| ---------| -----------------| -------------| ---------------------------| ------------------------| -----------------------------|
139
- | moc-lsbe393il9d | Ready | control-plane| 3h14m | 1.30.4 | 100.72.248 .133 | None | CBL-Mariner/Linux | 5.15.173.1-2.cm2 | containerd://1.6.26 |
140
- | moc-lzwagtkjah5 | Ready | None | 3h12m | 1.30.4 | 100.72.248 .134 | None | CBL-Mariner/Linux | 5.15.173.1-2.cm2 | containerd://1.6.26 |
141
- | moc-wlcjnwn5n02 | Ready | None | 14m | 1.30.4 | 100.72.248 .135 | None | Windows Server 2022 Datacenter | 10.0.20348.2700 | containerd://1.6.21+Azure |
139
+ | moc-lsbe393il9d | Ready | control-plane| 3h14m | 1.30.4 | 100.0.12 .133 | None | CBL-Mariner/Linux | 5.15.173.1-2.cm2 | containerd://1.6.26 |
140
+ | moc-lzwagtkjah5 | Ready | None | 3h12m | 1.30.4 | 100.0.12 .134 | None | CBL-Mariner/Linux | 5.15.173.1-2.cm2 | containerd://1.6.26 |
141
+ | moc-wlcjnwn5n02 | Ready | None | 14m | 1.30.4 | 100.0.12 .135 | None | Windows Server 2022 Datacenter | 10.0.20348.2700 | containerd://1.6.21+Azure |
142
142
143
143
From this sample output:
144
144
145
- - Control plane IP is 100.72.248 .133 (where the ROLES value is ` control-plane ` and OS image is ` CBL-Mariner/Linux ` ).
146
- - Linux node IP is 100.72.248 .134 (where the ROLES value is ` none ` and OS image is ` CBL-Mariner/Linux ` ).
147
- - Windows node IP is 100.72.248 .135 (where the OS image is ` Windows Server 2022 ` ).
145
+ - Control plane IP is 100.0.12 .133 (where the ROLES value is ` control-plane ` and OS image is ` CBL-Mariner/Linux ` ).
146
+ - Linux node IP is 100.0.12 .134 (where the ROLES value is ` none ` and OS image is ` CBL-Mariner/Linux ` ).
147
+ - Windows node IP is 100.0.12 .135 (where the OS image is ` Windows Server 2022 ` ).
148
148
149
149
## Step 3: run the image validation script on the control plane and worker nodes
150
150
@@ -155,43 +155,43 @@ These steps work for both the control plane node and Linux worker node since the
155
155
1 . Check if the commands can be run on the Linux VM (assuming the private key is in ** C:\Users\Administrator\. ssh** ):
156
156
157
157
``` bash
158
- ssh -i " C:\Users\Administrator\.ssh\id_rsa" -o StrictHostKeyChecking=no clouduser@100.72.248 .133 " sudo crictl images --no-trunc"
158
+ ssh -i " C:\Users\Administrator\.ssh\id_rsa" -o StrictHostKeyChecking=no clouduser@100.0.12 .133 " sudo crictl images --no-trunc"
159
159
```
160
160
161
161
1 . Copy the Linux-specific files to the Linux VM:
162
162
163
163
``` bash
164
- scp -i " C:\Users\Administrator\.ssh\id_rsa" C:\i magesign\l inux\* clouduser@100.72.248 .133:.
164
+ scp -i " C:\Users\Administrator\.ssh\id_rsa" C:\i magesign\l inux\* clouduser@100.0.12 .133:.
165
165
```
166
166
167
167
1 . Mark the notation binary file as executable:
168
168
169
169
``` bash
170
- ssh -i " C:\Users\Administrator\.ssh\id_rsa" -o StrictHostKeyChecking=no clouduser@100.72.248 .133 " sudo chmod +x notation"
170
+ ssh -i " C:\Users\Administrator\.ssh\id_rsa" -o StrictHostKeyChecking=no clouduser@100.0.12 .133 " sudo chmod +x notation"
171
171
```
172
172
173
173
1 . Execute commands to validate image signature verification. This step can take around 2-5 minutes:
174
174
175
175
``` bash
176
- ssh -i " C:\Users\Administrator\.ssh\id_rsa" -o StrictHostKeyChecking=no clouduser@100.72.248 .133 " sudo python3 LinuxImageValidate.py"
176
+ ssh -i " C:\Users\Administrator\.ssh\id_rsa" -o StrictHostKeyChecking=no clouduser@100.0.12 .133 " sudo python3 LinuxImageValidate.py"
177
177
```
178
178
179
179
1 . Copy the output file to the local directory:
180
180
181
181
``` bash
182
- ssh -i " C:\Users\Administrator\.ssh\id_rsa" -o StrictHostKeyChecking=no clouduser@100.72.248 .133 " sudo cat imagevalidation_results_linux.json" > imagevalidation_results_controlplane.json
182
+ ssh -i " C:\Users\Administrator\.ssh\id_rsa" -o StrictHostKeyChecking=no clouduser@100.0.12 .133 " sudo cat imagevalidation_results_linux.json" > imagevalidation_results_controlplane.json
183
183
```
184
184
185
185
1 . Clean up all files copied to the VM:
186
186
187
187
``` bash
188
- ssh -i " C:\Users\Administrator\.ssh\id_rsa" -o StrictHostKeyChecking=no clouduser@100.72.248 .133 rm LinuxImageValidate.py notation tsa.crt ca.crt LICENSE imagevalidation_results_linux.json results.yaml
188
+ ssh -i " C:\Users\Administrator\.ssh\id_rsa" -o StrictHostKeyChecking=no clouduser@100.0.12 .133 rm LinuxImageValidate.py notation tsa.crt ca.crt LICENSE imagevalidation_results_linux.json results.yaml
189
189
```
190
190
191
191
1 . Clean up the IP reference from the SSH cache:
192
192
193
193
``` bash
194
- ssh-keygen -R 100.72.248 .133
194
+ ssh-keygen -R 100.0.12 .133
195
195
```
196
196
197
197
Sample output:
@@ -236,41 +236,41 @@ These steps work on all supported Windows OS worker nodes.
236
236
1 . Check if the commands can be run on the Windows VM (assuming the private key is in folder ** C:\Users\Administrator\. ssh** ):
237
237
238
238
``` bash
239
- ssh -i " C:\Users\Administrator\.ssh\id_rsa" -o StrictHostKeyChecking=no Administrator@100.72.248 .135 " crictl images --no-trunc"
239
+ ssh -i " C:\Users\Administrator\.ssh\id_rsa" -o StrictHostKeyChecking=no Administrator@100.0.12 .135 " crictl images --no-trunc"
240
240
```
241
241
242
242
1 . Copy the Windows-specific files inside the Windows VM:
243
243
244
244
``` bash
245
- ssh -i " C:\Users\Administrator\.ssh\id_rsa" Administrator@100.72.248 .135 " powershell -ExecutionPolicy Bypass mkdir c:\win"
246
- scp -i " C:\Users\Administrator\.ssh\id_rsa" C:\i magesign\w in\c a.crt Administrator@100.72.248 .135:c:\w in\c a.crt
247
- scp -i " C:\Users\Administrator\.ssh\id_rsa" C:\i magesign\w in\n otation.exe Administrator@100.72.248 .135:c:\w in\n otation.exe
248
- scp -i " C:\Users\Administrator\.ssh\id_rsa" C:\i magesign\w in\t sa.crt Administrator@100.72.248 .135:c:\w in\t sa.crt
249
- scp -i " C:\Users\Administrator\.ssh\id_rsa" C:\i magesign\w in\W indowsImageValidate.ps1 Administrator@100.72.248 .135:c:\w in\W indowsImageValidate.ps1
245
+ ssh -i " C:\Users\Administrator\.ssh\id_rsa" Administrator@100.0.12 .135 " powershell -ExecutionPolicy Bypass mkdir c:\win"
246
+ scp -i " C:\Users\Administrator\.ssh\id_rsa" C:\i magesign\w in\c a.crt Administrator@100.0.12 .135:c:\w in\c a.crt
247
+ scp -i " C:\Users\Administrator\.ssh\id_rsa" C:\i magesign\w in\n otation.exe Administrator@100.0.12 .135:c:\w in\n otation.exe
248
+ scp -i " C:\Users\Administrator\.ssh\id_rsa" C:\i magesign\w in\t sa.crt Administrator@100.0.12 .135:c:\w in\t sa.crt
249
+ scp -i " C:\Users\Administrator\.ssh\id_rsa" C:\i magesign\w in\W indowsImageValidate.ps1 Administrator@100.0.12 .135:c:\w in\W indowsImageValidate.ps1
250
250
```
251
251
252
252
1 . Execute commands to validate image signature verification. This step can take around 2-5 minutes:
253
253
254
254
``` bash
255
- ssh -i " C:\Users\Administrator\.ssh\id_rsa" Administrator@100.72.248 .135 " powershell -ExecutionPolicy Bypass -File c:\win\WindowsImageValidate.ps1"
255
+ ssh -i " C:\Users\Administrator\.ssh\id_rsa" Administrator@100.0.12 .135 " powershell -ExecutionPolicy Bypass -File c:\win\WindowsImageValidate.ps1"
256
256
```
257
257
258
258
1 . Copy the output file to the local directory:
259
259
260
260
``` bash
261
- scp -i " C:\Users\Administrator\.ssh\id_rsa" Administrator@100.72.248 .135:c:\w in\i magevalidation_results_windows.json C:\i magesign\i magevalidation_results_windows.json
261
+ scp -i " C:\Users\Administrator\.ssh\id_rsa" Administrator@100.0.12 .135:c:\w in\i magevalidation_results_windows.json C:\i magesign\i magevalidation_results_windows.json
262
262
```
263
263
264
264
1 . Clean up all files copied to the VM:
265
265
266
266
``` bash
267
- ssh -i " C:\Users\Administrator\.ssh\id_rsa" Administrator@100.72.248 .135 " powershell -ExecutionPolicy Bypass remove-item -force c:\win"
267
+ ssh -i " C:\Users\Administrator\.ssh\id_rsa" Administrator@100.0.12 .135 " powershell -ExecutionPolicy Bypass remove-item -force c:\win"
268
268
```
269
269
270
270
1 . Clean up IP reference from the SSH cache:
271
271
272
272
``` bash
273
- ssh-keygen -R 100.72.248 .135
273
+ ssh-keygen -R 100.0.12 .135
274
274
```
275
275
276
276
Sample output:
0 commit comments