WebService and SideKiq pods alway failed at the first start up

Summary

In EKS 1.34, install the new Gitlab CE. All gitlab pods are in an acceptable state, with the exception of WebService and Sidekiq.

Steps to reproduce

Install Gitlab with:

• helm template then apply by kubectl with serverside
• External postgres 16.9
• External redis 7.2 sentinels mode

Configuration used

global:
  edition: ce
  serviceAccount:
    enabled: true
    create: true
    annotations:
      eks.amazonaws.com/role-arn: arn:aws:iam::xxxxxxxxxxx:role/zzzzzzzzz-GitLab
  minio:
    enabled: false
  kas:
    enabled: false
  ingress:
    configureCertmanager: false
    enabled: false
  hosts:
    domain: "example.com"
    https: true
    gitlab:
      https: true
      name: "git.example.com"
    pages:
      https: false
      name: "pages.example.com"
    registry:
      https: false
      name: "registry.example.com"
  psql:
    password:
      useSecret: true
      secret: gitlab-postgresql-password
      key: postgresql-password
      value: zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
    main:
      database: gitlabhq_production
    ci:
      database: gitlabhq_production_ci
    host: postgresql-host
    port: 5432
    username: gitlab
    applicationName:
    preparedStatements: false
  antiAffinity: disabled
  appConfig:
    webhookTimeout: 30
    defaultProjectsFeatures:
      builds: false
    defaultCanCreateGroup: false
    omniauth:
      enabled: true
      autoSignInWithProvider: 'openid_connect'
      syncProfileFromProvider: ['openid_connect']
      syncProfileAttributes: ['name', 'preferred_username']
      allowSingleSignOn: ['openid_connect']
      autoLinkUser: ["openid_connect"]
      blockAutoCreatedUsers: false
      providers:
        - secret: gitlab-oidc-provider-secret
    object_store:
      enabled: true
      connection:
        secret: gitlab-rails-storage
        key: connection
    lfs:
      enabled: true
      bucket: 's3bucket-gitlab-lfs'
    artifacts:
      enabled: true
      bucket: 's3bucket-gitlab-artifacts'
    uploads:
      enabled: true
      bucket: 's3bucket-gitlab-uploads'
    packages:
      enabled: true
      bucket: 's3bucket-gitlab-packages'
    backups:
      enabled: true
      bucket: 's3bucket-gitlab-backups'
    externalDiffs:
      enabled: false
      bucket: 's3bucket-gitlab-exdiffs'
    terraformState:
      enabled: true
      bucket: 's3bucket-gitlab-tfstate'
    dependencyProxy:
      enabled: false
      bucket: 's3bucket-gitlab-depproxy'
    initialDefaults:
      signupEnabled: false
  praefect:
    enabled: true
    replaceInternalGitaly: true
    virtualStorages:
    - name: default
      gitalyReplicas: 1
      maxUnavailable: 1
      defaultReplicationFactor: 1
    dbSecret:
      secret: gitlab-praefect-dbsecret
      key: postgresql-password
      value: xxxxxxxxxxxxxxx
    psql:
      sslMode: 'disable'
      host: postgresql-host
      port: 5432
      user: praefect
      dbName: praefect
    reconciliation: |
      scheduling_interval = '30s'
  gitaly:
    resources:
      requests:
        cpu: '50m'
        memory: '100Mi'
    internal:
      names:
      - default
  redis:
    host: mymaster
    serviceName: redis
    port: 6379
    sentinels:
      - host: redis-node-0
        port: 26379
      - host: redis-node-1
        port: 26379
      - host: redis-node-2
        port: 26379
    password:
      enabled: false
  extraEnv:
    GITLAB_ALLOW_SEPARATE_CI_DATABASE: 1
    GITLAB_THROTTLE_BYPASS_HEADER: Apps-Bypass-RateLimit
    DISABLE_DATABASE_ENVIRONMENT_CHECK: 1
  railsS3:
    provider: AWS
    region: us-east-1
    use_iam_profile: true
  webManualBuider:
    enabled: true
  pages:
    enabled: true
    accessControl: false
  migrations:
    enabled: true
  webservice:
    service:
      type: ClusterIP
    ingress:
      enabled: false
    helmTests:
      enabled: false
  ## doc/charts/gitlab/gitaly
  gitaly:
    persistence:
      storageClass: st1
      size: 125Gi
  praefect:
    electionStrategy: per_repository
  sidekiq:
  gitlab-shell:
    enabled: false
  gitlab-exporter:
    enabled: false
  gitlab-pages:
    nameOverride: pages
    gitlabCache:
      expiry: 1s
redis:
  install: false
upgradeCheck:
  enabled: false
certmanager:
  install: false
nginx-ingress:
  enabled: false
prometheus:
  install: false
gitlab-runner:
  install: false
postgresql:
  install: false
registry:
  enabled: true

Current behavior

The Sidekiq & WebService pods always began failing at the first time. In the Sidekiq pod, container Sidekiq restarted with exit code 1. In the Webservice pod, container webservice restarted with exit code 1.

Expected behavior

The Sidekiq & WebService pods start normaly.

Versions

• Chart: 9.4.2
• Platform:
  • Cloud: EKS 1.34
• Kubernetes: (kubectl version)
  • Client: 1.34.x
  • Server: 1.34
• Helm: (helm version)
  • Client:
  • Server:

Relevant logs

Sidekiq logs:

{"severity":"INFO","time":"2025-11-30T23:26:33.424Z","message":"Gitlab::Metrics::SliConfig registering Gitlab::Metrics::RequestsRackMiddleware, runtime=sidekiq"}
uninitialized constant Gitlab::Redis::ALL_CLASSES
/srv/gitlab/lib/gitlab/instrumentation/redis.rb:12:in `<class:Redis>'

Webservice logs:

{"timestamp":"2025-11-30T23:26:49.047Z","pid":20,"message":"! Unable to load application: NameError: uninitialized constant Gitlab::Redis::ALL_CLASSES"}
bundler: failed to load command: puma (/srv/gitlab/vendor/bundle/ruby/3.2.0/bin/puma)
/srv/gitlab/lib/gitlab/instrumentation/redis.rb:12:in `<class:Redis>': uninitialized constant Gitlab::Redis::ALL_CLASSES (NameError)