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

Add note to the example of Manifest Deployer #5482

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
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
2 changes: 1 addition & 1 deletion docs/manifests.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Included with k0s, Manifest Deployer is one of two methods you can use to run k0

Manifest Deployer runs on the controller nodes and provides an easy way to automatically deploy manifests at runtime.

By default, k0s reads all manifests under `/var/lib/k0s/manifests` and ensures that their state matches the cluster state. Moreover, on removal of a manifest file, k0s will automatically prune all of it associated resources.
By default, k0s reads all manifests under `/var/lib/k0s/manifests` that end with `.yaml` and ensures that their state matches the cluster state. It does not read files with other extensions, such as `.yml`. Moreover, on removal of a manifest file, k0s will automatically prune all of its associated resources.

The use of Manifest Deployer is quite similar to the use the `kubectl apply` command. The main difference between the two is that Manifest Deployer constantly monitors the directory for changes, and thus you do not need to manually apply changes that are made to the manifest files.

Expand Down