Cannot schedule pods on the Windows node

kubernetes-sigs / sig-windows-dev-tools

This is a batteries included local development environment for Kubernetes on Windows.

Apache License 2.0

80 stars 46 forks source link

Cannot schedule pods on the Windows node #189

Closed luckerby closed 2 years ago

luckerby commented 2 years ago

After completing the setup for the 2 nodes-setup (1x Linux control plane node and 1x Windows worker node), and ensuring that the configuration is finished on both nodes (due to #188 this currently means pasting the 1-antrea.ps1 file in an SSH connection on the Windows node (the file cannot be accessed by going to C:\sync\windows) for whatever reason)) trying to schedule a pod on the Windows node doesn't work as expected:

  Warning  FailedCreatePodSandBox  22s (x105 over 23m)  kubelet  (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "9125a4d13f634963a8f635f987c5be41d826fb5f9400ff2aa80706db6a929da5": rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing open \\\\.\\pipe\\cnisock: The system cannot find the file specified."

There is an issue opened on the antrea repo here - currently closed due to inactivity - which further leads to this issue on the containerd repo. As the discussion in the latter doesn't seem to suggest any fix coming soon, is there any workaround for now?

gitisacatsname commented 2 years ago

We are facing the same issue in an airgapped env.

knabben commented 2 years ago

For this issue in particular it's related with the missing OpenSSL installation https://github.com/kubernetes-sigs/sig-windows-dev-tools/issues/188

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

dougsland commented 2 years ago

As @knabben mentioned, related to #188. Closing as dup

dougsland commented 2 years ago

/close

k8s-ci-robot commented 2 years ago

@dougsland: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/sig-windows-dev-tools/issues/189#issuecomment-1232383786): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.