search

openshift / origin

Conformance test suite for OpenShift
http://www.openshift.org
Apache License 2.0
8.47k stars 4.7k forks source link

Release 4.1 #23188

Closed ricardo-aspira closed 3 years ago

ricardo-aspira commented 5 years ago

Guys, I did not find any information about the release date of OKD 4.1. Do you guys know?

Thank you so much.

ted-bunny commented 5 years ago

Hey, check this blog post out about okd4 and its future:

https://blog.openshift.com/openshift-commons-briefing-okd4-release-and-road-map-update-with-clayton-coleman-red-hat/

edysli commented 5 years ago

@ted-bunny That blog post doesn't really explain why this project's releases page barely has a "4.1.0" tag (and no binaries to download) while RedHat already released OpenShift Container Platform 4.1 a month ago, does it?

ted-bunny commented 5 years ago

Hello @edysli

@ted-bunny That blog post doesn't really explain why this project's releases page barely has a "4.1.0" tag (and no binaries to download) (...)

No, it doesn't

(...) while RedHat already released OpenShift Container Platform 4.1 a month ago, does it?

At least it clarifies a bit why OKD hadn't a 4.0 release so far.

normanschlatter commented 5 years ago

fyi 4.1 is missing the Dev Console and you cant install it offline, in a nutshell its a unfinished product, I already deployed 4.1 on premise.

wait for 4.2

image

mliker commented 5 years ago

Hi @normanschlatter can you share your notes on on premise okd 4.1 install? I don't mind the missing bits a pieces since I build and run Openshift clusters for living and would like to familiarise myself with the new stack.

normanschlatter commented 5 years ago

Hi @normanschlatter can you share your notes on on premise okd 4.1 install? I don't mind the missing bits a pieces since I build and run Openshift clusters for living and would like to familiarise myself with the new stack.

sorry, Im talking about OCP, OKD isnt ready right now, there is no Fedora CoreOS download right now available, please see: https://blog.openshift.com/openshift-commons-briefing-okd4-release-and-road-map-update-with-clayton-coleman-red-hat/

amalic commented 5 years ago

It is becoming obvious that OKD has only low priority at Redhat/IBM.

Here's what is completelly useless for the community:

What the community wants to see:

If OpenShift continues this path, I see the community looking for alternatives, and recommending other products at their workplaces.

To IBM: Here's how Open Source nowadays works. Organisations who can afford Enterprise Support will always go with this option if available. Organisations who can not afford Enterprise Support will use the community version or alternatives that work. People who have good experience with an Open Source product are very likley to recommend the Enterprise Version of this product at their day-time jobs.

jkroepke commented 5 years ago

I recommend to look for alternative before installing OKD 4.

If you really want to use Openshift you have to buy a subscription.

amalic commented 5 years ago

Don't get me wrong. I have 3.11 running, and am mostly happy with it.

But at some point projects will require Kubernetes 1.12 and higher. And if there's no upgrade path, people will look for alternatives.

My organisation can not afford an infrastructure group for on-premise cloud computing. And even less permanent public cloud resources to host services and data through public funds.

philipp1992 commented 5 years ago

any news on this? is there any official information about when the open-source version of OpenShift 4.x will be released and installable?

jkroepke commented 5 years ago

@philipp1992 since Openshift 4 requires RH CoreOS we have to wait utils Fedora CoreOS is ready.

https://getfedora.org/en/coreos/download/

gpowers01 commented 4 years ago

@philipp1992 since Openshift 4 requires RH CoreOS we have to wait utils Fedora CoreOS is ready.

https://getfedora.org/en/coreos/download/

I understand that Fedora CoreOS is a dependency, but is there any back of the napkin guess on the overall release schedule? Q4 CY2019? Q1CY2020?

ThinkBriK commented 4 years ago

The stable release of Fedora CoreOS is expected in late 2019 From https://github.com/coreos/fedora-coreos-tracker

ricardo-aspira commented 4 years ago

My main concern is how we would be able to migrate from 3.11 to 4.1 or 4.2.

aneagoe commented 4 years ago

afaik it won't be possible to upgrade from 3.11 to 4.x. however, migrating resources and projects should be trivial. With an external LB, you should have an easy time setting up a separate 4.x cluster and migrate workloads at your convenience. You get a fresh start and probably drop a lot of baggage you've accumulated in 3.11. And on the upside, once you're on 4.x it should be trivial to stay up to date. While I agree there's some appeal in having some form of upgrade from 3.x to 4.x, in reality it's something quite complex and error prone, with high chances of failure. Even if there was such a thing, I'd still prefer a fresh deployment as a safer migration path.

manuel1733 commented 4 years ago

is a little frustrating to have openshift commercial 4x available for month and no progress nor timeline for openshift open-source . as I understand the Red Hat business model that they create commercial products from the open-source base and do some hardening. am I misunderstanding something ?

shinebayar-g commented 4 years ago

This is no brainer, they don't wanna release open source version for community. :P 🙄

check this out https://www.youtube.com/watch?v=XXpr-ESIbDU

sapkra commented 4 years ago

They have to wait until Fedora CoreOS is stable and have to adapt the docs and installer scripts I guess.

The Fedora release is scheduled for late 2019.

aneagoe commented 4 years ago

As per https://blog.openshift.com/introducing-red-hat-openshift-4-2-developers-get-an-expanded-and-improved-toolbox (section "Note for community users of OKD") RedHat has actively started working on releasing OKD 4.x. Even more information can be found on the forum: https://groups.google.com/forum/#!forum/okd-wg However, it is somewhat frustrating to have to go out of your way to understand the current state of affairs with OKD. Communication around OKD seems to be in need of improvement.

h-vetinari commented 4 years ago

Fedora CoreOs has an associated github project that gives an overview over the open issues. Late 2019 seems ambituous IMO, but maybe the tracker is not fully representative / up to date.

Also, a roadmap for OKD was merged in openshift/community#55 about a week ago.

aistellar commented 4 years ago

Com'on guys, it's been over a year since the last stable release of OKD...

ricardo-aspira commented 4 years ago

I have just migrated to Rancher.

On Sun, Nov 10, 2019, 6:58 AM shulinwz notifications@github.com wrote:

Com'on guys, it's been over a year since the last stable release of OKD...

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/openshift/origin/issues/23188?email_source=notifications&email_token=ABVZXPBPJX4AEUFL7S44IM3QS7LKRA5CNFSM4HYWPWJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDUZRWQ#issuecomment-552179930, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVZXPGWW2PNC2BJWZFSPTDQS7LKRANCNFSM4HYWPWJA .

h-vetinari commented 4 years ago

Some movement with https://github.com/openshift/origin/commit/8189ff86d2478d3701c3aa0e7486de7db07ec2ad (pointing to new OKD info repo), first preview release here...

OKD4 github project here.

warmchang commented 4 years ago

[OKD 4.x]: first preview drop https://lists.openshift.redhat.com/openshift-archives/dev/2019-November/msg00005.html https://mobile.twitter.com/smarterclayton/status/1196477646885965824

openshift-bot commented 4 years ago

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 commented 4 years ago

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

anroots commented 4 years ago

This is ironic :point_up:

Openshift 4 / OKD 4 seems stale + rotten. To the developers - I appreciate the work you've been doing (especially on Openshift 3.x OS); but comms around progress / timeline + visible "moving forward" are not optimal. As a community user, I've been trying to figure out what's going on, but can't get a conclusive, clear answer. Best I gathered is that The Company has sidelined/ditched the open source project and only separated a small dev team to it; for lip service. Roadmap seems to always be Soon :tm:.

Hence, after a year+ of silence (and commercial version already being 3 releases ahead), I'm ditching Openshift and moving to vanilla Kubernetes - who has regular releases and is still supported open-source. I will miss Openshift, but I can't see a clear future with it.

If OpenShift continues this path, I see the community looking for alternatives, and recommending other products at their workplaces.

is a little frustrating to have openshift commercial 4x available for month and no progress nor timeline for openshift open-source

Please fix comms around the project to keep others with it. Say clearly what's going on, and what to expect - especially with timelines. Clarify how much effort is put to it compared to the commercial version.

:wave: , :bowing_man: - :fish:

edysli commented 4 years ago

/remove-lifecycle rotten please? I'd like to see an official reply here.

claudio-walser commented 4 years ago

I am in the same boat, this is kind of a joke. I was a huge fan of coreos. Had a hard time to learn/adapt about fedora coreos and redhat enterprise linux coreos. Was confused about openshift as well, installed a ocp 4 cluster to learn i would need to pay around 60k for licensing my hardware. Gave okd a 4 preview a chance and am now waiting for a stable okd 4 release for a full year. You are loosing a lot of people because of this and as an enduser, it feels like kind of a big mess. Okd vs ocp is a bit like fcos vs rhelcos. Open Source Versions are upstream, paid versions have stable releases but the os version of both have kind of unsure futures. I really don't get this.

I might shift to vanilla kubernetes as well within the next few weeks... Which is sad, i liked openshift alot but what happens here is not acceptable.

philipp1992 commented 4 years ago

Please fix comms around the project to keep others with it. Say clearly what's going on, and what to expect - especially with timelines. Clarify how much effort is put to it compared to the commercial version.

@dmueller2001 is there an official statement from RH regarding the state of OKD4? Will it become the upstream to RH OpenShift in the future again? Ive followed development of OKD4 and i also think its really sad, that RH is not putting more resources into it.

claudio-walser commented 4 years ago

Latest Meeting Minutes are interesting regarding the release timeline: https://youtu.be/VSnerYEzxtE?t=904

vboufleur commented 4 years ago

The video posted in the comment above says that OKD 4 will probably be released together with OCP 4.5 in June or July, this year.

openshift-bot commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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-ci-robot commented 3 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/origin/issues/23188#issuecomment-748631333): >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](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.