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

📖 Update production-environment.md #1152

Merged
merged 1 commit into from
Feb 9, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/topics/production-environment.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Production Environment Best Practices

## HA Cluster API Components
The clusterctl CLI will create all the four needed components cluster-api (CAPI), cluster-api-bootstrap-provider-kubeadm (CAPBK), cluster-api-control-plane-kubeadm (KCP) and cluster-api-provider-hetzner (CAPH).
It uses the respective *-components.yaml from the releases. However, these are not highly available. By scaling the components we can at least reduce the probability of failure. For whom this is not enough could add anti-affinity rules and PDBs.
The clusterctl CLI will create all four needed components, such as Cluster API (CAPI), cluster-api-bootstrap-provider-kubeadm (CAPBK), cluster-api-control-plane-kubeadm (KCP), and cluster-api-provider-hetzner (CAPH).
It uses the respective *-components.yaml from the releases. However, these are not highly available. By scaling the components, we can at least reduce the probability of failure. If this is not enough, add anti-affinity rules and PDBs.

Scale up the deployments
```shell
Expand All @@ -14,4 +14,4 @@ kubectl -n capi-kubeadm-control-plane-system scale deployment capi-kubeadm-contr

kubectl -n caph-system scale deployment caph-controller-manager --replicas=2

```
```