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
Yes sure! If acme servers can't join your routers the HTTP challenge can't
be validated.
Maybe it could be nice to add optional support to this in openshift-ansible:
- deploy openshift-acme
- create a route in front of the kubernetes service with the proper
annotation
Le jeu. 6 sept. 2018 à
Very nice Mickael !
Just a minor note (although i'm sure you know already) if others bump into
this thread, this method works for public domains but it won't work if your
domain is internal/ dev one (i.e - .local).
Dani
On Wed, Sep 5, 2018 at 4:11 PM Mickaël Canévet
wrote:
> Thanks a lot
