added a info about the auto heal of k8 #49282
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
the
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
size/S
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
katcosgrove
reviewed
Jan 14, 2025
| ## Ability to self-heal | ||
|
|
||
| The idea behind self-healing Kubernetes is simple: If a container fails, Kubernetes automatically redeploys the afflicted | ||
| container to its desired state to restore operations |
There was a problem hiding this comment.
Suggested change
| container to its desired state to restore operations | |
| container to its desired state to restore operations. |
| The idea behind self-healing Kubernetes is simple: If a container fails, Kubernetes automatically redeploys the afflicted | ||
| container to its desired state to restore operations | ||
|
|
||
| Self-healing Kubernetes has four capabilities : |
There was a problem hiding this comment.
Suggested change
| Self-healing Kubernetes has four capabilities : | |
| Self-healing Kubernetes has four capabilities: |
| - disable containers that don't respond to predefined health checks. | ||
| - prevent containers from appearing to users or other containers until they are ready. | ||
|
|
||
| Ideally, container detection and restoration should be seamless and immediate, minimize application disruption and mitigate negative UX. |
There was a problem hiding this comment.
Suggested change
| Ideally, container detection and restoration should be seamless and immediate, minimize application disruption and mitigate negative UX. | |
| Ideally, container detection and restoration should be seamless and immediate, minimize application disruption and mitigate negative user experience. |
| Ideally, container detection and restoration should be seamless and immediate, minimize application disruption and mitigate negative UX. | ||
| Organizations can specify how Kubernetes performs health checks and what actions it should take after it detects a problem. | ||
|
|
||
| How does self-healing work with Kubernetes? : |
There was a problem hiding this comment.
Suggested change
| How does self-healing work with Kubernetes? : | |
| How does self-healing work with Kubernetes?: |
|
Hi @ayushpatil2122, I am the PR wrangler shadow for this week (January 12) and I will be helping to review this PR. |
Comment on lines
+116
to
+119
| - restart failed containers. | ||
| - replace containers that require updates, such as a new software version. | ||
| - disable containers that don't respond to predefined health checks. | ||
| - prevent containers from appearing to users or other containers until they are ready. |
There was a problem hiding this comment.
Suggested change
| - restart failed containers. | |
| - replace containers that require updates, such as a new software version. | |
| - disable containers that don't respond to predefined health checks. | |
| - prevent containers from appearing to users or other containers until they are ready. | |
| - Restart failed containers. | |
| - Replace containers that require updates, such as a new software version | |
| - Kill containers that don't respond to user-defined health checks. | |
| - Prevent advertising containers to clients until they are ready to serve traffic. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The Kubernetes documentation currently mentions self-healing as a feature, but it does not provide a detailed explanation of what self-healing entails. This feature request aims to address that gap by adding a concise, dedicated page within the Kubernetes architecture section. The new page will briefly outline Kubernetes' self-healing capabilities, such as automatic Pod replacement, workload rescheduling, node health monitoring, and storage recovery. It will also link to relevant documentation to guide users in implementing and understanding these features.
Issue
#48963