kubernetes/ingress-nginx

Feature Request: Add Support for Startup Probe Configuration in default-backend-deployment.yaml

Open

#12437 opened on Dec 4, 2024

View on GitHub
 (8 comments) (0 reactions) (0 assignees)Go (15,199 stars) (7,888 forks)batch import
help wantedkind/featurelifecycle/frozenneeds-priorityneeds-triage

Description

As we are implementing the startup probe in our application, we observed that the ingress Helm chart in the latest GA version (4.11.3 ) does not include any object for the startup probe. Below is a sample code snippet to configure the startup probe in the default backend. Please consider this as a feature request for an upcoming release: {{- if .Values.defaultBackend.startupProbe }} startupProbe: {{ toYaml .Values.defaultBackend.startupProbe | nindent 12 }} {{- end }}

Contributor guide

Tech stack
gokubernetes
Domain
backenddevopsinfrastructure
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Helm basicsKubernetes probesingress nginx chart structureYAML templating
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
Review the existing liveness and readiness probe configurations in the default backend deployment template at templates/default backend deployment.yaml. Implement a startupProbe block following the same pattern, gated by a .Values.defaultBackend.startupProbe condition. Ensure the value is properly documented in values.yaml and update any relevant tests.