Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

example #3

Open
chechuironman opened this issue Nov 7, 2019 · 4 comments
Open

example #3

chechuironman opened this issue Nov 7, 2019 · 4 comments

Comments

@chechuironman
Copy link

is there any example??

I'm running the busybox example from teh root repo, removing the tolerations for azure...and get provider error:

time="2019-11-07T15:04:02+01:00" level=info msg="receive CreatePod \"busyecho2\""
time="2019-11-07T15:04:02+01:00" level=info msg="Updated k8s pod status" key=default/busyecho2 method=createOrUpdatePod name=busyecho2 namespace=default node=virtual-kubelet operatingSystem=Linux phase=Pending pod=busyecho2 podPhase=Pending provider=cri reason=ProviderFailed uid=52edc4f3-0167-11ea-a9a4-00505681174c watchedNamespace= workerId=10
time="2019-11-07T15:04:02+01:00" level=warning msg="requeuing [[\"default/busyecho2\"]] due to failed sync" error="failed to sync pod \"default/busyecho2\" in the provider: rpc error: code = Unknown desc = failed to setup network for sandbox \"b5b746ecf1193f3cab8e144ece3df574e5de815fba5a14da44007f25cae58ccd\": cni plugin not initialized" key=default/busyecho2 method=handleQueueItem node=virtual-kubelet operatingSystem=Linux provider=cri watchedNamespace= workerId=10```

listing the pods:

```root@uubelet20:~# kubectl  get pods
NAME                       READY   STATUS           RESTARTS   AGE
busyecho2                  0/1     ProviderFailed   0          1m
busyecho2xy                0/1     Pending          0          5m
docker-registry-1-fqsxw    1/1     Running          0          21d
registry-console-1-2xhzt   1/1     Running          0          21d
router-1-ck75m             1/1     Running          0          21d
router-1-x27sm             1/1     Running          1          21d```

any idea?
@chechuironman
Copy link
Author

also got this:

Error from server: Get https://virtual-kubelet:10250/containerLogs/default/busyecho2/nginx: x509: certificate is valid for system:admin, not virtual-kubelet```

@cpuguy83
Copy link
Collaborator

You need to setup CNI on the node.

@chechuironman
Copy link
Author

Thanks @cpuguy83 , could you point me to a doc that I can follow to do it ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants