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 etc.) in the cloud init file? I have some automation relying on that and for now forcing "cos-stable-58-...", would like to have a heads up on what to expect from the future VM image releases. 2) "updating /etc/default/kubelet": how can I include that in cloud init yaml file? Also, while we're on this topic, could you please have a look at a related disk mounting issue here: https://stackoverflow.com/questions/44222208/standalone-kubelet-persistent-disk-mount-on-google-cloud-instance Thank you! Pavel On Friday, June 9, 2017 at 11:31:46 AM UTC-7, Daniel Wang wrote: > > 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/kubelet should work. > > On Fri, Jun 9, 2017 at 11:08 AM, Vishnu Kannan <vis...@google.com > <javascript:>> wrote: > >> >> >> On Fri, Jun 9, 2017 at 10:56 AM, Vishnu Kannan <vis...@google.com >> <javascript:>> wrote: >> >>> +cos team >>> >>> On Fri, Jun 9, 2017 at 1:15 AM, Pavel <pavel.p...@gmail.com >>> <javascript:>> 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 following: >>>> >>>> #cloud-configs >>>> >>>> runcmd: >>>> - systemctl start kubelet.service >>>> >>>> >>>> Once cos-stable-59 replaced -58 as cos-stable, this setup does not work. >>>> The most relevant log enntry seems to be: >>>> >>>> "Usage of /usr/bin/kubelet: unknown flag: --config" >>>> >>>> Any suggestions on what to modify so that the service starts my >>>> container in the newer Container OS release? 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 kubernetes-use...@googlegroups.com <javascript:>. >>>> To post to this group, send email to kubernet...@googlegroups.com >>>> <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 >> "gke-kubernetes-gci" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to gke-kubernetes-gci+unsubscr...@google.com <javascript:>. >> To post to this group, send email to gke-kuber...@google.com >> <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/a/google.com/d/msgid/gke-kubernetes-gci/CAA_vbqQbJZbHdG3zA3aMYk99u9_iYANVApj-oN2NHeQLVjSgOw%40mail.gmail.com >> >> <https://groups.google.com/a/google.com/d/msgid/gke-kubernetes-gci/CAA_vbqQbJZbHdG3zA3aMYk99u9_iYANVApj-oN2NHeQLVjSgOw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > > > > -- > Best, > Daniel > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
