Enable daemonset deployment using the helm chart #409

Merged
lx merged 5 commits from kaiyou/garage:feat-k8s-daemonset into main 2023-01-26 21:07:58 +00:00
Contributor

DaemonSet is a k8s resource that schedules one instance per node, which is useful for some garage deployment use cases, including managing garage nodes using k8s node labels.

This PR introduces a new value section named deployment, which now holds the replicaCount, plus a new kind value for the workload kind: either StatefulSet or DaemonSet.

When set to StatefulSet (default), behavior is unchanged. Thus only moving the replicaCount was added to the docs at this point.

When set to DaemonSet, the Helm chart deploys a daemonset indeed, and persistence is switched to a host path.


Currently tagged as WIP, this is my first PR and clearly it requires manual testing from peers :)

DaemonSet is a k8s resource that schedules one instance per node, which is useful for some garage deployment use cases, including managing garage nodes using k8s node labels. This PR introduces a new value section named `deployment`, which now holds the `replicaCount`, plus a new `kind` value for the workload kind: either `StatefulSet` or `DaemonSet`. When set to `StatefulSet` (default), behavior is unchanged. Thus only moving the `replicaCount` was added to the docs at this point. When set to `DaemonSet`, the Helm chart deploys a daemonset indeed, and persistence is switched to a host path. --- Currently tagged as WIP, this is my first PR and clearly it requires manual testing from peers :)
kaiyou changed title from Enable daemonset deployment using the helm chart to WIP: Enable daemonset deployment using the helm chart 2022-10-29 19:23:08 +00:00
kaiyou force-pushed feat-k8s-daemonset from bf5868a71d to 4787685912 2022-11-18 19:02:09 +00:00 Compare
Author
Contributor

This has been running on our production cluster for some time now. It is still missing a version bump, what would the policy recommend? Should I go for 0.2.0 due to breaking API change?

This has been running on our production cluster for some time now. It is still missing a version bump, what would the policy recommend? Should I go for 0.2.0 due to breaking API change?
maximilien requested review from maximilien 2022-12-12 08:42:33 +00:00
kaiyou force-pushed feat-k8s-daemonset from 4787685912 to e852c91d18 2022-12-25 12:28:49 +00:00 Compare
kaiyou added 1 commit 2022-12-25 12:30:39 +00:00
continuous-integration/drone/pr Build is passing Details
559e924cc2
Bump the helm chart version
Author
Contributor

I went with 0.3.0, removing WIP! Please note this partially conflicts with #425 while not incompatible, so depending on which is merged first, the other one will require changes: I am fine with either.

I went with 0.3.0, removing WIP! Please note this partially conflicts with https://git.deuxfleurs.fr/Deuxfleurs/garage/pulls/425 while not incompatible, so depending on which is merged first, the other one will require changes: I am fine with either.
kaiyou changed title from WIP: Enable daemonset deployment using the helm chart to Enable daemonset deployment using the helm chart 2022-12-25 12:34:18 +00:00
Owner

Is this alive?

Is this alive?
lx merged commit a08e01f17a into main 2023-01-26 21:07:58 +00:00
Sign in to join this conversation.
No description provided.