kmesh-net / kmesh-net/kmesh

[E2E Enchancement] define command line flags for different cleanup granularity

Open
#656 3 comments 0 reactions 0 assignees View on GitHub
kind/enhancement
Dominant language
Go
Stars
757
Forks
276
Avg merge
5d 20h
Merged PRs (30d)
2

Description

**What would you like to be added**:

Implement more command line flags for different cleanup granularity to make it more convenient for local run and debug flaky test case.

Now after running test/e2e/run_test.sh, infra like k8s, istio and Kmesh will not cleanup, but test applications will.

So add command line flag to implement such as:

- [x] Cleanup all components: this seems simple, just use kind to delete the testing k8s cluster. #649
- [ ] Don't cleanup test applications: we can use istio.test.nocleanup which is the flag of istio integration framework to control it.
And more if it's necessary.

NOTE: If there are multiple subtasks in an issue, when submitting a PR, you shoud use `fix part of #xxx` instead of directly using `fix #xxx` which will automatically close the entire issue.

Contributor guide

Open the contributing guide

Research direction

Start with test/e2e/run_test.sh and inspect how the current cleanup is performed, including the istio.test.nocleanup flag and the kind-based cluster cleanup from #649. Done means command-line flags provide the requested cleanup granularity, including retaining test applications, while preserving the existing default behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes, shell
Domain
cli, devops, testing-qa
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.