Skip to content

Commit 1329a60

Browse files
committed
fmt
1 parent e1ecbbd commit 1329a60

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/content/guides/kamaji-aws-deployment.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ In Kamaji, a Management Cluster is a regular Kubernetes cluster which hosts zero
4848

4949
Throughout the following instructions, shell variables are used to indicate values that you should adjust to your own AWS environment:
5050

51-
### create EKS cluster
51+
### Create EKS cluster
5252

5353
In order to create quickly an EKS cluster, we will use `eksctl` provided by AWS. `eksctl` is a simple CLI tool for creating and managing clusters on EKS
5454

@@ -146,7 +146,7 @@ helm install \
146146
--set installCRDs=true
147147
```
148148

149-
### (optional) Install externalDNS
149+
### (optional) Install ExternalDNS
150150

151151
Setting externalDNS allows to update your DNS records dynamically from an annotation that you add in the service within EKS. Run the following commands to install externalDNS helm chart:
152152

@@ -316,7 +316,7 @@ kubectl --kubeconfig=${TENANT_NAMESPACE}-${TENANT_NAME}.kubeconfig config \
316316

317317
and let's check it out:
318318

319-
```
319+
```bash
320320
kubectl --kubeconfig=${TENANT_NAMESPACE}-${TENANT_NAME}.kubeconfig get svc
321321

322322
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
@@ -325,7 +325,7 @@ kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 38h
325325

326326
Check out how the Tenant Control Plane advertises itself:
327327

328-
```
328+
```bash
329329
kubectl --kubeconfig=${TENANT_NAMESPACE}-${TENANT_NAME}.kubeconfig get ep
330330

331331
NAME ENDPOINTS AGE
@@ -340,7 +340,7 @@ Kamaji does not provide any helper for creation of tenant worker nodes, instead
340340

341341
An alternative approach to create and join worker nodes in AWS is to manually create the VMs, turn them into Kubernetes worker nodes and then join through the `kubeadm` command.
342342

343-
### generate kubeadm join command
343+
### Generate kubeadm join command
344344

345345
To join the worker nodes to the Tenant Control Plane, you need to generate the `kubeadm join` command from the Management cluster:
346346

@@ -351,7 +351,7 @@ JOIN_CMD=$(echo "sudo kubeadm join ${TENANT_ADDR}:6443 ")$(kubeadm --kubeconfig=
351351

352352
> Setting `--ttl=0` on the `kubeadm token create` will guarantee that the token will never expires and can be used every time.
353353
354-
### create tenant worker nodes
354+
### Create tenant worker nodes
355355

356356
In this section, we will use AMI provided by CAPA (Cluster API Provider AWS) to create the worker nodes. Those AMIs are built using [image builder](https://github.com/kubernetes-sigs/image-builder/tree/main) and contains all the necessary components to join the cluster.
357357

0 commit comments

Comments
 (0)