Hi @gkoenig, not sure if this helps but my dev flow with renku is as follows:
- Clone the renku repo
- Clone any of the repos that are tied to the renku requirements
- Run chartpress (i.e.
pipenv run chartpress) in any of the repos for the renku requirements you wish to modify (i.e. insert sleep statements in), chartpress will build the docker images for that repo and also tag a new chart version
- Update the renku requirements.yaml file to point to the helm chart locally that you just modified. For example for renku-notebooks if you have the repo cloned in the same parent folder as renku then the path in the requirements file needs to be
- Update the chart version in the renku requirements file to match the new version tagged by chartpress in the component repo - you can find this in the
Chart.yaml file in the component repo.
- After you have modified, built and tagged all requirements that you wish to change then run
helm dep update helm-chart/renku in the renku repo and then run
helm install ...
- When you change a component you have to rerun chartpress for it, update the chart version in the requirements file, run
helm dep update and then
helm upgrade ...
But I rarely have to insert sleep statements in the different components to debug. Usually a simple
kubectl logs ... will give enough information on what the problem is.
Hopefully this helps. Let me know if you want me to post all the links to the repos of components in the renku requirements file.
Disclaimer: these steps will probably not work on the two components that we do not directly maintain (keycloak, postgress) or with the gitlab chart.