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: docs/troubleshooting/installation.md
+354-1Lines changed: 354 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -119,7 +119,7 @@ Please include the following information in a bug report when reporting a failed
119
119
```
120
120
supportconfig -k -c
121
121
```
122
-
122
+
123
123
The command output messages contain the generated tarball path. For example the path is `/var/loq/scc_aaa_220520_1021 804d65d-c9ba-4c54-b12d-859631f892c5.txz` in the following example:
@@ -129,3 +129,356 @@ Please include the following information in a bug report when reporting a failed
129
129
A failure PXE Boot installation automatically generates a tarball if the [`install.debug`](../install/harvester-configuration.md#installdebug) field is set to `true` in the Harvester configuration file.
130
130
131
131
:::
132
+
133
+
## Check Charts Status
134
+
135
+
Harvester uses the following chart CRDs:
136
+
137
+
- `HelmChart`: Maintains RKE2 charts.
138
+
139
+
- `rke2-runtimeclasses`
140
+
- `rke2-multus`
141
+
- `rke2-metrics-server`
142
+
- `rke2-ingress-nginx`
143
+
- `rke2-coredns`
144
+
- `rke2-cannal`
145
+
146
+
- `ManagedChart`: Manages Rancher and Harvester charts.
147
+
148
+
- `rancher-monitoring-crd`
149
+
- `rancher-logging-crd`
150
+
- `kubeovn-operator-crd`
151
+
- `harvester-crd`
152
+
- `harvester`
153
+
154
+
You can use the `helm list -A` command to retrieve a list of installed charts.
155
+
156
+
Example of output:
157
+
158
+
```shell
159
+
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
160
+
fleet cattle-fleet-system 4 2025-09-24 09:07:10.801764068 +0000 UTC deployed fleet-107.0.0+up0.13.0 0.13.0
161
+
fleet-agent-local cattle-fleet-local-system 1 2025-09-24 08:59:28.686781982 +0000 UTC deployed fleet-agent-local-v0.0.0+s-d4f65a6f642cca930c78e6e2f0d3f9bbb7d3ba47cf1cce34ac3d6b8770ce5
162
+
fleet-crd cattle-fleet-system 1 2025-09-24 08:58:28.396419747 +0000 UTC deployed fleet-crd-107.0.0+up0.13.0 0.13.0
163
+
harvester harvester-system 1 2025-09-24 08:59:37.718646669 +0000 UTC deployed harvester-0.0.0-master-ac070598 master-ac070598
164
+
harvester-crd harvester-system 1 2025-09-24 08:59:35.341316526 +0000 UTC deployed harvester-crd-0.0.0-master-ac070598 master-ac070598
165
+
kubeovn-operator-crd kube-system 1 2025-09-24 08:59:34.783356576 +0000 UTC deployed kubeovn-operator-crd-1.13.13 v1.13.13
166
+
mcc-local-managed-system-upgrade-controller cattle-system 1 2025-09-24 08:59:10.656784284 +0000 UTC deployed system-upgrade-controller-107.0.0 v0.16.0
167
+
rancher cattle-system 1 2025-09-24 08:57:20.690330683 +0000 UTC deployed rancher-2.12.0 8815e66-dirty
168
+
rancher-logging-crd cattle-logging-system 1 2025-09-24 08:59:36.262080367 +0000 UTC deployed rancher-logging-crd-107.0.1+up4.10.0-rancher.10
169
+
rancher-monitoring-crd cattle-monitoring-system 1 2025-09-24 08:59:35.287099045 +0000 UTC deployed rancher-monitoring-crd-107.1.0+up69.8.2-rancher.15
170
+
rancher-provisioning-capi cattle-provisioning-capi-system 1 2025-09-24 08:59:00.561162307 +0000 UTC deployed rancher-provisioning-capi-107.0.0+up0.8.0 1.10.2
171
+
rancher-webhook cattle-system 2 2025-09-24 09:02:38.774660489 +0000 UTC deployed rancher-webhook-107.0.0+up0.8.0 0.8.0
172
+
rke2-canal kube-system 1 2025-09-24 08:57:25.248839867 +0000 UTC deployed rke2-canal-v3.30.2-build2025071100 v3.30.2
173
+
rke2-coredns kube-system 1 2025-09-24 08:57:25.341016864 +0000 UTC deployed rke2-coredns-1.42.302 1.12.2
174
+
rke2-ingress-nginx kube-system 3 2025-09-24 09:01:31.331647555 +0000 UTC deployed rke2-ingress-nginx-4.12.401 1.12.4
175
+
rke2-metrics-server kube-system 1 2025-09-24 08:57:42.162046899 +0000 UTC deployed rke2-metrics-server-3.12.203 0.7.2
176
+
rke2-multus kube-system 1 2025-09-24 08:57:25.341560394 +0000 UTC deployed rke2-multus-v4.2.106 4.2.1
177
+
rke2-runtimeclasses kube-system 1 2025-09-24 08:57:40.137168056 +0000 UTC deployed rke2-runtimeclasses-0.1.000 0.1.0
178
+
```
179
+
180
+
### HelmChart CRD
181
+
182
+
`HelmChart` items are installed by jobs. You can determine the name and status of each job by running the following command on the Harvester node:
Message: Applying HelmChart using Job kube-system/helm-install-rke2-canal
198
+
- Type: Failed
199
+
Status: False
200
+
Reason:
201
+
Message:
202
+
JobName: helm-install-rke2-canal
203
+
204
+
Namespace: kube-system
205
+
Name: rke2-coredns
206
+
Status:
207
+
- Type: JobCreated
208
+
Status: True
209
+
Reason: Job created
210
+
Message: Applying HelmChart using Job kube-system/helm-install-rke2-coredns
211
+
- Type: Failed
212
+
Status: False
213
+
Reason:
214
+
Message:
215
+
JobName: helm-install-rke2-coredns
216
+
217
+
Namespace: kube-system
218
+
Name: rke2-ingress-nginx
219
+
Status:
220
+
- Type: JobCreated
221
+
Status: True
222
+
Reason: Job created
223
+
Message: Applying HelmChart using Job kube-system/helm-install-rke2-ingress-nginx
224
+
- Type: Failed
225
+
Status: False
226
+
Reason:
227
+
Message:
228
+
JobName: helm-install-rke2-ingress-nginx
229
+
230
+
Namespace: kube-system
231
+
Name: rke2-metrics-server
232
+
Status:
233
+
- Type: JobCreated
234
+
Status: True
235
+
Reason: Job created
236
+
Message: Applying HelmChart using Job kube-system/helm-install-rke2-metrics-server
237
+
- Type: Failed
238
+
Status: False
239
+
Reason:
240
+
Message:
241
+
JobName: helm-install-rke2-metrics-server
242
+
243
+
Namespace: kube-system
244
+
Name: rke2-multus
245
+
Status:
246
+
- Type: JobCreated
247
+
Status: True
248
+
Reason: Job created
249
+
Message: Applying HelmChart using Job kube-system/helm-install-rke2-multus
250
+
- Type: Failed
251
+
Status: False
252
+
Reason:
253
+
Message:
254
+
JobName: helm-install-rke2-multus
255
+
256
+
Namespace: kube-system
257
+
Name: rke2-runtimeclasses
258
+
Status:
259
+
- Type: JobCreated
260
+
Status: True
261
+
Reason: Job created
262
+
Message: Applying HelmChart using Job kube-system/helm-install-rke2-runtimeclasses
263
+
- Type: Failed
264
+
Status: False
265
+
Reason:
266
+
Message:
267
+
JobName: helm-install-rke2-runtimeclasses
268
+
```
269
+
270
+
You can use the information in the following ways:
271
+
272
+
- Determine the cause of a failed job: Check the `Reason` and `Message` values of the `Failed` condition.
273
+
- Rerun a job: Remove the `Status` field for that specific job from the `HelmChart` CRD. The controller deploys a new job.
274
+
275
+
### ManagedChart CRD
276
+
277
+
Rancher uses [Fleet](https://fleet.rancher.io/) to install charts on target clusters. Harvester has only one target cluster (`fleet-local/local`).
278
+
279
+
Fleet deploys an agent on each target cluster via `helm install`, so you can find the `fleet-agent-local` chart using the `helm list -A` command. The `cluster.fleet.cattle.io` CRD contains the agent's status.
Rancher converts the `ManagedChart` CRD into a `Bundle` resource with an `mcc-` prefix. The Fleet agent watches for `Bundle` resources and deploys them to the target cluster. The `BundleDeployment` resource contains the deployment status.
331
+
332
+
The Fleet controller does not push data to the agent. Instead, the agent polls `Bundle` resource data from the cluster on which the Fleet controller is installed. In Harvester, the Fleet controller and agent are on the same cluster, so network issues are not a concern.
333
+
334
+
```shell
335
+
$ kubectl get bundledeployments -A -o jsonpath='{range .items[*]}{"Namespace: "}{.metadata.namespace}{"\nName: "}{.metadata.name}{"\nStatus:\n"}{range .status.conditions[*]}{" - Type: "}{.type}{"\n Status: "}{.status}{"\n Reason: "}{.reason}{"\n Message: "}{.message}{"\n"}{end}{"\n"}{end}'
336
+
337
+
Namespace: cluster-fleet-local-local-1a3d67d0a899
338
+
Name: fleet-agent-local
339
+
Status:
340
+
- Type: Installed
341
+
Status: True
342
+
Reason:
343
+
Message:
344
+
- Type: Deployed
345
+
Status: True
346
+
Reason:
347
+
Message:
348
+
- Type: Ready
349
+
Status: True
350
+
Reason:
351
+
Message:
352
+
- Type: Monitored
353
+
Status: True
354
+
Reason:
355
+
Message:
356
+
357
+
Namespace: cluster-fleet-local-local-1a3d67d0a899
358
+
Name: mcc-harvester
359
+
Status:
360
+
- Type: Installed
361
+
Status: True
362
+
Reason:
363
+
Message:
364
+
- Type: Deployed
365
+
Status: True
366
+
Reason:
367
+
Message:
368
+
- Type: Ready
369
+
Status: True
370
+
Reason:
371
+
Message:
372
+
- Type: Monitored
373
+
Status: True
374
+
Reason:
375
+
Message:
376
+
377
+
Namespace: cluster-fleet-local-local-1a3d67d0a899
378
+
Name: mcc-harvester-crd
379
+
Status:
380
+
- Type: Installed
381
+
Status: True
382
+
Reason:
383
+
Message:
384
+
- Type: Deployed
385
+
Status: True
386
+
Reason:
387
+
Message:
388
+
- Type: Ready
389
+
Status: True
390
+
Reason:
391
+
Message:
392
+
- Type: Monitored
393
+
Status: True
394
+
Reason:
395
+
Message:
396
+
397
+
Namespace: cluster-fleet-local-local-1a3d67d0a899
398
+
Name: mcc-kubeovn-operator-crd
399
+
Status:
400
+
- Type: Installed
401
+
Status: True
402
+
Reason:
403
+
Message:
404
+
- Type: Deployed
405
+
Status: True
406
+
Reason:
407
+
Message:
408
+
- Type: Ready
409
+
Status: True
410
+
Reason:
411
+
Message:
412
+
- Type: Monitored
413
+
Status: True
414
+
Reason:
415
+
Message:
416
+
417
+
Namespace: cluster-fleet-local-local-1a3d67d0a899
418
+
Name: mcc-rancher-logging-crd
419
+
Status:
420
+
- Type: Installed
421
+
Status: True
422
+
Reason:
423
+
Message:
424
+
- Type: Deployed
425
+
Status: True
426
+
Reason:
427
+
Message:
428
+
- Type: Ready
429
+
Status: True
430
+
Reason:
431
+
Message:
432
+
- Type: Monitored
433
+
Status: True
434
+
Reason:
435
+
Message:
436
+
437
+
Namespace: cluster-fleet-local-local-1a3d67d0a899
438
+
Name: mcc-rancher-monitoring-crd
439
+
Status:
440
+
- Type: Installed
441
+
Status: True
442
+
Reason:
443
+
Message:
444
+
- Type: Deployed
445
+
Status: True
446
+
Reason:
447
+
Message:
448
+
- Type: Ready
449
+
Status: True
450
+
Reason:
451
+
Message:
452
+
- Type: Monitored
453
+
Status: True
454
+
Reason:
455
+
Message:
456
+
```
457
+
458
+
If you change the `harvester-system/harvester` deployment image, the Fleet agent detects the change and updates the corresponding status in the `BundleDeployment` resource.
0 commit comments