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

Bump to Kubernetes 1.15 will kill all OpenShift 3.11/4.2 activities #2187

Closed
disposab1e opened this issue Mar 8, 2020 · 11 comments
Closed
Labels
kind/question Issues or PRs that are questions around the project or a particular feature lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@disposab1e
Copy link

disposab1e commented Mar 8, 2020

A bump of +4! versions from Kubernetes 1.11 to 1.15 to fix one! bug (#1113) will kill all OpenShift 3.11/4.2 activities.

@disposab1e disposab1e changed the title Bump to Kubernetes 1.15 will kill all OpenShit 3.11 activities Bump to Kubernetes 1.15 will kill all OpenShit 3.11/4.2 activities Mar 8, 2020
@disposab1e disposab1e changed the title Bump to Kubernetes 1.15 will kill all OpenShit 3.11/4.2 activities Bump to Kubernetes 1.15 will kill all OpenShift 3.11/4.2 activities Mar 8, 2020
@vdemeester
Copy link
Member

vdemeester commented Mar 9, 2020

@disposab1e thanks for the issue. The bump was not to fix one bug (#1113) ; that bug happened to get fixed at the same time. The bump was to be able to bump knative.dev/pkg, to benefit enhancements on that, and prepare the use of conversion webhook (that are beta in 1.15).

This indeed means that starting from 0.11, Tekton Pipeline won't work on anything lower than OpenShift 4.2 (The same way Knative does not). OpenShift 3.11 was never really supported either (to have a working webhook you needed to enable some configuration on you cluster, that are not there by default).

I understand this can be frustrating but as a project, we also have to, sometimes make hard choice, keep being up-to-date.

/kind question

@tekton-robot tekton-robot added the kind/question Issues or PRs that are questions around the project or a particular feature label Mar 9, 2020
@chmouel
Copy link
Member

chmouel commented Mar 9, 2020

OpenShift 3.11 never was properly tested so it may just be by luck that it was working previously.

As 4.2 drop we (tekton upstream) are supporting kubernetes releases minus two which maps to the not yet released openshift 4.4 and the current openshift 4.3.

Having said that our (as red hat) downstream product openshift-pipelines is not yet GA and we are still working out on our support matrices on how to best support different versions.

(and just fyi, it is not just for this only one bug that we updated knative/pkg)

@chmouel
Copy link
Member

chmouel commented Mar 9, 2020

(sorry for the duplication between vincent and my comment, but basically we are both saying the same thing :) )

@disposab1e
Copy link
Author

@chmouel @vdemeester Thanks for clarification!

BUT: Have a look at your own documentation at install.md

Headline: Installing Tekton Pipelines on OpenShift/MiniShift

Minishift NEVER was OpenShift 4 ;-)

@vdemeester
Copy link
Member

@disposab1e yeah… this needs to go 😓 This was there on the early days (when it was still knative/build-pipeline 😅)

@disposab1e
Copy link
Author

@vdemeester times change.. quickly :-)

@disposab1e
Copy link
Author

Btw.. I was able to install latest tekton release in OpenShift 3.11, everything was fine... but than the workspace in the tasks (pvc) was missing... I think this is because of the different handling with sidecars... so I failed late :-(

@tekton-robot
Copy link
Collaborator

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Collaborator

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

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Collaborator

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/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.

@tekton-robot tekton-robot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Aug 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Issues or PRs that are questions around the project or a particular feature lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants