Skip to content

Commit

Permalink
Merge pull request #243 from stakater/malformatted_notes
Browse files Browse the repository at this point in the history
Fix malformatting and mkdocs
  • Loading branch information
rasheedamir authored May 27, 2024
2 parents 0d76894 + 6e738e4 commit 0d77748
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 369 deletions.
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -21,3 +21,4 @@ node_modules
# Build files
site/
styles
mkdocs.yml
10 changes: 4 additions & 6 deletions content/help/k8s-concepts/high-availability.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,8 @@ SAAP provides many features and options for protecting your workloads against do

SAAP can help further protect you against many common Kubernetes issues by adding Stakater Site Reliability Engineer (SRE) support and the option to deploy a multi-zone cluster, but there are a number of ways in which a container or infrastructure can still fail. By understanding potential points of failure, you can understand risks and appropriately architect both your applications and your clusters to be as resilient as necessary at each specific level.

!!! note "NOTE"

An outage can occur at several different levels of infrastructure and cluster components.
!!! note
An outage can occur at several different levels of infrastructure and cluster components.

SAAP provides several approaches to add more availability to your cluster by adding redundancy and anti-affinity. Review the following image to learn about potential points of failure and how to eliminate them.

Expand All @@ -36,9 +35,8 @@ A worker node is a VM that runs on physical hardware. Worker node failures inclu

Worker nodes are the virtual machines that contain your application pods. By default, SAAP cluster has a minimum of three worker nodes for a single availability-zone cluster. In the event of a worker node failure, pods are relocated to functioning worker nodes, as long as there is enough capacity, until any issue with an existing node is resolved or the node is replaced. More worker nodes means more protection against single node outages, and ensures proper cluster capacity for rescheduled pods in the event of a node failure.

!!! note "NOTE"

When accounting for possible node failures, it is also important to understand how storage is affected.
!!! note
When accounting for possible node failures, it is also important to understand how storage is affected.

### Potential failure point 3: Cluster availability

Expand Down
363 changes: 0 additions & 363 deletions mkdocs.yml

This file was deleted.

0 comments on commit 0d77748

Please sign in to comment.