Kubernetes health checks: php liveness is now httpGet, and the probe path skips Souin for the kubelet
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- kubernetes, php
- Domain
- devops, documentation
Research direction
Open content/6.deployment/2.kubernetes.md and find the Health Checks section. Update the PHP liveness prose and rendered YAML, reword the timeout and PWA paragraphs, then search the documentation for the template's Souin patch list and add the singleflight patch if it is listed. Done means the PHP probe details and all related explanations match the issue without claiming the pod never becomes ready.
Written by the indexing model from the issue text.
Description
Template change: components-web-app 9b7bca6 (issue components-web-app#104).
Affects content/6.deployment/2.kubernetes.md → Health Checks:
- The php container's
livenessProbeis no longertcpSocket. It is the samehttpGetas readiness (/_api/_/site_config_parameters.jsonld, sameAcceptheader) withperiodSeconds: 10,failureThreshold: 6,timeoutSeconds: 5, and noinitialDelaySeconds(the startup probe holds it off). Update the opening sentence and the rendered YAML. A pod whose php stops answering now restarts after about a minute. A database outage also restarts it. - The
timeoutSeconds: 5callout: the singleflight wedge it describes is now fixed in three ways. The template's Souin build carries darkweak/souin#850 (api/frankenphp/souin/v1.7.9-singleflight-fix.patch), so a timed-out call releases its key. The Caddyfile's@use_cacheskips requests to that path whoseUser-Agentstarts withkube-probe/. And liveness now catches a stuck php. Keep the 5s timeout (the 1s default can lose a cold worker's first request), but reword the callout so it no longer says the pod "never becomes ready". - The pwa paragraph says "the same TCP liveness probe". It's still TCP for pwa, so reword that to stop implying php's probe is TCP.
- If the docs list the template's Souin patches anywhere, add the singleflight patch next to the purge patch. Remove it once a Souin release includes #850.
- Dominant language
- Vue
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from components-web-app/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
components-web-app/docs#210 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
components-web-app/docs#209 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
components-web-app/docs#208 ·
-
Website: the docs site's own service worker can't install (navigateFallback "/" isn't precached)Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
components-web-app/docs#173 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
components-web-app/docs#207 · 1 comment ·
All issues in components-web-app/docs
Similar issues
-
docs pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pydantic/pydantic-ai#10113 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
darnitdevorg/darnit#585 ·
Maintainers usually reply within 1 day
-
ci-cd from-review-extraction python severity:nit tests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LearningCircuit/local-deep-research#7332 ·
Maintainers usually reply within 2 days
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 65/100
lirantal/discoprint#43 ·
Maintainers usually reply within 1 day