Gitlab by helm on K8s

Infrastructure as Code & Cloud Native
,
1

Problem to solve

Describe your question in as much detail as possible:

  • We deploy a new Gitlab with Helm on our new K8s infrastructure.
  • We create custom Helm charts with Gitlab doc and default helms values on https://charts.gitlab.io/
  • When we deploy it, the SignIn page look a 90’s page: no CSS, no JS.
  • With dev tools on web browser, we could see 302 redirect to sign-in page for all assets and favicon. If we login with root, we could see a 404 error on same items.

Steps to reproduce

  1. Deploy the default Gitlab helm on rancher or git clone (gitlab/gitlab) on kubernetes with these changes on values:
global:
  gitaly:
    enabled: false
    external:
      - name: default
        hostname: <ip>
        port: <port>
        tlsEnabled: false
    authToken:
      secret: gitlab-gitaly-secret
      key: token

certmanager-issuer:
  email: <email>

nginx-ingress:
  enabled: false
  1. We have a Reverse proxy in front of web, DMZ in, so we don’t need ingress controler usage.

Configuration

On premise K8s cluster with Rancher (fresh install) and Longhorn (Fresh install too)

  • Nodes and masters OS: CoreOS (by default is up to date)
  • Container runtime: CRI-O
  • SELinux: permissive

Versions

  • K8s: 1.30.0
  • CRI-O: 1.30.6
  • Rancher: 2.9.3
  • Longhorn: 104.2.0+up1.7.1

Gitlab

  • [x ] Self-managed
  • GitLab.com SaaS
  • Dedicated
  • Self-hosted Runners

Versions

  • GitLab (Web: /help or self-managed system information sudo gitlab-rake gitlab:env:info): 17.5.2
  • GitLab Runner, if self-hosted (Web /admin/runners or CLI gitlab-runner --version): No runner at this time (disabled)

Many thanks ! We did a LOT of tests before going here, with and without lot of changes on the values.
Before we have another K8s cluster with Alpine Linux nodes, Gitlab worked like a charm on it. For technical reasons we need to change to CoreOS and from that we have these results on the signin page.
We try to restore old K8S Cluster to re-deploy charts: same result with sign-in in 302 error and no CSS/JS.