Unstructured-IO / Unstructured-IO/unstructured-api
Helm chart for self-hosted deployment?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 951
- Forks
- 192
- Avg merge
- 7d 8h
- Merged PRs (30d)
- 2
Description
I've put together a production-oriented Helm chart for the self-hosted API:
- Deployment
- Service
- HPA
- PDB
- Ingress
- API-key Secret
- non-root securityContext
- probes on /healthcheck,
- well-tested resource defaults
You can check it here: https://github.com/yod527/unstructured-api/tree/feat/helm-chart/charts/unstructured-api
Happy to follow whatever conventions you'd want (CI lint, chart-releaser, docs).
Thanks
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.
Research direction
Review the proposed chart at https://github.com/yod527/unstructured-api/tree/feat/helm-chart/charts/unstructured-api, then inspect this repository's deployment and documentation conventions before deciding how it could be integrated. Verify the listed Deployment, Service, HPA, PDB, Ingress, Secret, securityContext, /healthcheck probes, and resource defaults, and define the repository's expected CI, release, and documentation updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100