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

etcd not mentioned as Cluster Plane component Kubernetes Components #39605

Open
Shivam164 opened this issue Feb 21, 2023 · 5 comments
Open

etcd not mentioned as Cluster Plane component Kubernetes Components #39605

Shivam164 opened this issue Feb 21, 2023 · 5 comments
Assignees
Labels
language/en Issues or PRs related to English language lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@Shivam164
Copy link

Hi all!

In the overview section Kubernetes Components, it is mentioned that kube-apiserver, kube-scheduler, kube-controller-manager, etc are control plane component but it has not been mentioned for etcd component.

I think it can lead to slight confusion.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 21, 2023
@Shivam164 Shivam164 changed the title Didn't mentioned etcd as Cluster Plane component Kubernetes Components Haven't mentioned etcd as Cluster Plane component Kubernetes Components Feb 21, 2023
@Shivam164 Shivam164 changed the title Haven't mentioned etcd as Cluster Plane component Kubernetes Components etcd not mentioned as Cluster Plane component Kubernetes Components Feb 21, 2023
@sftim
Copy link
Contributor

sftim commented Feb 21, 2023

We should perhaps explain that etcd is not part of the control plane per se; it is in fact the backing store for one of the control plane components (kube-apiserver)

/language en

@k8s-ci-robot k8s-ci-robot added the language/en Issues or PRs related to English language label Feb 21, 2023
@Ritikaa96
Copy link
Contributor

Ritikaa96 commented Feb 22, 2023

Adding one line to mention it as a separate coordination service might suffice as its already mentioned that it works as a backing store already.

etcd
Consistent and highly-available key value store used as Kubernetes' backing store for all cluster data. It is not particularly a control plane component but is mainly used as a separate coordination service.
If your Kubernetes cluster uses etcd as its backing store, make sure you have a back up plan for those data.
You can find in-depth information about etcd in the official documentation.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 23, 2023
@Ritikaa96
Copy link
Contributor

/triage accepted
@Shivam164 @sftim . As per the discussion above this addition of line will be helpful.
Is there anything else in your mind?

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 23, 2023
@kumarankit999
Copy link

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
language/en Issues or PRs related to English language lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

6 participants