Re: [kubernetes-users] cos-stable-59 breaks kubelet launch

Got it working with projects/cos-cloud/global/images/cos-dev-62-9901-8-0 Em sábado, 9 de setembro de 2017 00:50:51 UTC-3, Ronoaldo Pereira escreveu: > > While I'm not mounting a device, I am trying to figure out a way to port > the old container-vm-* to the new cos-* and I am facing similar

Re: [kubernetes-users] cos-stable-59 breaks kubelet launch

While I'm not mounting a device, I am trying to figure out a way to port the old container-vm-* to the new cos-* and I am facing similar issues. I am unable to launch a standalone kubelet VM from cos-stable (60*) and have it pick up my google-container-manifest and run the pods there. I did

Re: [kubernetes-users] Re: Kubernetes pulled image with digital instead of tag

An image tag is resolved to a concrete content addressable identifier. So, 1.7.9 is just an easy human understandable shortcut to the content address of f01bde0. The OCI spec sort of explains it here: https://github.com/opencontainers/image-spec/blob/master/image-layout.md#indexjson-file Brandon

Re: [kubernetes-users] RollingUpdate strategy on statefulsets

Can you `kubectl describe statefulset foo`? There might be details there. Also, did you upgrade from 1.6? https://groups.google.com/forum/#!topic/kubernetes-announce/5T8Ah5xuFz8 On Fri, Sep 8, 2017 at 5:51 AM wrote: > Hi, > > currently I am using Kubernetes (v 1.7.4) to

Re: [kubernetes-users] How to get access to the Heapster's Grafana dashboard after clean Kubernetes installation using Rancher

Hello Parth- This isn't a general Kuberentes question so you might get help on the Rancher forums: https://forums.rancher.com/ Brandon On Fri, Sep 8, 2017 at 6:21 AM Parth Gandhi wrote: > I have just installed 3 node kubernetes cluster using rancher. I am trying > to

[kubernetes-users] Overriding kube-dns settings using the config map

I see that kube-dns now has support for a config map, as well as the ability to override some config settings by updating the contents of the map: http://blog.kubernetes.io/2017/04/configuring-private-dns-zones-upstream-nameservers-kubernetes.html Is it possible to override all kube-dns settings

Re: [kubernetes-users] FQDN's for pods?

Ah, there we are.  That worked!  (Even on the v1.5.2 that ships with Centos 7.) I set the subdomain to "pod" and now I see the following: [centos@ip-172-31-93-54 ~]$ kubectl exec -it custom-django-app-1796634124-7jmd4 /bin/bash root@custom-django-app-1796634124-7jmd4:/django-apps/challenge1#

Re: [kubernetes-users] FQDN's for pods?

We don't set the FQDN at all unless you specify the `subdomain` field in Pod.spec. That could be a bug, but the assumption is that the FQDN is "about" DNS lookup-ability. We could have that conversation, though. On Fri, Sep 8, 2017 at 8:39 AM, David Rosenstrauch wrote: > On

Re: [kubernetes-users] FQDN's for pods?

On 2017-09-06 2:42 pm, David Rosenstrauch wrote: On 2017-09-06 2:36 pm, Matthias Rampke wrote: TL;DR when you set the cluster domain, this should Just Work™ in Kubernetes 1.7+ but not before That's good news! I'll start to look into us upgrading to a newer version. Hmmm ... some bad

[kubernetes-users] RollingUpdate strategy on statefulsets

Hi, currently I am using Kubernetes (v 1.7.4) to deploy a Lagom microservices application. Each service is represented by a statefulset with a RollingUpdate update strategy. I read in this documentation

Re: [kubernetes-users] Kubernetes API behind reverse proxy

I have same problem as you Torsten. Did you found a solution to forward the certificate ? On Saturday, 4 February 2017 07:38:15 UTC+1, Torsten Bronger wrote: > > Hallöchen! > > Alex Creek writes: > > > [...] > > > > I settled with the stream_proxy module I mentioned before and just > >

[kubernetes-users] Re: Kubernetes pulled image with digital instead of tag

The 'digital' in title should be 'digest' On Friday, 8 September 2017 13:55:35 UTC+8, Yong Zhang wrote: > > Hi, all > > I have a very tricky issue here, I defined image with tag in > deployment.yaml like this: > > apiVersion: apps/v1beta1kind: Deploymentmetadata: > name: nginx-deploymentspec: