Dynamic replica management using replicaCount to enable or disable DEV-LAKE.
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
Research direction
Start with charts/devlake/templates/statefulsets.yaml and charts/devlake/templates/deployments.yaml, then inspect how replicaCount is defined and used in the chart values. Render the chart with replicaCount set to 0, 1, and a value above 1; done means the StatefulSet and deployments produce the intended replica counts for each case.
Written by the indexing model from the issue text.
Description
Knowing that the dev-lake deployments cannot have more than one replica, we would like to have the ability to manage the replicas of StatefulSet and deployments to set to 0, and then completely disable devlake-helm-chart.
Current configuration:
spec:
replicas: 1
Changes for StatefulSet and deployments :
spec:
replicas: {{ if gt .Values.replicaCount 1 }}1{{ else }}{{ .Values.replicaCount }}{{ end }}
If you find it convenient:
Changes for StatefulSet and Deployment (devlake-ui)
spec:
replicas: {{ .Values.replicaCount }}
Change for Deployment (dev-lake)
spec:
replicas: {{ if gt .Values.replicaCount 1 }}1{{ else }}{{ .Values.replicaCount }}{{ end }}
- Dominant language
- Go Template
- Stars
- 52
- Forks
- 71
- Avg merge
- 16h 15m
- 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 apache/devlake-helm-chart
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/devlake-helm-chart#367 · 6 comments · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/devlake-helm-chart#366 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
apache/devlake-helm-chart#381 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
apache/devlake-helm-chart#374 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
apache/devlake-helm-chart#373 · 1 comment ·
All issues in apache/devlake-helm-chart
Similar issues
-
deployment release-lag
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nolte/kamerplanter#2047 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
plengauer/DXGIOutputDuplication#81 ·
Maintainers usually reply within 1 day
-
omarchy-windows-vm launch fails with false 'Failed to start Windows VM' when VM is already runningOpen
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
kind/engineering pulumi/pulumi-terraform Task Workflow Failure
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pulumi/pulumi-terraform#1215 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
agilepathway/label-checker#710 · 2 comments ·
Maintainers usually reply within 1 day