Configuring SCM to Use a Specific Time Zone

To configure SCM to use a specific time zone:

Verify the current time zone of the SCM pod as follows:
```
kubectl exec -it scm-5765f9f4d6-jplmd -n scm-261 -- bash
bash-5.1$ date
```
Sample output:
```
Thu Feb 5 06:06:58 UTC 2026
```

Update the SCM Helm chart deployment file to set the required time zone, as follows:

In the <scm Helm chart directory>/templates/deployment.yaml file, under the cloudmanager container definition, add the following environment variable:

- name: cloudmanager
    image: {{ template "scm.image" . }}
    imagePullPolicy: {{ .Values.image.imagePullPolicy }}
    ports:
      {{- if and (eq $serviceType "LoadBalancer") (eq   .Values.service.loadBalancer.useDualTls "False") }}
      - name: cm-port-http
        containerPort: {{ .Values.port.scmPortHTTP }}
        protocol: TCP
      {{- else }}
      - name: cm-port-https
        containerPort: {{ .Values.port.scmPortHTTPS }}
        protocol: TCP
        {{- end }}
    env:
      - name: oci_cli_auth
        value: api_key
      - name: POD_NAMESPACE
        valueFrom:
          fieldRef:
            fieldPath: metadata.namespace
      - name: TZ
        value: "Asia/Kolkata"

Upgrade the Helm release to apply the changes. For example:

helm upgrade scm-261 . -n scm-261

Sample output:

Release "scm-261" has been upgraded. Happy Helming!
NAME: scm-261
LAST DEPLOYED: Thu Feb 5 06:17:11 2026
NAMESPACE: scm-261
STATUS: deployed
REVISION: 3

Verify the time zone of the SCM Pod. For example:

kubectl exec -it scm-864fc946f6-xxxpx -n scm-261 – bash
bash-5.1$ date

Sample output:

Thu Feb 5 11:48:29 IST 2026

After the upgrade, the SCM pod runs with the IST (Asia/Kolkata) time zone configured in the deployment YAML.