Skip to content

Commit c709788

Browse files
bene2k1nerda-codes
andauthored
Apply suggestions from code review
Co-authored-by: nerda-codes <[email protected]>
1 parent 290e3f1 commit c709788

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

containers/kubernetes/reference-content/multi-az-clusters.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ For more information, refer to the [official Kubernetes best practices for runni
4343
- Kapsule's Control Plane network access is managed by a Load Balancer in the primary zone of each region. If this zone fails globally, the Control Plane will be unreachable, even if the cluster spans multiple zones. This limitation also applies to HA Dedicated Control Planes.
4444
- Persistent volumes are limited to their Availability Zone (AZ). Applications must replicate data across persistent volumes in different AZs to maintain high availability in case of zone failures.
4545
- In "controlled isolation" mode, nodes access the Control Plane via their public IPs. If two AZs can not communicate (split-brain scenario), nodes will not appear unhealthy from Kubernetes' perspective, but communication between nodes in different AZs will be disrupted. Applications must handle this scenario if they use components across multiple AZs.
46-
- In "full isolation" mode, nodes also use the Public Gateway to access the Control Plane. If nodes can not reach the Public Gateway (e.g. because of Private Network failure in an AZ), they will become unhealthy. As there is only one Public Gateway per Private Network, losing the AZ with the Public Gateway results in the loss of all nodes in all private pools across all AZs.
46+
- In "full isolation" mode, nodes also use the Public Gateway to access the Control Plane. If nodes cannot reach the Public Gateway (e.g. because of Private Network failure in an AZ), they will become unhealthy. As there is only one Public Gateway per Private Network, losing the AZ with the Public Gateway results in the loss of all nodes in all private pools across all AZs.
4747

4848
<Message type="note">
4949
It is important to note that the scalability and reliability of Kubernetes does not automatically ensure the scalability and reliability of an application hosted on it. While Kubernetes is a robust and scalable platform, each application must independently implement measures to achieve scalability and reliability, ensuring it avoids bottlenecks and single points of failure. Therefore, although Kubernetes itself remains responsive, the responsiveness of your application relies on your design and deployment choices.

tutorials/store-s3-transmit/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ To access Object Storage using s3md, you need to [configure your API key](/ident
3232
## Downloading Transmit 5
3333

3434
Transmit 5 is a powerful and easy-to-use solution to manage Object Storage from your Mac.
35-
It provides a clean and straightforward interface to create, list, and delete buckets, and download, upload, and delete objects inside the Object Storage.
35+
It provides a clean and straightforward interface to create, list, and delete buckets, and download, upload, and delete objects inside the Object Storage bucket.
3636

3737
[Download Transmit 5](https://panic.com/transmit/).
3838

0 commit comments

Comments
 (0)