Skip to content

Day 3: add probes question to Kubernetes quiz - #1891

Open
sonawaneutkarsh wants to merge 1 commit into
The-DevOps-Daily:mainfrom
sonawaneutkarsh:hacktoberfest/day-3-quiz
Open

sonawaneutkarsh wants to merge 1 commit into
The-DevOps-Daily:mainfrom
sonawaneutkarsh:hacktoberfest/day-3-quiz

Conversation

@sonawaneutkarsh

Copy link
Copy Markdown

Adds an intermediate multiple-choice question on liveness vs readiness probes (slow-starting app restart loop scenario) to the Kubernetes Fundamentals quiz. Updates totalPoints (115 -> 128) and difficultyLevels accordingly.

Part of the 8-Day Hacktoberfest Challenge (Day 3).

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-10T20:24:54.442385Z 4368bea PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4368beaa09

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

"Set restartPolicy to OnFailure in the pod spec"
],
"correctAnswer": 0,
"explanation": "Only the liveness probe can trigger a container restart: when it fails, the kubelet kills the container. For slow-starting apps the fix is a startupProbe (which gates the liveness probe until the app is up) or a generous initialDelaySeconds on the liveness probe. The readiness probe only controls whether the pod receives traffic - it never restarts anything.",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Correct the claim that only liveness probes restart containers

When a configured startupProbe reaches its failureThreshold, Kubernetes also kills the container and applies its restart policy; it does not merely gate the liveness probe. The unqualified claim here therefore teaches a false distinction in this exact slow-start scenario and may lead readers to add a startup probe whose own probe budget is still shorter than 60 seconds; clarify that readiness failures never restart containers, while both liveness and startup probe failures can.

Useful? React with 👍 / 👎.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant