Configuring Siebel Server Pods to Use a Specific Time Zone

This topic describes how to configure a custom time zone for Siebel Server, SAI Server, CGW, and SMC by using environment variables. It also describes how to apply the configuration changes through SCM and verify that the updated time zone is in effect. For more information, see the

To configure a Siebel Server pod to use a specific time zone:

1. Verify the current time zone of the Siebel Server pod. For example:

   kubectl -n sbl261 exec -it edge-0 -- bash
   bash-5.1$ date

   Sample output:

   Tue Feb 10 09:22:49 UTC 2026

2. Configure the time zone for Siebel Server and SAI Server pods as follows:
   1. Open the siebel.yaml file in the /home/opc/siebel/<env_id>/<namespace>-cloud-manager/flux-crm/apps/base/siebel directory.
   2. Add the envlist parameter under the appropriate server definitions. For example:
      • For each profile (for example, quantum and edge), add the following configuration under the corresponding server definition:

        envlist:
        - name: TZ
          value: "Asia/Kolkata"

      • SAI Server example:

        saiServer:
        - profile: ai_financialservices_greenfield
          replicas: 1
          sai_prefix: quantum
          envlist:
          - name: TZ
            value: "Asia/Kolkata"

      • Siebel Server example:

        siebelServer:
        - profile: siebel
          replicas: 1
          sesResources:
            limits:
              cpu: 4
              memory: 24Gi
            requests:
              cpu: 1
              memory: 8Gi
          siebsrvr_prefix: edge
          envlist:
          - name: TZ
            value: "Asia/Kolkata"

   3. Commit the changes to the SCM Git repository:

      git pull
      git add .
      git commit -m "<message>"
      git push

3. Configure the time zone for CGW and SMC pods as follows:
   1. Open the siebel-gateway.yaml file, in the /home/opc/siebel/<env_id>/<namespace>-cloud-manager/flux-crm/apps/base/siebel directory.
   2. Add the envlist parameter under the cgw and smc sections. For example:

      envlist:
      - name: TZ
        value: "Asia/Kolkata"

      • CGW example:

        cgw:
          affinity:
            podAntiAffinity:
              preferredDuringSchedulingIgnoredDuringExecution:
              - podAffinityTerm:
                  labelSelector:
                    matchExpressions:
                    - key: app.siebel.tier
                      operator: In
                      values:
                      - cgw
                  topologyKey: kubernetes.io/hostname
                weight: 100
          replicas: 3
          envlist:
          - name: TZ
            value: "Asia/Kolkata"

      • SMC example:

        smc:
          affinity: {}
          envlist:
          - name: TZ
            value: "Asia/Kolkata"

   3. Commit the changes to the SCM Git repository:

      git pull
      git add .
      git commit -m "<message>"
      git push

4. Verify the time zone configuration:

   After reconciliation completes, all Siebel component pods, and the ingress controller will run with the configured IST (Asia/Kolkata) time zone instead of the default UTC time zone. You can verify the time zone configuration as follows:

   kubectl -n sbl261 exec -it edge-0 -- bash
   bash-5.1$ date

   Sample output:

   Tue Feb 10 14:41:57 IST 2026

   Note: This example uses the IST (Asia/Kolkata) time zone. You can configure any supported time zone based on your requirements.