Skip to content

Missing initialDelaySeconds configuration of startupProbe #47093

@oryanperl

Description

@oryanperl

Official Helm Chart version

1.15.0 (latest released)

Apache Airflow version

2.9.3

Kubernetes Version

v1.30.5

Helm Chart configuration

Image

Docker Image customizations

No response

What happened

Hi!
When running on small clusters sometimes the webserver takes longer period to start up
this causes the startupProbe to kill and restart the web server.

There is a possible workaround solution by configuring startupProbe's failureThreshold and periodSeconds but, as far as i can think of, the correct solution would be to configure initialDelaySeconds to allow slow pods to run the webserver before attempting to hearbeat it.

Image

What you think should happen instead

Allow initialDelaySeconds to startupProbes.

configuring initialDelaySeconds is already possible for livenessProbe and readinessProbe, so the addition is only needed for startupProbe

How to reproduce

  1. Running a small kubernetes cluster (e.g. docker desktop's default kubernetes cluster)

  2. Run argocd on the cluster

kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
  1. Have an app of apps in argocd
  2. Have app of apps define a child application which uses airflow chart, i.e.:
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: airflow
  namespace: argocd
spec:
  project: default
  source:
    repoURL: https://airflow.apache.org
    chart: airflow
    targetRevision: 1.15.0
    helm:
      values: |-
        {{- with .Values.airflow }}
        {{- toYaml . | nindent 8 }}
  destination:
    server: https://kubernetes.default.svc
    namespace: {{ .Values.airflow.namespace }}
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - CreateNamespace=true
      - Replace=true
  1. The manifest of startupProbe does not contain initialDelaySeconds

Image

Anything else

I Would like to sole this issue and am willing to submit a PR

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:helm-chartAirflow Helm Chartkind:bugThis is a clearly a bugkind:featureFeature Requestsneeds-triagelabel for new issues that we didn't triage yet

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions