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 issue
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 wha
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
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/
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
+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
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
