feat: Add support bundle spec to openebs addon #5023
Conversation
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5023-67c5ba6-openebs-3.10.0-k8s-docker-localpv-2024-01-05T20:01:29Z |
addons/openebs/3.10.0/install.sh
Outdated
| # install troubleshoot spec | ||
| render_yaml_file_2 "$src/tmpl-troubleshoot.yaml" | kubectl apply -f - |
There was a problem hiding this comment.
not quite the idiom we normally use, but it'll work
(I would normally render it to a file in $dst, and then include it in the kustomization)
banjoh
added
type::improvement
and removed
type::feature
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5023-4f1928d-openebs-3.10.0-k8s-docker-localpv-2024-01-08T10:30:35Z |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5023-a146604-openebs-3.9.0-k8s-docker-localpv-2024-01-08T11:06:27Z |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5023-a146604-openebs-3.8.0-k8s-docker-localpv-2024-01-08T11:06:27Z |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5023-a146604-openebs-3.7.0-k8s-docker-localpv-2024-01-08T11:06:35Z |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5023-a146604-openebs-3.6.0-k8s-docker-localpv-2024-01-08T11:06:42Z |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5023-a146604-openebs-3.5.0-k8s-docker-localpv-2024-01-08T11:06:55Z |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5023-a146604-openebs-3.3.0-k8s-docker-localpv-2024-01-08T11:07:30Z |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5023-a146604-openebs-3.10.0-k8s-docker-localpv-2024-01-08T11:07:32Z |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5023-a146604-openebs-3.2.0-k8s-docker-localpv-2024-01-08T11:07:36Z |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5023-a146604-openebs-3.4.0-k8s-docker-localpv-2024-01-08T11:07:33Z |
What this PR does / why we need it:
Whenever openebs addon is installed as part of kURL, ensure a support bundle spec is installed in the cluster as well
Which issue(s) this PR fixes:
Fixes sc-96000
Special notes for your reviewer:
Steps to reproduce
Does this PR introduce a user-facing change?
Does this PR require documentation?