Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
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
Next Next commit
docs: Use lowercase filename for FAQ
  • Loading branch information
marc1404 committed Oct 10, 2025
commit 4861bcc2c8be98c2cb58a52b8393e15191551aba
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ Along with the above Custom Controllers and Resources, MCM requires the `Machine
To start using or developing the Machine Controller Manager, see the documentation in the `/docs` repository.

## FAQ
An FAQ is available [here](docs/FAQ.md).
An FAQ is available [here](docs/faq.md).

## cluster-api Implementation
- `cluster-api` branch of machine-controller-manager implements the machine-api aspect of the [cluster-api project](https://github.com/kubernetes-sigs/cluster-api).
Expand Down
2 changes: 1 addition & 1 deletion docs/FAQ.md → docs/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ A machine is deleted by MCM generally for 2 reasons-
- Machine is unhealthy for at least `MachineHealthTimeout` period. The default `MachineHealthTimeout` is 10 minutes.
- By default, a machine is considered unhealthy if any of the following node conditions - `DiskPressure`, `KernelDeadlock`, `FileSystem`, `Readonly` is set to `true`, or `KubeletReady` is set to `false`. However, this is something that is configurable using the following [flag](../kubernetes/deployment/out-of-tree/deployment.yaml#L30).
- Machine is scaled down by the `MachineDeployment` resource.
- This is very usual when an external controller cluster-autoscaler (aka CA) is used with MCM. CA deletes the under-utilized machines by scaling down the `MachineDeployment`. Read more about cluster-autoscaler's scale down behavior [here](https://github.com/gardener/autoscaler/blob/machine-controller-manager-provider/cluster-autoscaler/FAQ.md#how-does-scale-down-work).
- This is very usual when an external controller cluster-autoscaler (aka CA) is used with MCM. CA deletes the under-utilized machines by scaling down the `MachineDeployment`. Read more about cluster-autoscaler's scale down behavior [here](https://github.com/gardener/autoscaler/blob/machine-controller-manager-provider/cluster-autoscaler/faq.md#how-does-scale-down-work).

### What are the different sub-controllers in MCM?

Expand Down
Loading