Repository navigation
Expand file tree
/
Copy pathREADME.md.gotmpl
More file actions
99 lines (61 loc) · 2.76 KB
/
Copy pathREADME.md.gotmpl
File metadata and controls
99 lines (61 loc) · 2.76 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
# Must Gather Chart for Red Hat Developer Hub (RHDH)
{{ template "chart.deprecationWarning" . }}
{{ template "chart.versionBadge" . }}
{{ template "chart.typeBadge" . }}
{{ template "chart.description" . }}
{{ template "chart.homepageLine" . }}
{{ template "chart.maintainersSection" . }}
{{ template "chart.sourcesSection" . }}
{{ template "chart.requirementsSection" . }}
## TL;DR
```console
helm upgrade --install my-rhdh-must-gather redhat-developer-hub-must-gather \
--repo https://redhat-developer.github.io/rhdh-chart \
--version {{ template "chart.version" . }} \
[--wait --timeout=$duration]
```
Running the command again will automatically replace the previous pod and start a new gather.
Then follow the instructions that will be printed to retrieve the gathered data.
When using `--wait`, the `helm` command will return only when the `gather` init container has finished or the specified timeout has elapsed.
Note that the default Helm timeout when using `--wait` is **5m** (5 minutes), which may be too short for the RHDH must-gather to finish collecting diagnostic data.
Feel free to adjust accordingly.
## Running on OpenShift
This chart works on both Kubernetes and OpenShift.
But for OpenShift, we recommend using the `oc adm must-gather` command, like so:
```sh
oc adm must-gather --image=quay.io/rhdh-community/rhdh-must-gather
```
See the [must-gather tool README](https://github.com/redhat-developer/rhdh-must-gather#for-openshift-clusters) for more details.
## Testing a Release
Once a Helm Release has been deployed, you can test it using the [`helm test`](https://helm.sh/docs/helm/helm_test/) command:
```sh
helm test <release_name>
```
This will run a simple Pod in the cluster to check that the required resources have been created.
You can control whether to disable this test pod or you can also customize the image it leverages.
See the `test.enabled` and `test.image` parameters in the [`values.yaml`](./values.yaml) file.
> **Tip**: Disabling the test pod will not prevent the `helm test` command from passing later on. It will simply report that no test suite is available.
Below are a few examples:
<details>
<summary>Disabling the test pod</summary>
```sh
helm install <release_name> <repo> \
--set test.enabled=false
```
</details>
<details>
<summary>Customizing the test pod image</summary>
```sh
helm install <release_name> <repo> \
--set test.image.registry=docker.io \
--set test.image.repository=bitnami/kubectl \
--set test.image.tag=1.30.0
```
</details>
## Uninstalling the Chart
To uninstall/delete a Helm release named `my-rhdh-must-gather`:
```console
helm uninstall my-rhdh-must-gather
```
The command removes all the Kubernetes resources associated with the chart and deletes the release.
{{ template "chart.valuesSection" . }}