api7 / api7/api7-ingress-controller
test: gatewayclasss resources can be normally deleted after the test is completed
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 5
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 10
Description
In the current test process, there may be a situation where the gatewayclass is not deleted normally. We need to consider how to delete normally.
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 with test/e2e/crds/v1alpha1/gatewayproxy.go, especially the referenced lines 143-145, and trace how GatewayClass resources are cleaned up when the test completes. Run the relevant end-to-end test and verify that the GatewayClass is deleted normally without remaining resources or cleanup failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100