Troubleshoot VirtualBox
This section includes troubleshooting some of the common issues I faced when running Gitlab on K8S.
What went wrong
Running Gitlab on k8s cluster with storage class nfs
PostgreSQL & Redis internal instances failed to connect to socket (acquire socket lock)
Web server failed to also acquire socket lock.
How to solve the issue
- Make sure
no_root_squash
applied to NFS folder - Run the pod in
privileged = true
security context - PostgreSQL & Redis moved to run in their own external instances
- Configured gitlab.rb to point to the new instances using their k8s dns names (
gitlab-db.NAMESPACE.svc.cluster.local
) - Apply the same for Redis
- Configured gitlab.rb to point to the new instances using their k8s dns names (
- Webserver:
- Because the file was created by a user called
git
web_server['username']
must be changed togit
instead ofgitlab-www
- Run
gitlab-ctl reconfigure
from the pod for changes to take affect
- Because the file was created by a user called