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

Thank you Daniel for your pointers. I am a kubernetes newbie so wanted to clarify in order to more fully understand your answer: 1) "we're fixing this": does it mean some "cos-stable-6*" release will run this again as cos-stable-58 was, or would I need to make some edits (kubernetes config vars

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

cos-stable-59 upgraded the built-in kubelet to 1.6, which replaced the deprecated flag `--config` with `--pod-manifest-path`. https:/ /github.com/kubernetes/kubernetes/pull/40048/commits/ bec6635ccc05b1f02c9971ec9bf529faac0b9ca1 We're fixing this at our end. For the interim, updating /etc/default/

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

On Fri, Jun 9, 2017 at 10:56 AM, Vishnu Kannan wrote: > +cos team > > On Fri, Jun 9, 2017 at 1:15 AM, Pavel wrote: > >> As of cos-stable-58-9334-74-0, I was able to launch a kubelet on a single >> compute instance with: >> >> --metadata-from-file \ >> "google-container-manifest=containers.yaml,u

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

+cos team On Fri, Jun 9, 2017 at 1:15 AM, Pavel wrote: > As of cos-stable-58-9334-74-0, I was able to launch a kubelet on a single > compute instance with: > > --metadata-from-file \ > "google-container-manifest=containers.yaml,user-data=cloudinit.yaml" \ > > where cloudinit.yaml contains the fo

Re: [kubernetes-users] Authentication on GKE

On the cluster details page on https://console.cloud.google.com/kubernetes , if you have upgraded to 1.6 (I think?), you should see the following drop down to edit an existing cluster. I haven't yet attempted this personally:

Re: [kubernetes-users] Authentication on GKE

https://cloud.google.com/container-engine/docs/role-based-access-control mentions that you can create a cluster with the --no-enable-legacy-authorization flag. On Thursday, June 8, 2017 at 12:53:41 PM UTC-4, timo.r...@holidaycheck.com wrote: > > Any update on this one? IAM seems to be supporte

[kubernetes-users] How to install nginx ingress controller on a 3-node K8s cluster of CentOS 7 VMs

Hi I have a running 3-node K8s cluster running in 3 Virtualbox VMS on a laptop. I'd like to use the nginx-ingress-controller to expose a simple NGINX service to my host (the laptop). However I cannot find any reliable documentation showing how to set this up. Would anyone have a link, or a few

[kubernetes-users] Re: kubeadm init hangs forever at: "[apiclient] Created API client, waiting for the control plane to become ready"

Got this working eventually, will post a link when I figure out how ... -- 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 kubernetes-users+un

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

As of cos-stable-58-9334-74-0, I was able to launch a kubelet on a single compute instance with: --metadata-from-file \ "google-container-manifest=containers.yaml,user-data=cloudinit.yaml" \ where cloudinit.yaml contains the following: #cloud-configs runcmd: - systemctl start kubelet.service