Skip to content

Ping Helm Version Issue Leading to Deployment Failures: Timeout Error Resolution #602

@arunplm109083

Description

@arunplm109083

Hello Ping Team,

Earlier Helm version: 0.11.10
Proposed Helm version: 0.11.15

We implemented Helm version 0.11.15 for certain pods (PingDirectory and PingFederate). However, the Helm version alternated between 0.11.10 and 0.11.15 at times, causing deployment failures mostly among pingfederate (k8s deployment) pods with "time exceeded" or "timeout" errors. We updated the version references throughout our codebase wherever applicable.

Although the exact cause of the error was unclear, we observed that reverting to the previous version resolved the issue without any errors.

This is our current setup

a) Workflow where we are passing helm version

name: Create the dynamic configuration environment

concurrency:
  group: ${{ github.head_ref }}
  cancel-in-progress: false

permissions:
  id-token: write
  contents: write

on: [pull_request]

env:
  **PING_HELM_CHART_VERSION: 0.11.15**

jobs:
  docker-pf-build:
    if: contains(github.head_ref, 'IDX-') || contains(github.head_ref, 'idx-') || contains(github.head_ref, 'ID-') || contains(github.head_ref, 'id-')
    name: docker-pf-build
    runs-on: ubuntu-22.04
    steps:
    .
.
.
.
.
.
.

b) our deployment definition

global:
  annotations:
    application_service: "CIAM - dynamic environments"
  workload:
    enableServiceLinks: false
    annotations:
      application_service: "CIAM - dynamic environments"
  ingress:
    addReleaseNameToHost: prepend
    defaultDomain: dev.ciam.non-prod.managed-eks.aws.nuuday.nu
    annotations:
      nginx.ingress.kubernetes.io/backend-protocol: HTTPS
  container:
    strategy:
      type: RollingUpdate
      rollingUpdate:
        maxUnavailable: 1
        maxSurge: 1
    minReadySeconds: 15

pingfederate-admin:
  container:
    resources:
      requests:
        cpu: null
        memory: 2Gi
      limits:
        cpu: null
        memory: 4Gi
  ingress:
    enabled: true
    tls:
      - hosts:
          - federate._defaultDomain_
        secretName: dev-wildcard-tls
    hosts:
      - host: federate._defaultDomain_
        paths:
          - path: /
            pathType: Prefix
            backend:
              serviceName: https
  envs:
    PF_CONSOLE_TITLE: ${ BRANCH } PingFederate
    PD_HOST: ${ PD_HOST }
    PF_ADMIN_NODE: ${ PF_ADMIN_NODE }
    PF_ENGINE_NODE: ${ PF_ENGINE_NODE }
    PF_ENGINE_NODE_2: ${ PF_ENGINE_NODE_2 }
    MYSQL_CONNECTION: ${ MYSQL_CONNECTION }
    RANDOM: ${RANDOM_PLACEHOLDER}
    
pingtoolkit:
  name: pingtoolkit
  image:
    name: pingtoolkit
    repository: 4355####0396.dkr.ecr.eu-north-1.amazonaws.com
    repositoryFqn:
    tag: "2303-1.0.0"
    pullPolicy: IfNotPresent
    
pingfederate-engine:
  container:
    replicaCount: 1
    resources:
      requests:
        cpu: null
        memory: 1Gi
      limits:
        cpu: null
        memory: 1Gi
  clustering:
    autoscaling:
      enabled: false
      minReplicas: 1
  ingress:
    enabled: true
    tls:
      - hosts:
          - federate-engine._defaultDomain_
        secretName: dev-wildcard-tls
    hosts:
      - host: federate-engine._defaultDomain_
        paths:
          - path: /
            pathType: Prefix
            backend:
              serviceName: https
  envs:
    PF_CONSOLE_TITLE: ${ BRANCH } PingFederate
    PD_HOST: ${ PD_HOST }
    PF_ADMIN_NODE: ${ PF_ADMIN_NODE }
    PF_ENGINE_NODE: ${ PF_ENGINE_NODE }
    PF_ENGINE_NODE_2: ${ PF_ENGINE_NODE }
    MYSQL_CONNECTION: ${ MYSQL_CONNECTION }
    RANDOM: ${RANDOM_PLACEHOLDER}

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions