Kubernetes version matrix testing

[afrittoli]

Feature request

Test various Tekton components and branches against the versions of k8s supported for that component.

Use case

Validate that Tekton can run on the versions of k8s available when a release is made.

Components

• pipeline Better Kubernetes version test "coverage" pipeline#5606
• triggers
• dashboard
• chains
• results
• operator

Branches

MIN_K8S_TEKTON: min version of k8s that a version of Tekton can use at the time of release
MIN_K8S_SUPPORTED: min version of k8s that is supported (not EOL) - https://kubernetes.io/releases/
MAX_K8S_TEKTON: max version of k8s that a version of Tekton can use at the time of release
MAX_K8S_SUPPORTED: the latest version of k8s available

• PRs on main: test [MIN_K8S_TEKTON, MAX_K8S_SUPPORTED] This should typically be 3 versions.
• PRs on LTS branches: [ max(MIN_K8S_TEKTON, MIN_K8S_SUPPORTED), MAX_K8S_TEKTON ] This will start typically as 3 versions and decrease over time as k8s version go EOL.

Tests

Different components have a different number of e2e jobs.

For pipeline, we have one job for stable, one for beta flags and one for alpha flags.
The whole matrix would be nine jobs, which may be problematic:

• this can have a significant impact on the cost of CI
• if there are flakes, they are much likely to show in any PR

Each component should define their strategy, which may include a combination full CI tests, smoke CI tests and periodic tests to provide coverage for the whole matrix.

[afrittoli]

Related: tektoncd/pipeline#5767

[vdemeester]

/area roadmap

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[afrittoli]

/remove-lifecycle rotten

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[afrittoli]

/remove-lifecycle stale
/lifecycle frozen