Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added a info about the auto heal of k8 #49282

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

added a info about the auto heal of k8 #49282

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions content/en/docs/concepts/architecture/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,6 +106,29 @@ kube-proxy on the nodes in your cluster.

{{< glossary_definition term_id="container-runtime" length="all" >}}

## 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
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
container to its desired state to restore operations
container to its desired state to restore operations.


Self-healing Kubernetes has four capabilities :
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Self-healing Kubernetes has four capabilities :
Self-healing Kubernetes has four capabilities:


- 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.
Comment on lines +116 to +119
Copy link
Contributor

Choose a reason for hiding this comment

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

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.


Ideally, container detection and restoration should be seamless and immediate, minimize application disruption and mitigate negative UX.
Copy link
Contributor

Choose a reason for hiding this comment

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

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.

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? :
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
How does self-healing work with Kubernetes? :
How does self-healing work with Kubernetes?:


- Pending. The pod has been created but is not running.
- Running. The pod and its containers are running without issue
- Succeeded. The pod completes its container lifecycle properly -- it runs and stops normally.
- Failed. At least one container within the pod has failed, and the pod is terminated.
- Unknown. The pod's state and disposition cannot be determined.

## Addons

Addons use Kubernetes resources ({{< glossary_tooltip term_id="daemonset" >}},
Expand Down