Hi all I see this issue is closed https://github.com/k3d-io/k3d/issues/122 But I can't find related topic in docs https://k3d.io/v5.0.0/ Am I missing smth ?

Hey there 👋 What do you want to know from the docs? Auto-Deploy Manifests are a K3s feature And that issue just lead me to make a change on K3s level, allowing you to have subfolders in the manifests directory 👍

well, i would like to see in docs a dedicated section about this with examples because for new users it's absolutely unclear that this feature exists. the reason is that not all k3d users are familiar with k3s and even understand that k3d is k3s for my case I'll be able to handle it myself, but for other users the dedicated section would be a great addition to existing features

There's a tiny bit about it here: https://k3d.io/v5.4.1/usage/k3s/?h=manifests#general-k3s-documentation

hmm

Got ya. Would you mind creating a feature request? I hope that I'll find some time by the end of this month to work off some issues :) For you: volume shortcuts (also need documentation) are a nice thing regarding volume mounts "with a k3s meaning" (see release notes https://github.com/k3d-io/k3d/releases/tag/v5.3.0)

thnx, sorry for stupid question

That's how it's intended to work, yep 👍🏼

will try it

No stupid question, there's really not too much documentation around it 🤷‍♂️

it's actually stupid because i just realized that i aws loooking at docs for 5.0.0 🤦‍♂️

Well, I have actually no clue when I added the docs around k3s features 🤷‍♂️ But then it was probably after 5.0.0 😬 Would be nice if search would suggest results from different versions as well.

This - worked

apiVersion: <http://k3d.io/v1alpha4|k3d.io/v1alpha4>
...
volumes:
  - volume: ${PWD}/test/e2e/kafka.yaml:/var/lib/rancher/k3s/server/manifests/kafka.yaml
    nodeFilters: ["all"]

And this - failed

apiVersion: <http://k3d.io/v1alpha4|k3d.io/v1alpha4>
...
volumes:
  - volume: ${PWD}/test/e2e/kafka.yaml:/k3s-manifests/kafka.yaml
    nodeFilters: ["all"]

Yeah, that's where docs are needed. The shortcuts can currently only be used on their own and not as a path item. This can certainly be enhanced.

and btw leading slash must be present in a volume declaration, otherwise docker won't consider the dest path as valid i,e,

- volume: ${PWD}/test/e2e/kafka.yaml:k3s-manifests/kafka.yaml

will throw an docker error

K3d should replace the shortcut with the actual path before passing it to docker.

got it