In case anyone else is curious for more details, the links
appear to be:
On Wed, May 25, 2016, at 10:38 PM, Clayton Coleman wrote:
> Stay tuned - 1.3 has a lot of exciting changes, and the next alpha.2
> will include PetSets
https://github.com/kubernetes/kubernetes/issues/260
> init containers
Under https://github.com/openshift/origin/releases
it looks like there was never a "non-prerelease" 1.5. Now we're
on the train to 3.6 (which makes sense to me).
Currently in Fedora, all versions are 1.4:
https://bodhi.fedoraproject.org/updates/?packages=origin
The CentOS PaaS SIG built 1.5rc:
On Thu, Jun 20, 2019, at 5:20 PM, Clayton Coleman wrote:
> Because the operating system integration is so critical, we need to
> make sure that the major components (ostree, ignition, and the kubelet)
> are tied together in a CoreOS distribution that can be quickly
> refreshed with OKD -
On Wed, Jun 26, 2019, at 1:10 PM, Colin Walters wrote:
> The tricky thing here is...if we want this to work the same as OpenShift 4/OCP
> with RHEL CoreOS, then what we're really talking about here is a *derivative*
> of FCOS that for example embeds the kubelet from OKD. And s
On Fri, Jul 12, 2019, at 10:19 AM, Neal Gompa wrote:
> Fedora didn't shut down its users@ list when it deployed
> discussions.fp.o. And adoption of Discourse in Fedora hasn't been very
> high outside of the Silverblue/CoreOS bubble.
Eh, but the traditional Fedora community has a pretty high
Hi,
I think the Common's use of Slack is not a good match for "support". Requiring
an invitation is also an impediment to quickly asking questions. Further Slack
is proprietary, and also any discussion there won't be easily found by Google.
On the other hand we have these mailing lists,
On Wed, Jul 24, 2019, at 10:40 AM, Michael Gugino wrote:
> I tried FCoS prior to the release by using the assembler on github.
> Too much secret sauce in how to actually construct an image. I
> thought atomic was much more polished, not really sure what the
> value-add of ignition is in this
