It just detects. It checks the operating system type. You don’t even need
to change the inventory at all. As rpms are only supported on Centos and
containerised only on Atomic
On Mon, 7 Jan 2019 at 7:47 pm, mabi wrote:
> ‐‐‐ Original Message ‐‐‐
> On Sunday, January 6, 2019 11:13 PM,
‐‐‐ Original Message ‐‐‐
On Sunday, January 6, 2019 11:13 PM, Joel Pearson
wrote:
> It looks like the RPMs will eventually get the security fix according to the
> other reply from Daniel Comnea. But with containers you could have a fix
> within a day as opposed to waiting for new tag
Hi all,
I don't think RPMs have a critical security vulnerability. The module in
problem should be origin-control-plane [1], which is container running within
OKD 3.11. I have two OKD 3.11 clusters , on each master node, I ran
docker pull docker.io/openshift/origin-control-plane:v3.11
On Mon, 7 Jan 2019 at 8:01 am, mabi wrote:
> ‐‐‐ Original Message ‐‐‐
> On Sunday, January 6, 2019 12:28 PM, Joel Pearson <
> japear...@agiledigital.com.au> wrote:
>
> I think it's worth mentioning here that the RPMs at
> http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/
‐‐‐ Original Message ‐‐‐
On Sunday, January 6, 2019 12:28 PM, Joel Pearson
wrote:
> I think it's worth mentioning here that the RPMs at
> http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/ have a
> critical security vulnerability, I think it's unsafe to use the RPMs if
Joel & all,
On the CVE subject you are correct however if you read [1] you will better
understand a) the PaaS sig process on how the Origin rpm is getting build
(based on the Origin release tag) and b) what is holding on getting a new
Origin v3.11 rpm out
Hope that helps a bit
Dani
[1]
I think it's worth mentioning here that the RPMs at
http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/ have a
critical security vulnerability, I think it's unsafe to use the RPMs if
you're planning on having your cluster available on the internet.
‐‐‐ Original Message ‐‐‐
On Saturday, January 5, 2019 3:57 PM, Daniel Comnea
wrote:
> [DC]: i think you are a bit confused: there are 2 ways to get the rpms from
> CentOS yum repo: using the generic repo [1] which will always have the latest
> origin release OR [2] where i've
On Sat, Jan 5, 2019 at 10:03 AM mabi wrote:
> ‐‐‐ Original Message ‐‐‐
> On Saturday, January 5, 2019 10:57 AM, Daniel Comnea <
> comnea.d...@gmail.com> wrote:
>
> The specific openshift release directory been present for a long time.
> Saying that i'll work next week in pushing v3.11
‐‐‐ Original Message ‐‐‐
On Saturday, January 5, 2019 10:57 AM, Daniel Comnea
wrote:
> The specific openshift release directory been present for a long time.
> Saying that i'll work next week in pushing v3.11 rpms to
> http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/ too
The specific openshift release directory been present for a long time.
Saying that i'll work next week in pushing v3.11 rpms to
http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/ too
Dani
On Fri, Jan 4, 2019 at 10:41 PM mabi wrote:
> ‐‐‐ Original Message ‐‐‐
> On Friday,
‐‐‐ Original Message ‐‐‐
On Friday, January 4, 2019 11:15 PM, Erik McCormick
wrote:
> Change it to use:
> http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/
I see, so now there is one directory per version released and not all versions
in the same openshift-origin
On Fri, Jan 4, 2019, 4:30 PM mabi Hello,
>
> I am currently running an OKD 3.10 cluster on a few CentOS 7.6 nodes and
> would like to upgrade to 3.11. Unfortunately I noticed that the official
> CentOS 7 paas repo (
> http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/) still
> does
Hello,
I am currently running an OKD 3.10 cluster on a few CentOS 7.6 nodes and would
like to upgrade to 3.11. Unfortunately I noticed that the official CentOS 7
paas repo (http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/)
still does not contain the RPMs for version 3.11. I read
14 matches
Mail list logo
