Deployment gitlab on cluster minikube on windows10

General
1

I tried to deploy gitlab on cluster minikube on windows10. Checking the deployment on minikube all pods, deployments, services … are green, but I can’t access gitlab. After I entered root/initially provided password I always get the error 422 The change you requested was rejected

I deployed gitlab with the following command: helm upgrade --install gitlab gitlab/gitlab --version 7.8.2 --timeout 600s -f .\gitlab-minikube.yaml --namespace gitlab --set global.edition=ce

and the minimal settings:

Minimal settings

global: ingress: configureCertmanager: false class: “nginx” hosts: domain: 192.168.49.2.nip.io externalIP: 192.168.49.2

Disable Rails bootsnap cache (temporary)

rails: bootsnap: enabled: false shell: # Configure the clone link in the UI to include the high-numbered NodePort # value from below (gitlab.gitlab-shell.service.nodePort) port: 32022

Don’t use certmanager, we’ll self-sign

certmanager: install: false

Use the ingress addon, not our Ingress (can’t map 22/80/443)

nginx-ingress: enabled: false

Save resources, only 3 CPU

prometheus: install: false gitlab-runner: install: false

Reduce replica counts, reducing CPU & memory requirements

gitlab: webservice: minReplicas: 1 maxReplicas: 1 sidekiq: minReplicas: 1 maxReplicas: 1 gitlab-shell: minReplicas: 1 maxReplicas: 1 # Map gitlab-shell to a high-numbered NodePort to support cloning over SSH since # Minikube takes port 22. service: type: NodePort nodePort: 32022 registry: hpa: minReplicas: 1 maxReplicas: 1

than: I forwarded all ports.

I can start gitlab and I can see the login page, but the login with root and the password I found in the secret gitlab-gitlab-initial-root-password fails.

2

Start by checking the logs of the GitLab pods to see if there are any specific error messages:

kubectl logs -n gitlab <gitlab-webservice-pod-name>
kubectl logs -n gitlab <gitlab-sidekiq-pod-name>
kubectl logs -n gitlab <gitlab-postgresql-pod-name>

Replace <gitlab-webservice-pod-name>, <gitlab-sidekiq-pod-name>, and <gitlab-postgresql-pod-name> with the actual pod names.

Make sure that the externalIP in your configuration is correctly set up. Since you’re using nip.io, verify that it resolves correctly to your Minikube IP:

nslookup 192.168.49.2.nip.io

Ensure that you are using a compatible Helm chart version for your GitLab deployment. Sometimes specific configurations may change across versions. Consider using the latest stable version unless you have a specific reason to stick to 7.8.2.

Confirm that the initial password you are using is correct. You can check it directly from the secret:

kubectl get secret -n gitlab gitlab-gitlab-initial-root-password -o jsonpath='{.data.password}' | base64 --decode

Sometimes, this issue can arise if Rails migrations haven’t run properly. You can check the status of your database migrations:

kubectl exec -n gitlab -it <gitlab-webservice-pod-name> -- gitlab-rake db:migrate:status

If you see any pending migrations, you might need to run them:

kubectl exec -n gitlab -it <gitlab-webservice-pod-name> -- gitlab-rake db:migrate

Make sure to clear your browser cache or try accessing GitLab in incognito mode to ensure that no stale session data is causing the issue.

Since you’re not using the built-in ingress, ensure that the service type is set correctly. You can also try to access GitLab directly via the NodePort service you set up. For example, if you mapped it to 32022, try:

http://192.168.49.2:32022

If you have other NGINX ingress controllers running, they might conflict. Ensure that the NGINX ingress controller is disabled by setting:

nginx-ingress:
  enabled: false

Ensure that your deployment has the necessary persistent storage configuration. If you’re using local volumes, confirm that they are correctly mounted.