gitlab-upgrade-check fails on clean install (ArgoCD / Minikube) with "It seems you are attempting an unsupported upgrade path"

Summary

I'm trying to setup chart v6.11.0 on Minikube using the values-minikube-minimum.yaml in ArgoCD. However, the health check of gitlab-upgrade-check fails with "It seems you are attempting an unsupported upgrade path. Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/#upgrade-paths" and refuses to proceed with the installation.

Steps to reproduce

• minikube start
• Install ArgoCD using the instructions
• Create the ArgoCD application for Gitlab and provide the helm:values with the values of values-minikube-minimum.yaml

Configuration used

---
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
    name: gitlab
    namespace: argocd
    finalizers:
        - resources-finalizer.argocd.argoproj.io
spec:
    destination:
        server: https://kubernetes.default.svc
        namespace: gitlab
    project: apps
    source:
        chart: gitlab
        repoURL: https://charts.gitlab.io
        targetRevision: 6.11.0
        helm:
            values: |
                # values-minikube.yaml
                # This example intended as baseline to use Minikube for the deployment of GitLab
                # - Minimized CPU/Memory load, can fit into 3 CPU, 6 GB of RAM (barely)
                # - Services that are not compatible with how Minikube runs are disabled
                # - Some services entirely removed, or scaled down to 1 replica.
                # - Configured to use 192.168.99.100, and nip.io for the domain

                # Minimal settings
                global:
                    ingress:
                        configureCertmanager: false
                        class: "nginx"
                    hosts:
                        domain: 192.168.99.100.nip.io
                        externalIP: 192.168.99.100
                    # 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

    syncPolicy:
        automated:
            prune: true
            selfHeal: true
        syncOptions:
            - CreateNamespace=true

Current behavior

Install fails because the healthchecks of gitlab-upgrade-check is preventing the application to install.

Expected behavior

Application installing or providing the details on why this would not be a proper upgrade path.

Versions

• Chart: v6.11.0
• Platform:
  • Self-hosted: Minikube
• Kubernetes: (kubectl version)
  • Client: v1.27.1
  • Server: v1.26.3
• Helm: (helm version)
  • Client: v3.11.3

Relevant logs