Deuxfleurs/garage
34
65
Fork 83
Code Issues95 Pull requests16 Releases32 Wiki Activity

Allow cluster nodes deployed via Helm to be reachable from external Garage nodes (for multi-site/multi-cluster setups) #1000

New issue
Open
opened 2025-04-01 22:23:15 +00:00 by roxy · 1 comment
roxy commented 2025-04-01 22:23:15 +00:00

Currently, the Garage Helm chart only supports forming a cluster fully within the same Kubernetes environment. However, there are use cases where we want Garage nodes outside of Kubernetes such as on bare metal or in another K8s cluster to join the same Garage cluster.

Problem

We cannot easily configure rpc_public_addr (or equivalent) for each node so that external Garage instances know how to connect.

Why this is needed

To allow hybrid clusters (K8s + bare metal/other K8s clusters) for support multi-site on geographically distributed deployments.

Proposed Solutions

Add a Helm chart configuration a way to generate value for rpc_public_addr on each pod, ensuring external nodes can find and connect to the correct address.

By enabling these options, the Garage Helm chart would support more flexible, multi-cluster deployments with minimal manual intervention.

Currently, the Garage Helm chart only supports forming a cluster fully within the same Kubernetes environment. However, there are use cases where we want Garage nodes outside of Kubernetes such as on bare metal or in another K8s cluster to join the same Garage cluster. **Problem** We cannot easily configure rpc_public_addr (or equivalent) for each node so that external Garage instances know how to connect. **Why this is needed** To allow hybrid clusters (K8s + bare metal/other K8s clusters) for support multi-site on geographically distributed deployments. **Proposed Solutions** Add a Helm chart configuration a way to generate value for rpc_public_addr on each pod, _ensuring external nodes can find and connect to the correct address_. By enabling these options, the Garage Helm chart would support more flexible, multi-cluster deployments with minimal manual intervention.
roxy started working 2025-04-02 08:34:19 +00:00
roxy canceled time tracking 2025-04-02 08:35:31 +00:00
lx added the
kind
improvement
scope
ops
action
for-external-contributors
 labels 2025-04-02 17:31:38 +00:00
roxy commented 2025-04-03 21:29:57 +00:00
Author

i tweaked a bit the chart, and with a scale of 1 it's seems to work.

i tweaked a bit the chart, and with a scale of 1 it's seems to work.
Sign in to join this conversation.
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind/experimental
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
admin-sdk
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#1000
No description provided.
Delete branch "%!s()"

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?