Enable daemonset deployment using the helm chart #409
No reviewers
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#409
Loading…
Reference in New Issue
No description provided.
Delete Branch "kaiyou/garage:feat-k8s-daemonset"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 thereplicaCount
, plus a newkind
value for the workload kind: eitherStatefulSet
orDaemonSet
.When set to
StatefulSet
(default), behavior is unchanged. Thus only moving thereplicaCount
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 :)
Enable daemonset deployment using the helm chartto WIP: Enable daemonset deployment using the helm chartbf5868a71d
to4787685912
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?
4787685912
toe852c91d18
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.
WIP: Enable daemonset deployment using the helm chartto Enable daemonset deployment using the helm chartIs this alive?