Andrei Shvedau

+1 on that, applied with runners_token, that commented it out, runner instance was recreated and finally connected to GitLab. Module version "5.2.0".

+1 on that. How come using suggested docker image based on release tag gives this error?

+1 on this, tried to upgrade 3.19.0 -> 5.4.0, `create_database_subnet_route_table = true` was going to delete route tables, which was a no-go for me.

Yeah it does, in my specific case the structure was something like that - values-common.yaml - values-dev.yaml - values-prod.yaml where I needed the hook to work on the first ”common”...

This can be the case, but for me, the chart was not fetched from somewhere else but packaged locally with `values-common.yaml` as the main `values.yml` file. Basically breaking the naming...

great issue, came here to create a similar one:) thanks @palashgdev i will check how it looks with my logs

Thanks @cile98, I was having similar issues while setting this up with a bitnami chart for mlflow and this thread gave me the right ideas to look into. Specifically, one...

+1, I cant figure it out yet. Are you also running in the Alpine-based container @dpointk?