I upgraded our cluster to 1.4 and GCI which caused multiple of our 
deployments to stop working. I created a new node pool and specified the 
old container image and the deployments started working again.

After some testing it looks like all the docker images has problem binding 
to the correct interfaces.
Testing a simple ruby container running a bare bones sinatra app fails to 
run on a GCI node but succeeds when binding to 0.0.0.0. (If you are 
interested i would be happy to push the sinatra app and dockerfiles to 
github)

We also run a spray-can container using the java image which seems to have 
some problems even though binding to 0.0.0.0.

I solved it by binding sinatra to 0.0.0.0 but as i said i still have some 
problem with the java app, but i havent had time that much time testing the 
java app yet.
But this still looks like a different behaviour/gap when comparing to the 
old containerVM.


Den onsdag 5 oktober 2016 kl. 19:51:25 UTC+2 skrev Alexander Mohr:
>
> ... and if anyone has other requests or notices other gaps between GCI and 
> the older containerVM, please do let us know!
>
> On Wed, Oct 5, 2016 at 10:50 AM, 'Vishnu Kannan' via Kubernetes user 
> discussion and Q&A <[email protected] <javascript:>> wrote:
>
>> FYI: We are also actively working on adding support for Gluster in GCI. 
>> #34127 <https://github.com/kubernetes/kubernetes/issues/34127> tracks 
>> the integration. 
>>
>>
>> On Wed, Oct 5, 2016 at 10:27 AM, 'Alex Mohr' via Kubernetes user 
>> discussion and Q&A <[email protected] <javascript:>> wrote:
>>
>>> Joshua and Hilda, I don't think it will affect future upgrades if you 
>>> use the older image for now.
>>>
>>> In more detail, we plan to release 1.5 in early-to-mid December; that 
>>> version is likely to only support the newer ContainerVM image because the 
>>> older version is based on an upstream-deprecated Debian 7.  Until then, 1.4 
>>> will fully support the older version of the image and we'll be sure to have 
>>> a node upgrade path to 1.5 nodes running the newer image.
>>>
>>> On Wed, Oct 5, 2016 at 7:13 AM, Hilda Merom <[email protected] 
>>> <javascript:>> wrote:
>>>
>>>> +1 I'm facing the same problem
>>>>
>>>> On Thursday, September 29, 2016 at 6:37:02 PM UTC+7, Joshua Sindy wrote:
>>>>>
>>>>> GKE 1.3.7 nodes had glusterfs-client available. New 1.4.0 clusters are 
>>>>> missing it. Error: "Output: mount: unknown filesystem type 'glusterfs' ".
>>>>>
>>>>> http://kubernetes.io/docs/user-guide/volumes/ still shows glusterfs 
>>>>> as an option.
>>>>>
>>>>> Would be ideal to get the client back in the image.
>>>>>
>>>>> If that is not possible I would like instruction on how to add it in a 
>>>>> programatic way. I haven't been able to find any documentation on doing 
>>>>> that.
>>>>>
>>>>> Thanks.
>>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "Kubernetes user discussion and Q&A" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to [email protected] <javascript:>.
>>>> To post to this group, send email to [email protected] 
>>>> <javascript:>.
>>>> Visit this group at https://groups.google.com/group/kubernetes-users.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Kubernetes user discussion and Q&A" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected] <javascript:>.
>>> To post to this group, send email to [email protected] 
>>> <javascript:>.
>>> Visit this group at https://groups.google.com/group/kubernetes-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Kubernetes user discussion and Q&A" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/kubernetes-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.
  • [kubernetes-u... Joshua Sindy
    • Re: [kub... 'Alex Mohr' via Kubernetes user discussion and Q&A
    • [kuberne... Hilda Merom
      • Re: ... 'Alex Mohr' via Kubernetes user discussion and Q&A
        • ... 'Vishnu Kannan' via Kubernetes user discussion and Q&A
          • ... 'Alex Mohr' via Kubernetes user discussion and Q&A
            • ... Joshua Sindy
            • ... Micke Lisinge
              • ... 'David Aronchick' via Kubernetes user discussion and Q&A
                • ... Micke Lisinge
    • [kuberne... László Károlyi
      • [kub... Joshua Sindy
        • ... 'Vishnu Kannan' via Kubernetes user discussion and Q&A
          • ... laplj003
            • ... 'Vishnu Kannan' via Kubernetes user discussion and Q&A
              • ... Jeffery LaPlante
                • ... 'Michael Rubin' via Kubernetes user discussion and Q&A
                • ... 'Jing Xu' via Kubernetes user discussion and Q&A

Reply via email to