Adding extra containers to deployments
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- helm, kubernetes
- Domain
- devops
Research direction
Start by reading the Helm chart's deployment configuration and determine how values could represent additional containers. Validate the rendered Kubernetes manifests for a configurable sidecar such as Cloud SQL Proxy, with no Kustomize or post-renderer required.
Written by the indexing model from the issue text.
Description
When using an external database, it's common to have to use a proxy to safely connect from a service to the database. In Google Cloud, one of the recommended approaches is to have a side car container of cloud-sql-proxy.
I am deploying Devlake in a GitOps Flux-based environment, so Kustomize is not an option as it executes before the Helm chart is extracted and applied. Helm post renderers are an option, but some good effort to get it working.
Additionally, enabling extra containers can also enable other use cases.
- 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
-
API bug connectors
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
pyinfra-dev/pyinfra#1986 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
plengauer/DXGIOutputDuplication#81 ·
Maintainers usually reply within 1 day