Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Properly document and test our supported version for k8s/Tekton #681

Open
qu1queee opened this issue Mar 18, 2021 · 2 comments
Open

Properly document and test our supported version for k8s/Tekton #681

qu1queee opened this issue Mar 18, 2021 · 2 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Comments

@qu1queee
Copy link
Contributor

Idea:

This is a follow-up from this PR discussion. At the moment is not clear for users:

  • which is the minimal version and latest version that Shipwright supports for Tekton
  • which is the minimal version and latest version that Shipwright supports for k8s

We need to provide more clarity on the above, so that users that run on an older version of these dependencies are aware that there is no need to force a bump on their side, in order to use Shipwright.

At the same time, we do not have a mechanism in place to test different versions for the core dependencies, so it makes it harder to properly document this.

As an initial step, we might want to define:

  • How do we express the versions we support for Kubernetes, would that be N(latest) plus N-1 and N-2?
  • How do we express the versions we support for Tekton, would that be N(latest) plus N-1 and N-2?
  • How can we test all permutations of the above core dependencies? git-actions ?
@qu1queee qu1queee added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Mar 18, 2021
@adambkaplan
Copy link
Member

@qu1queee I believe #669 will fix this, correct?

@qu1queee
Copy link
Contributor Author

@adambkaplan not 100%, I think the goal is:

Document all versions that we support for k8s and Tekton

The idea behind that is:

Avoid as much as possible to force users to bump their k8s/Tekton only because of Shipwright

The current problem:

  • [1] We do not know which versions of Tekton we can support, because we do not have the right testing in place to build a matrix of versions and test them continuously.
  • [2] We know which versions of K8S we support, but we might not know this in the future, because we do not have the right testing in place to build a matrix of versions and test them continuously.

I think this issue is currently looking for feedback on how to achieve [1] [2].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests

2 participants