Support for adding annotations to deployment spec to Package Manager
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
Research direction
Start with charts/rstudio-pm/values.yaml and charts/rstudio-pm/templates/deployment.yaml, and compare the related Connect change in pull request #794. Done means users can configure deployment annotations through values.yaml and the deployment spec receives them.
Written by the indexing model from the issue text.
Description
Description
Users would like the ability to add annotations to the deployment spec. Right now it's possible to add annotations to the pod spec and to the service spec, but not the deployment spec.
apiVersion: apps/v1
kind: Deployment
metadata:
annotations:
reloader.stakater.com/auto: "true"
This request arose because I was talking to a user who is using a tool (https://github.com/stakater/Reloader) to automate redeployments when a secret changes. But that tool depends on an annotation being set on a deployment.
Approach
- Add new top level item to values.yaml:
deployment:
annotations: {}
- Update the deployment template
(https://github.com/rstudio/helm/blob/main/charts/rstudio-pm/templates/deployment.yaml)to add annotations set in values.yaml.
Related
I already completed this work for Connect. See, this pull request: https://github.com/rstudio/helm/pull/794
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Contributor guide
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 rstudio/helm
-
bug team: workbench
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
bug team: launcher team: workbench
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
team: connect
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
team: launcher team: workbench
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
team: workbench
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
repo:raw-data
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hotosm/raw-data-api#316 · 1 comment ·
-
agentic-workflows cascade-suspected
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
willow
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openedx/openedx-authz#460 ·