Modularize cluster validation logic in e2e framework
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
Refactor the `ValidateCluster` method to take in arbitrary validation checks (e.g. on taints, cp count, K8s version, etc.)
```go
ValidateCluster(validationOpts ...ValidationE2ETestOpt)
```
So that we don't need to keep adding new upgrade workflow when simply wanna validate different aspects of the cluster.
Related discussions:
- https://github.com/aws/eks-anywhere/pull/1224#discussion_r809167468
- https://github.com/aws/eks-anywhere/pull/1176#discussion_r802846451
- https://github.com/aws/eks-anywhere/pull/1176#discussion_r803041868
Contributor guide
Research direction
Locate the Go e2e framework's ValidateCluster method and the existing upgrade workflows that perform cluster validation. Read the linked pull request discussions for context on the proposed validation options. Done means ValidateCluster accepts arbitrary validation checks without requiring a new upgrade workflow for each cluster aspect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100