Expose extraTemplateSpec for deployment-api.yaml
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- kubernetes
- Domain
- infrastructure
Research direction
Start by locating deployment-api.yaml and comparing the existing extraSpec pattern elsewhere in the chart. Trace how chart values are passed into the deployment template, then verify that extraTemplateSpec can set priorityClassName under spec.template.spec without breaking existing defaults. Done means the rendered deployment exposes the requested field.
Written by the indexing model from the issue text.
Description
We've run into an issue with self-hosted Flagsmith where its pods are occasionally cycled due to other pods hogging resources. To resolve this we need to set a priorityClassName on the Flagsmith pods. This can be done through deployment-api.yaml through spec.template.spec. However, there is no hook in the chart to do so.
Recommendation: Add extraTemplateSpec to allow adding addition fields for the template in the deployment. This would allow us to specify priorityClassName and be flexible enough to handle other needs. This follows the pattern of extraSpec elsewhere.
Workarounds: Use kustomize or other means to modify the charts.
- Dominant language
- Mustache
- Stars
- 44
- Forks
- 47
- Avg merge
- 14m
- Merged PRs (30d)
- 1
Getting set up
We have not checked this project's setup files yet. 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 Flagsmith/flagsmith-charts
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Flagsmith/flagsmith-charts#543 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Flagsmith/flagsmith-charts#588 ·
Maintainers usually reply within 1 day
-
tech-debt
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Flagsmith/flagsmith-charts#523 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Flagsmith/flagsmith-charts#443 ·
Maintainers usually reply within 1 day
-
Add helm chart for Edge ProxyPossibly taken @BennyG93 claimed this 726 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Flagsmith/flagsmith-charts#408 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in Flagsmith/flagsmith-charts
Similar issues
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
stackabletech/kafka-operator#1033 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Urigo/accounter-fullstack#4583 ·
Maintainers usually reply within 2 days
-
agentic-workflows documentation workflow-editor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#3966 ·
Maintainers usually reply within 1 day
-
🔒 [IBM OSPO Security Notification] — IBM/Deploy-a-Cloud-Native-Application-that-uses-Generative-AIOpensecurity
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
IBM/Deploy-a-Cloud-Native-Application-that-uses-Generative-AI#7 ·
-
agentic-workflows area/Docs partner/agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day