Mirantis / Mirantis/cri-dockerd
adding testing with minikube to cri-dockerd release
Open
Nobody has claimed this yet.
build
testing
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 356
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 3
Description
hello ! after the https://github.com/Mirantis/cri-dockerd/issues/163 I thought maybe we could add a github action to cri-dockerd repo to install minikube with Cri-docker from head and do some basic testing with minikube, to avoid surprises in the future
Contributor guide
No contributing guide indexed for this repository
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
Start by reading issue #163 and reviewing the cri-dockerd repository's existing GitHub Actions. Define the workflow's completion criteria as installing Minikube, using cri-dockerd from the repository head, and running basic Minikube tests that catch future integration surprises.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, kubernetes
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100