Kubernetes version matrix testing - Githubissues

tektoncd / plumbing

This repo holds configuration for infrastructure used across the tektoncd org 🏗️

Apache License 2.0

60 stars 110 forks source link

Kubernetes version matrix testing #1288

Open afrittoli opened 2 years ago

afrittoli commented 2 years ago

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 https://github.com/tektoncd/pipeline/issues/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 commented 2 years ago

Related: https://github.com/tektoncd/pipeline/pull/5767

vdemeester commented 1 year ago

/area roadmap

tekton-robot commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

@tekton-robot: Closing this issue.

In response to [this](https://github.com/tektoncd/plumbing/issues/1288#issuecomment-1636811736): >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](https://github.com/tektoncd/plumbing). Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

afrittoli commented 1 year ago

/remove-lifecycle rotten

tekton-robot commented 1 year ago

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 commented 1 year ago

/remove-lifecycle stale /lifecycle frozen