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

fix(typo): fix typo in kubeone guide for machine controller #1793

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/kubeone/v1.3/guides/machine_controller/_index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ kubectl apply -f machines.yaml

Some examples of possible machine deployment yamls can be found in Machine-controller [examples directory](https://github.com/kubermatic/machine-controller/tree/master/examples)

Otherwise, you can also define MachineDeployment objects directly in the KubeOne Configuration Manifest, under `dynamicWorkers` key.
Otherwise, you can also define MachineDeployment objects directly in the KubeOne Configuration Manifest, under `dynamicWorkers` key.
You can run `kubeone config print --full` for an example configuration.

## Creating Additional Worker Nodes
Expand Down Expand Up @@ -139,15 +139,15 @@ kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replic
```

```bash
# Scalding down
# Scaling down
kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replicas=2
```

Scaling down to zero is useful when you want to "temporarily" delete worker
nodes, i.e. have the ability to easily recreate them by scaling up.

```bash
# Scalding down
# Scaling down
kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replicas=0
```

Expand Down
6 changes: 3 additions & 3 deletions content/kubeone/v1.4/guides/machine_controller/_index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ kubectl apply -f machines.yaml

Some examples of possible machine deployment yamls can be found in Machine-controller [examples directory](https://github.com/kubermatic/machine-controller/tree/master/examples)

Otherwise, you can also define MachineDeployment objects directly in the KubeOne Configuration Manifest, under `dynamicWorkers` key.
Otherwise, you can also define MachineDeployment objects directly in the KubeOne Configuration Manifest, under `dynamicWorkers` key.
You can run `kubeone config print --full` for an example configuration.

## Creating Additional Worker Nodes
Expand Down Expand Up @@ -139,15 +139,15 @@ kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replic
```

```bash
# Scalding down
# Scaling down
kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replicas=2
```

Scaling down to zero is useful when you want to "temporarily" delete worker
nodes, i.e. have the ability to easily recreate them by scaling up.

```bash
# Scalding down
# Scaling down
kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replicas=0
```

Expand Down
4 changes: 2 additions & 2 deletions content/kubeone/v1.5/guides/machine-controller/_index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,15 +139,15 @@ kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replic
```

```bash
# Scalding down
# Scaling down
kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replicas=2
```

Scaling down to zero is useful when you want to "temporarily" delete worker
nodes, i.e. have the ability to easily recreate them by scaling up.

```bash
# Scalding down
# Scaling down
kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replicas=0
```

Expand Down
4 changes: 2 additions & 2 deletions content/kubeone/v1.6/guides/machine-controller/_index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,15 +139,15 @@ kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replic
```

```bash
# Scalding down
# Scaling down
kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replicas=2
```

Scaling down to zero is useful when you want to "temporarily" delete worker
nodes, i.e. have the ability to easily recreate them by scaling up.

```bash
# Scalding down
# Scaling down
kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replicas=0
```

Expand Down
4 changes: 2 additions & 2 deletions content/kubeone/v1.7/guides/machine-controller/_index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,15 +139,15 @@ kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replic
```

```bash
# Scalding down
# Scaling down
kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replicas=2
```

Scaling down to zero is useful when you want to "temporarily" delete worker
nodes, i.e. have the ability to easily recreate them by scaling up.

```bash
# Scalding down
# Scaling down
kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replicas=0
```

Expand Down
4 changes: 2 additions & 2 deletions content/kubeone/v1.8/guides/machine-controller/_index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,15 +139,15 @@ kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replic
```

```bash
# Scalding down
# Scaling down
kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replicas=2
```

Scaling down to zero is useful when you want to "temporarily" delete worker
nodes, i.e. have the ability to easily recreate them by scaling up.

```bash
# Scalding down
# Scaling down
kubectl scale -n kube-system machinedeployment <machinedeployment-name> --replicas=0
```

Expand Down