`extraEnvFrom` helm values are not available in sidekiq main container

Summary

When attempting to use the extraEnvFrom feature added in MR !2536 (merged) for sidekiq, we can see the env section gets populated correctly in the init containers, but the main sidekiq container does not get the values from extraEnvFrom.

Steps to reproduce

Install chart with sidekiq enabled, and with same values passed via extraEnvFrom to sidekiq. Note that the sidekiq main container does not have the values populated in env.

Configuration used

global:
  sidekiq:
    extraEnvFrom:
      SUBSCRIPTION_PORTAL_ADMIN_EMAIL:
        secretKeyRef:
          name: gitlab-subscription-portal-admin-email-v1
          key: SUBSCRIPTION_PORTAL_ADMIN_EMAIL
      SUBSCRIPTION_PORTAL_ADMIN_TOKEN:
        secretKeyRef:
          name: gitlab-subscription-portal-admin-token-v1
          key: SUBSCRIPTION_PORTAL_ADMIN_TOKEN

Current behavior

No values in env are being populated from global.sidekiq.extraEnvFrom on the sidekiq main container

Expected behavior

Values in env are being populated from global.sidekiq.extraEnvFrom on the sidekiq main container

Versions

• Chart: 419ef1ae
• Platform:
  • Cloud: GKE
• Kubernetes:
  • Client: 1.22
  • Server: 1.22
• Helm: 3.9.2
  • Client:
  • Server:

Relevant logs

(Please provide any relevate log snippets you have collected, using code blocks (```) to format)