On Sep 25, 2018, at 6:22 AM, Joel Pearson
wrote:
Clayton, does this mean that in OpenShift 4.0 you'd be able to take a
vanilla kubernetes installation and then install a bunch of OpenShift
operators and basically have an OpenShift cluster?
It’s not really the goal, since there are still
Clayton, does this mean that in OpenShift 4.0 you'd be able to take a
vanilla kubernetes installation and then install a bunch of OpenShift
operators and basically have an OpenShift cluster? Or is that not really
the goal of migration to operators? Is it just to make future OpenShift
releases
Master right now will be labeled 4.0 when 3.11 branches (happening right
now). It’s possible we might later cut a 3.12 but no plans at the current
time.
Changes to master will include significant changes as the core is rewired
with operators - you’ll also see much more focus on preparing
Clayton,
4.0 is that going to be 3.12 rebranded (if we follow the current release
cycle) or 3.13 ?
On Thu, Sep 6, 2018 at 2:34 PM Clayton Coleman wrote:
> The successor to atomic host will be RH CoreOS and the community
> variants. That is slated for 4.0.
>
> > On Sep 6, 2018, at 9:25 AM,
The successor to atomic host will be RH CoreOS and the community
variants. That is slated for 4.0.
> On Sep 6, 2018, at 9:25 AM, Marc Ledent wrote:
>
> Hi all,
>
> I have read in the 3.10 release notes that Atomic Host is deprecated and will
> nod be supported starting release 3.11.
>
> What
Hi all,
I have read in the 3.10 release notes that Atomic Host is deprecated and
will nod be supported starting release 3.11.
What this means? Is it advisable to migrate all Atomic host vms to
"standard" RHEL server?
Kind regards,
Marc
smime.p7s
Description: S/MIME Cryptographic
