replicaSet == vps
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
Research direction
No file or test is named. Start by locating the chart template containing replicaCount and the values controlling PVC and Longhorn storage, then compare the 4- and 16-replica branches with the proposed one-volume-per-pod and EC:1 setup. Done means a maintainer-approved storage configuration or a documented decision explaining the supported layout.
Written by the indexing model from the issue text.
Description
it's more a question rather than an issue but maybe i can get some insight on why there are a specific assumption in the cart
in this snippet
{{- if eq (int .Values.replicaCount) 4 }}
{{- range $i := until (int .Values.replicaCount) }} # genera 4 mount
- name: data-rustfs-{{ $i }}
mountPath: /data/rustfs{{ $i }}
{{- end }}
{{- else if eq (int .Values.replicaCount) 16 }}
- name: data
mountPath: /data
{{- end }}
the number of volumes that are given to a specific pod depend on the replica count.
so if replica = 4 i got 4 each with 5 volumes (1 log and 4 data)
if i set 16 i got 16 pod each with 16 volumes.
now, on prem, the disk abstraction layer in my case it's handled via longhorn, i have a dedicated set of worker where longhorn system work, that have storage. longhorn already replicate the data for me, there is replicaset = 3 for every pvc that get requested.
in this scenario, it's still correct to have 4 PVC for eveyr pod? it's gonna to be a huge waste of space i think
What is the best way to handle this scenario?
replicaCount=4, vps=1 (4 drive totali)
Pod rustfs-0 ─ PVC0 ─ 1 drive (nodo A)
Pod rustfs-1 ─ PVC1 ─ 1 drive (nodo B)
Pod rustfs-2 ─ PVC2 ─ 1 drive (nodo C)
Pod rustfs-3 ─ PVC3 ─ 1 drive (nodo D)
my idea is to have a scenario that look like that, with every pod with 1 volume and EC:1 does this make sense?
or i should make a "replica:1" of longhornstorage and use it as not replicated data?
- Dominant language
- CSS
- Stars
- 25
- Forks
- 8
- Avg merge
- 26m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rustfs/helm
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
api ingress supportOpen
Difficulty 3/5 1-2 days Newbie friendliness 66/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
sub domain supportOpen
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
add repositoryOpen
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gnosis/gnosis_vpn#540 ·
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
redhat-developer/rhdh-plugin-export-overlays#4261 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ggml-org/whisper.cpp#4103 ·
Maintainers usually reply within 1 day
-
nightly-tests
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
BlackBeltTechnology/pi-agent-dashboard#825 ·
Maintainers usually reply within 1 day