networkservicemesh / networkservicemesh/.github
Add kind testing job to re-useble worfkflow and refactor integration-k8s-kind
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 11
- Avg merge
- 4m
- Merged PRs (30d)
- 4
Description
Currently, we have a lot of code duplication in the integration-k8s-kind repo: https://github.com/networkservicemesh/integration-k8s-kind
This can be simplified and unified in this repository, which would allow us to flexibly use this workflow in different repositories. For example, to check the fix before merging, etc.
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 comparing the workflow setup in this .github repository with the integration-k8s-kind repository referenced in the issue. Identify the duplicated integration-kind logic, then confirm that a reusable workflow can run the Kind testing job across repositories and that the existing integration behavior remains covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes
- Domain
- ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100