Stefan Andres
Stefan Andres
> Updating the chart configuration via ArgoCD produces an endless sync status due to the pre-sync hooks unable to complete. We had the same problem. I think this is caused...
For what it's worth, I've came across the same problem. I think the mongodb just had some files with deleted users or something. To skip them I put a ugly...
/remove-lifecycle stale
We had the same issue. I was using your helm chart (which does the rbac stuff) and upgraded from 1.3 to 1.5. * the operator itself upgraded itself and wants...
Ah, this is interesting to here and explains why I did not find a migration guide for this use case. :-) For us, it really is helpful to have those...
I probably build it locally and never documented it (I guess there was no arm version available at the time). You might open a PR so that I can merge...
If you are not using a fritzbox in your setup, you might just as well remove the lines from the compose file and even if, it's really optional
This error prevents using this for auto scaled runners for gitlab-ci. :/ (when using anything >1 for IdlecCount https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runners-machine-section) Example: ``` root@gitlab-runner:/etc/gitlab-runner# cat config.toml concurrent = 10 check_interval = 0...
I doubt it, because docker-machine is not maintained anymore. We are also just applying our patch to gitlab's docker-machine fork (https://gitlab.com/gitlab-org/ci-cd/docker-machine).