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.

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

Add initial concept explanation of self-healing #48963

Open
sftim opened this issue Dec 6, 2024 · 4 comments
Open

Add initial concept explanation of self-healing #48963

sftim opened this issue Dec 6, 2024 · 4 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/docs Categorizes an issue or PR as relevant to SIG Docs. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@sftim
Copy link
Contributor

sftim commented Dec 6, 2024

This is a Feature Request

What would you like to be added
Add a brief page within https://kubernetes.io/docs/concepts/architecture/ that outlines Kubernetes' ability to self-heal, and link to some choice pages that help people learn more.

Why is this needed
https://kubernetes.io#k8s-features-heading says that Kubernetes is self healing but we don't really explain what that means. You can actually set up your cluster to automatically make replacement Pods, replacement storage volumes, replacement nodes etc. Some of that needs extra work. But right now we don't explain the concept.

Comments
Aim to add a minimum viable product - following our style guide etc, and leave room for people to add more detail.

Remember that concise docs are inherently a good thing. People usually don't want more to read.

/sig architecture
/sig docs
anyone can contribute here

/help

@sftim sftim added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 6, 2024
@k8s-ci-robot
Copy link
Contributor

@sftim:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

This is a Feature Request

What would you like to be added
Add a brief page within https://kubernetes.io/docs/concepts/architecture/ that outlines Kubernetes' ability to self-heal, and link to some choice pages that help people learn more.

Why is this needed
https://kubernetes.io#k8s-features-heading says that Kubernetes is self healing but we don't really explain what that means. You can actually set up your cluster to automatically make replacement Pods, replacement storage volumes, replacement nodes etc. Some of that needs extra work. But right now we don't explain the concept.

Comments
Aim to add a minimum viable product - following our style guide etc, and leave room for people to add more detail.

Remember that concise docs are inherently a good thing. People usually don't want more to read.

/sig architecture
/sig docs
anyone can contribute here

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. sig/docs Categorizes an issue or PR as relevant to SIG Docs. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 6, 2024
@sftim
Copy link
Contributor Author

sftim commented Dec 6, 2024

Got questions about how to work on this? Ask here in a reply, or on Slack (see https://slack.k8s.io for an invitation)

@sftim
Copy link
Contributor Author

sftim commented Dec 6, 2024

/triage accepted
/priority backlog

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/backlog Higher priority than priority/awaiting-more-evidence. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 6, 2024
@sftim
Copy link
Contributor Author

sftim commented Dec 6, 2024

I would make a new page because we are likely to expand it in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/docs Categorizes an issue or PR as relevant to SIG Docs. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants