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

docs: High availability explanation page #940

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

bschimke95
Copy link
Contributor

Adds a page with an explanation what high-availability is and how it is set up with Canonical Kubernetes.

@bschimke95 bschimke95 requested a review from a team as a code owner January 9, 2025 10:12
Copy link
Contributor

@HomayoonAlimohammadi HomayoonAlimohammadi left a comment

Choose a reason for hiding this comment

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

Great stuff @bschimke95, thanks a lot! LGTM, just a minor comment.

@bschimke95
Copy link
Contributor Author

Thanks, waiting for the final approval of @nhennigan then we can ship it.

Comment on lines +21 to +22
redundancy. If one node fails, workloads can be rescheduled on other available
nodes without disrupting services. This node-level redundancy minimizes the
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you add a sentence or two explaining if rescheduling needs manual intervention or if it happens automatically?

@@ -0,0 +1,44 @@
# High Availability
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: High availability

across multiple nodes, HA reduces the risk of downtime and service
interruptions, offering built-in redundancy and fault tolerance.

## Key Components of a Highly Available Cluster
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: Key components of a highly available cluster


A highly available Kubernetes cluster exhibits the following characteristics:

### 1. **Multiple Nodes for Redundancy**
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: Multiple nodes for redundancy

nodes without disrupting services. This node-level redundancy minimizes the
impact of hardware or network failures.

### 2. **Control Plane Redundancy**
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: Control plane redundancy

and controller-manager—are distributed across multiple nodes. This prevents a
single point of failure from rendering the cluster inoperable.

### 3. **Highly Available Datastore**
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: Highly available datastore

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.

4 participants