Origin: Is 3.11 the last version of Origin/OKD ?
Openshift commercial continues to be regularly updated, but Origin/OKD stays stuck to the 3.11 version since more that one year.
I know it's a community based product, so I'm not blaming anyone, I'm just asking for infos.
Will there be a release 4.x and so on ?
freeeflyer
All 7 comments
It's not the last version of OKD. I don't know if its officially released/annouced but there is a first preview of 4.3 in https://github.com/openshift/okd.
JaroslavMajera
on 20 Nov 2019
Some of the core binaries of OKD v3.11 still are built through Openshift‘s CI and can be found online if you know where. But its nothing „official“. The RPMs are neither signed nor published in the Repos.
Some Docker images are up to two years old. You must patch them with „yum update“ to get them through the security scanner. Some images are built every hour.
I wish there would be an intermediate version available. Maybe some v3..11.1 gets released before OKD4 comes out.
But as @freeeflyer said: it‘s a community project and we can be glad that there are people which take care about it so we can use this great software for free.
jomeier
on 20 Nov 2019
What's the relationship between this repo and the new OKD repo?
mmacfadden
on 15 Dec 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
openshift-bot
on 14 Mar 2020
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
openshift-bot
on 13 Apr 2020
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
openshift-bot
on 13 May 2020
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen.
Mark the issue as fresh by commenting/remove-lifecycle rotten.
Exclude this issue from closing again by commenting/lifecycle frozen./close
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.
openshift-ci-robot
on 13 May 2020
Related issues
crobby
·
4Comments
syui
·
3Comments
crobby
·
4Comments
thescouser89
·
3Comments
tnozicka
·
3Comments
Most helpful comment
Some of the core binaries of OKD v3.11 still are built through Openshift‘s CI and can be found online if you know where. But its nothing „official“. The RPMs are neither signed nor published in the Repos.
Some Docker images are up to two years old. You must patch them with „yum update“ to get them through the security scanner. Some images are built every hour.
I wish there would be an intermediate version available. Maybe some v3..11.1 gets released before OKD4 comes out.
But as @freeeflyer said: it‘s a community project and we can be glad that there are people which take care about it so we can use this great software for free.