-
Notifications
You must be signed in to change notification settings - Fork 98
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
Proposal: Add Helm Chart for nydus snapshotter #612
Comments
https://github.com/dragonflyoss/helm-charts/tree/main/charts/nydus-snapshotter is it enough for this? |
@imeoer The above helm chart is not updated with latest version of nydus snapshotter. When updated to latest snapshotter version v0.15.0. it fails with the below error
|
I have the same question. Currently, the helm chart includes nydus-snapshotter v0.9.0, but the latest version is v0.15.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nydus-snapshotter has no Helm Chart to be conventionally deployed in the K8s cluster yet. We can compose such a Helm Chart to pack all necessary binaries, configs and K8s manifests into a single Helm Chart package. Depoly nydus-snapshotter as Daemonset running a each node. Run nydusd by
systemd-run
which makes it possible that nydusd runs in the host namespace while nydus-snapshotter runs in the its container namespace.Nydus-snapshotter container image packs:
containerd-nydus-grpc
nydus-snapshotter pod's init-container installs nydusd binary to host's system path during pod startup, which means systemd can find it in the host namespace.
In such manner, even nydus-snapshotter pod is destroyed for the reason like Daemonset rolling upgrade or other maintenance purpose or unintentional operation, the container image IO is not affected.
The text was updated successfully, but these errors were encountered: