ROCm on K3s / Kubernetes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
Research direction
Start from the README's roadmap and the existing Docker path for AMD ROCm to see how the stack is containerized. Locate the Dockerfiles or compose files in the repo and the deployment scripts. Done means a K3s or Kubernetes manifest that launches the ROCm stack similarly to the Docker path.
Written by the indexing model from the issue text.
Description
Run the ROCm stack on K3s / Kubernetes. The Docker path for AMD ROCm exists today; the K3s path does not.
This item comes from the README's old roadmap list, which now links to this board.
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 197
- Avg merge
- 5h 12m
- Merged PRs (30d)
- 607
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 inferstep/ATLAS
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Bootstrap: the last two steps run as the user who owns the installMay be free again @assassinationss claimed this 28 days ago, and no pull request is open. Openarea/install reliability
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
inferstep/ATLAS#412 · 4 comments ·
Maintainers usually reply within 1 day
-
area/cli
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area/cli area/lens status/ready
Difficulty 2/5 Half a day Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
area/ci status/ready
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
inferstep/ATLAS#245 · 4 comments ·
Maintainers usually reply within 1 day
Similar issues
-
area/test type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Clodmony/starship-coop#70 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
punitarani/fli#270 ·
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
jumpserver/jumpserver#17980 ·
Maintainers usually reply within 1 day
-
community enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
namespace
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
EclipseFdn/open-vsx.org#15341 ·
Maintainers usually reply within 1 day