liquidmetal-dev / liquidmetal-dev/flintlock
[FAQ] can we write one starter guide to deploy flintlock without K8S depends?
Open
Nobody has claimed this yet.
help wanted
kind/feature
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 73
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 30
Description
**Describe the solution you'd like:**
can we write one starter guide to deploy flintlock without K8S depends?
**Why do you want this feature:**
make small deployment as easy as possible
**Anything else you would like to add:**
[Miscellaneous information that will assist in solving the issue.]
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
Read CONTRIBUTING.md and its community documentation guidance first, then review the existing deployment documentation for Flintlock. Done means adding a starter guide that explains how to deploy Flintlock without Kubernetes dependencies and makes a small deployment easier to follow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100