7da29afe6e
Address review feedback from coderabbitai on packages/system/postgres-operator/values.yaml:30. The old comment's 5-minute ImagePullBackOff scenario conflicted with the 180s activeDeadlineSeconds that the default maxAttempts/sleepSeconds resolve to, so the numbers could not both be taken at face value. Rewrite the comment to state the actual deadline math and frame the two gates as an AND with activeDeadlineSeconds being the shorter one under defaults, so readers understand why backoffLimit has little headroom without an accompanying maxAttempts/sleepSeconds bump. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Aleksei Sviridkin <f@lex.la>
32 lines
1.8 KiB
YAML
32 lines
1.8 KiB
YAML
cloudnative-pg:
|
|
crds:
|
|
create: true
|
|
image:
|
|
tag: "1.27.3"
|
|
# Image used by the post-install webhook-readiness Job (see templates/webhook-ready-hook.yaml).
|
|
# Any image with kubectl on PATH works; the Job calls the apiserver service proxy with the
|
|
# hook ServiceAccount's token to confirm the mcluster.cnpg.io webhook is reachable end-to-end
|
|
# before the HelmRelease reports Ready, closing the "connection refused" bootstrap race.
|
|
#
|
|
# The tag is digest-pinned so an upstream retag does not change what runs on every install
|
|
# and upgrade across the fleet. Refresh by resolving the current manifest-list digest
|
|
# (`docker manifest inspect docker.io/clastix/kubectl:v1.32`) and updating `digest` below.
|
|
# renovate: datasource=docker depName=docker.io/clastix/kubectl
|
|
webhookReady:
|
|
image:
|
|
repository: docker.io/clastix/kubectl
|
|
tag: v1.32
|
|
digest: sha256:b9ef7d8dbe65bcc81a46c09b8dc7543103055021c4f43287bf59e92a8f4fe05c
|
|
# Retry loop bounds for the readiness probe. Defaults total ~120s wall clock.
|
|
# Both are `default`-coerced in the template so an override that blanks them still
|
|
# produces a working Job.
|
|
maxAttempts: 60
|
|
sleepSeconds: 2
|
|
# Pod-level retry budget for transient node/registry failures (image pull rate limit,
|
|
# OOM, CNI hiccup). The shell loop inside the container only covers reachability retries.
|
|
# Pod retries and activeDeadlineSeconds (wall-clock bound on the whole Job across all
|
|
# pod retries) are ANDed, so activeDeadlineSeconds is the shorter of the two gates with
|
|
# the defaults above: the 60*2+60 = 180s deadline cuts the Job before backoffLimit=2
|
|
# ever matters if pod-level failures eat more than ~60s of the budget. Raise
|
|
# maxAttempts/sleepSeconds alongside backoffLimit when tuning for slow image pulls.
|
|
backoffLimit: 2
|