Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-07-24 Thread Dusty Mabe
On 06/29/2018 08:42 AM, Stephen Gallagher wrote: > > > On Fri, Jun 29, 2018 at 8:32 AM Daniel Walsh > wrote: > > Users of OpenSHift Origin require CRI-O 1.10 right now.  But Kubernetes > users want to try out the latest packages for kubernetes 1.11 which >

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-07-02 Thread Jan Chaloupka
On 06/30/2018 05:05 PM, Nicolas Mailhot wrote: Le samedi 30 juin 2018 à 14:22 +0200, Tomasz Torcz a écrit : BTW, kubernetes package is quite pathological. Installing it brings kubernetes-master, which contains following four binaries: -rwxr-xr-x. 3 root root 152M 04-26 11:34

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-07-02 Thread Jakub Cajka
- Original Message - > From: "Nicolas Mailhot" > To: "Development discussions related to Fedora" > > Cc: dwa...@redhat.com, mpa...@redhat.com, run...@redhat.com > Sent: Saturday, June 30, 2018 12:46:28 PM > Subject: Re: In the OpenShift

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-30 Thread Lokesh Mandvekar
On Sat, Jun 30, 2018 at 01:22:46PM +0200, Nicolas Mailhot wrote: > Le samedi 30 juin 2018 à 12:46 +0200, Nicolas Mailhot a écrit : > > Le vendredi 29 juin 2018 à 12:19 -0400, Lokesh Mandvekar a écrit : > > > FWIW, a fun read from the debian pkg-go list about packaging docker > > >

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-30 Thread Lokesh Mandvekar
On Sat, Jun 30, 2018 at 12:46:28PM +0200, Nicolas Mailhot wrote: > Le vendredi 29 juin 2018 à 12:19 -0400, Lokesh Mandvekar a écrit : > > FWIW, a fun read from the debian pkg-go list about packaging docker > > https://www.mail-archive.com/pkg-go-maintainers@alioth-lists.debian.ne > >

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-30 Thread Nicolas Mailhot
Le samedi 30 juin 2018 à 14:22 +0200, Tomasz Torcz a écrit : > > BTW, kubernetes package is quite pathological. Installing it brings > kubernetes-master, which contains following four binaries: > > -rwxr-xr-x. 3 root root 152M 04-26 11:34 /usr/bin/hyperkube > -rwxr-xr--. 1 root kube 128M

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-30 Thread Tomasz Torcz
On Sat, Jun 30, 2018 at 12:46:28PM +0200, Nicolas Mailhot wrote: > Le vendredi 29 juin 2018 à 12:19 -0400, Lokesh Mandvekar a écrit : > > FWIW, a fun read from the debian pkg-go list about packaging docker > > https://www.mail-archive.com/pkg-go-maintainers@alioth-lists.debian.ne > >

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-30 Thread Nicolas Mailhot
Le samedi 30 juin 2018 à 12:46 +0200, Nicolas Mailhot a écrit : > Le vendredi 29 juin 2018 à 12:19 -0400, Lokesh Mandvekar a écrit : > > FWIW, a fun read from the debian pkg-go list about packaging docker > > https://www.mail-archive.com/pkg-go-maintainers@alioth-lists.debian. > > ne > >

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-30 Thread Nicolas Mailhot
Le vendredi 29 juin 2018 à 12:19 -0400, Lokesh Mandvekar a écrit : > FWIW, a fun read from the debian pkg-go list about packaging docker > https://www.mail-archive.com/pkg-go-maintainers@alioth-lists.debian.ne > t/msg00032.html And so what? I hit this problem months ago (and I have the github

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-29 Thread Robert-André Mauchin
On vendredi 29 juin 2018 18:19:23 CEST Lokesh Mandvekar wrote: > FWIW, a fun read from the debian pkg-go list about packaging docker > https://www.mail-archive.com/pkg-go-maintainers@alioth-lists.debian.net/msg0 > 0032.html I wish we had a formal Go Packaging Team like them. It would be more

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-29 Thread Lokesh Mandvekar
FWIW, a fun read from the debian pkg-go list about packaging docker https://www.mail-archive.com/pkg-go-maintainers@alioth-lists.debian.net/msg00032.html On Fri, Jun 29, 2018 at 12:09:06PM -0400, Lokesh Mandvekar wrote: > On Fri, Jun 29, 2018 at 11:43:11AM -0400, Neal Gompa wrote: > > On Fri,

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-29 Thread Lokesh Mandvekar
On Fri, Jun 29, 2018 at 11:43:11AM -0400, Neal Gompa wrote: > On Fri, Jun 29, 2018 at 11:41 AM Lokesh Mandvekar > wrote: > > > > On Fri, Jun 29, 2018 at 04:03:28PM +0200, Nicolas Mailhot wrote: > > > Le 2018-06-29 14:31, Daniel Walsh a écrit : > > > > > > Hi, > > > > > > > Users of OpenSHift

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-29 Thread Neal Gompa
On Fri, Jun 29, 2018 at 11:41 AM Lokesh Mandvekar wrote: > > On Fri, Jun 29, 2018 at 04:03:28PM +0200, Nicolas Mailhot wrote: > > Le 2018-06-29 14:31, Daniel Walsh a écrit : > > > > Hi, > > > > > Users of OpenSHift Origin require CRI-O 1.10 right now. But > > > Kubernetes users want to try out

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-29 Thread Lokesh Mandvekar
On Fri, Jun 29, 2018 at 04:03:28PM +0200, Nicolas Mailhot wrote: > Le 2018-06-29 14:31, Daniel Walsh a écrit : > > Hi, > > > Users of OpenSHift Origin require CRI-O 1.10 right now.  But > > Kubernetes users want to try out the latest packages for kubernetes > > 1.11 which would require CRI-O

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-29 Thread Daniel Walsh
On 06/29/2018 10:03 AM, Nicolas Mailhot wrote: Le 2018-06-29 14:31, Daniel Walsh a écrit : Hi, Users of OpenSHift Origin require CRI-O 1.10 right now.  But Kubernetes users want to try out the latest packages for kubernetes 1.11 which would require CRI-O 1.11.  Origin might not be ready to

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-29 Thread Nicolas Mailhot
Le 2018-06-29 14:31, Daniel Walsh a écrit : Hi, Users of OpenSHift Origin require CRI-O 1.10 right now.  But Kubernetes users want to try out the latest packages for kubernetes 1.11 which would require CRI-O 1.11.  Origin might not be ready to move to Kubernetes 1.11 for a while. Bottom line

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-29 Thread Stephen Gallagher
On Fri, Jun 29, 2018 at 8:42 AM Stephen Gallagher wrote: > On Fri, Jun 29, 2018 at 8:32 AM Daniel Walsh wrote: > >> Users of OpenSHift Origin require CRI-O 1.10 right now. But Kubernetes >> users want to try out the latest packages for kubernetes 1.11 which >> would require CRI-O 1.11. Origin

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-29 Thread Stephen Gallagher
On Fri, Jun 29, 2018 at 8:32 AM Daniel Walsh wrote: > Users of OpenSHift Origin require CRI-O 1.10 right now. But Kubernetes > users want to try out the latest packages for kubernetes 1.11 which > would require CRI-O 1.11. Origin might not be ready to move to > Kubernetes 1.11 for a while. > >

In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

2018-06-29 Thread Daniel Walsh
Users of OpenSHift Origin require CRI-O 1.10 right now.  But Kubernetes users want to try out the latest packages for kubernetes 1.11 which would require CRI-O 1.11.  Origin might not be ready to move to Kubernetes 1.11 for a while. Bottom line we want to be able to ship CRI-0 1.10.* and