[Enhancement] include subdirectories for auto-deploy manifests #892
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
This PR makes the deploy controller scan the
manifests
directory recursively, i.e. alsoyaml
files living in subdirectories will be deployed upon k3s start.Why
In k3d, we can mount volumes into the k3s server container. To get custom manifests into the auto-deploy folder inside the k3s container, we have three options:
ro
won't work, since k3s will fail to write and error out)Fix: k3d-io/k3d#122