Description of Issue
A customer may wish to edit a helm release. An example of why a customer might want to do this is to increase the timeouts for a failing install or upgrade. A particular example of this requirement was when a customer's grafana-loki install was failing on a particularly large cluster. The customer edited the Helm release with kubectl edit and added a timeout of 20 minutes, but this change was not persistent. In order to make the change persistent, the helm release in Gitea must be updated.
Method
Caution - Any changes pushed to the git repo will be reflected onto your Kommander cluster
Here are the steps for editing the grafana-loki helm release.
1. Use the following commands to retrieve the gitea url and credentials:
ingress=$(kubectl -n kommander get svc kommander-traefik -o go-template='https://{{with index .status.loadBalancer.ingress 0}}{{or .hostname .ip}}{{end}}')
printf "$ingress/dkp/kommander/git\n"
gitea_username=$(kubectl -n kommander get secret admin-git-credentials -o go-template='{{.data.username|base64decode}}')
gitea_password=$(kubectl -n kommander get secret admin-git-credentials -o go-template='{{.data.password|base64decode}}')
printf " $gitea_username / $gitea_password\n"%
2. Login to gitea using the details above.
3. Go to explore, select kommander/kommander and then browse to services/grafana-loki/0.48.5/grafana-loki-helmrelease/grafana-loki.yaml
4. Click the edit button and make the required changes adding in the timeout values.
3. Go to explore, select kommander/kommander and then browse to services/grafana-loki/0.48.5/grafana-loki-helmrelease/grafana-loki.yaml
4. Click the edit button and make the required changes adding in the timeout values.
[...]
install:
crds: CreateReplace
remediation:
retries: 30
timeout: 20m
upgrade:
crds: CreateReplace
remediation:
retries: 30
timeout: 20m
[...]
5. Select 'Commit directly to the main branch' and click 'Commit Changes'. Please note that if you upgrade DKP then these changes will be lost.