Enhance development testing efficiency
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 758
- Forks
- 277
- Avg merge
- 5d 20h
- Merged PRs (30d)
- 2
Description
What would you like to be added:
Enhance development testing efficiency.
Why is this needed:
At present, I am doing tests by the following steps:
make dockerto build kmesh docker image- dispatch the newly-built docker image to each worker node in kind cluster using
kind load docker-image image_name --name cluster_name kubectl edit ds kmesh -n kmesh-systemto edit the image and trigger daemonset restart- enter the daemonset's corresponding pod and do some testings.
Are these steps correct? Or can we optimize(automate) the testing process?
My environment:
OS: ubuntu 20.04
K8s Cluster: running on kind
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
Start by reviewing the existing make docker workflow and the documented kind and Kubernetes commands in the issue. Determine how building, loading the image into the kind cluster, updating the kmesh DaemonSet, and entering its pod could be automated; done means a repeatable development testing workflow replaces the manual steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- devops, infrastructure, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100