Management of applications deployed in kubernetes using Salt
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description of Issue/Question
Given the huge number of possibilities how to manage the kubernetes-based applications using Salt I'm confused.
By managing kubernetes-based application I don't mean installation of kubernetes itself. I mean provisioning the actually deployed application, like sharding the MongoDB database, creating redis clusters. Anything that actually requires some kind of orchestration
In general, what's best:
- On kubernetes nodes, install salt-minion, have salt-master on separate VM, manage applications using docker events from salt-minions. Salt-master have the most complete view of kubernetes infrastructure and user application
- Have in-container minions, possibly in-container master
- some kind of mix 1. and 2. (to be honest I don't think it is any good)
- not using salt
Could someone more experienced share some insight?
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
No files, tests, or entry points are named. Start by reviewing the issue's Kubernetes, MongoDB, Redis, and Salt management scenarios, then determine whether a concrete Salt change can be scoped from them. Done would require an agreed management approach and a specific implementation target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, mongodb, python, redis
- Domain
- databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100