Skip to content

Helm Value file updates

Update the Values files

  1. Go to the ./deployment/helm directory

Update the Chart.yaml

  1. Verify the chart name that you want to use for the helm releases

    example: name: order-history

Update the values.yaml

  1. Update the liveness and readiness probe paths and ports to the appropriate values for both the deployment/blue and deployment/green sections:

    • Port should be set to the same port as the Dockerfile expose

    • Path should be set to the health check paths for the App/API

    Example:

        livenessProbe:
            httpGet:
                path: /myaccount/orderhistory/api/health
                port: 8080
                #initialDelaySeconds: 120
                #periodSeconds: 5
        readinessProbe:
            httpGet:
                path: /myaccount/orderhistory/api/health
                port: 8080
                #initialDelaySeconds: 30
                #periodSeconds: 5
    
  2. Update the container port to the appropriate value for both the deployment/blue and deployment/green sections:

    • Port should be set to the same port as the Dockerfile exposes

    Example:

        ports:
        - name: http
            containerPort: 8080
            protocol: TCP
    

Update the values-local.yaml

  1. Update service:

    • Port should be set to the same port as the Dockerfile exposes

    Example:

    service:
    type: ClusterIP
    port: 80
    targetPort: 8080
    

Update the values-[env]-[slot].yaml

The file references the values-[environment:dev/qa/prod]-[slot:blue/green].yaml files

  1. Update the fqdn: with the appropriate value for the [environment:dev/qa/prod]. You should be using what you had in Jinja for this.

  2. Update the gateway/tlsCredentialName: with the appropriate value for the [environment:dev/qa/prod]. You should be using what you had in Jinja for this.

  3. Add the environment variables the the deployment needs with the appropriate value for the [environment:dev/qa/prod] and [color:blue/green]:

    Example:

    deployment:
    blue:
        env:
        - name: NEXT_PUBLIC_client_USER_DATA_URL [update client reference](liatrio-tag)
            value: "https://hylt2.client.client.com/analytics/userdata?pageType=content" #[update client reference](liatrio-tag)
        - name: NEXT_PUBLIC_ORDERS_STATUS_URL
            value: "https://hylt2.client.client.com/myaccount/orderStatus" #[update client reference](liatrio-tag)
        - name: NEXT_PUBLIC_ORDERS_URL
            value: "http://order-search-api.order-dev.svc.cluster.local/v1/orders"
        - name: NEXT_PUBLIC_PRODUCTS_URL
            value: "https://hylt2.client.client.com/product/info" #[update client reference](liatrio-tag)
        - name: DD_AGENT_HOST
            valueFrom:
            fieldRef:
                fieldPath: status.hostIP
        - name: DD_SERVICE_NAME
            value: "order-history"
        - name: DD_JMXFETCH_ENABLED
            value: "true"
        - name: DD_TRACE_GLOBAL_TAGS
            value: "env:dev"