Closed MarkBoote closed 5 months ago
Please build your own image, see https://github.com/kubernetes-sigs/sig-windows-tools/issues/336#issuecomment-1633854019
Please build your own image, see #336 (comment)
Built my own image, but still had problems starting flannel on windows.
W0829 17:10:51.499936 3824 client_config.go:617] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. W0829 17:10:51.520129 3824 client_config.go:622] error creating inClusterConfig, falling back to default config: open /var/run/secrets/kubernetes.io/serviceaccount/token: The system cannot find the path specified. E0829 17:10:51.531215 3824 main.go:228] Failed to create SubnetManager: fail to create kubernetes config: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable
This turns out to be an issue with containerd.
Existing cluster was running containerd 1.6.22, which gives the above error. I did try updating to 1.7.5, but bumped into issues with flannel getting 'Access Denied' to the etc & opt folders.
Built a lab cluster to reproduce, stopping containerd service, deleting program files/containerd, /etc & /opt folders then installing containerd 1.7.1, everything seems to start without problems.
Might be worth making a note in the docs that latest will NOT work with containerd < 1.7.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Describe the bug Trying to update our windows nodes following the instructions at https://github.com/kubernetes-sigs/sig-windows-tools/blob/master/guides/flannel.md
To Reproduce controlPlaneEndpoint=$(kubectl get configmap -n kube-system kube-proxy -o jsonpath="{.data['kubeconfig.conf']}" | grep server: | sed 's/.*\:\/\///g') kubernetesServiceHost=$(echo $controlPlaneEndpoint | cut -d ":" -f 1) kubernetesServicePort=$(echo $controlPlaneEndpoint | cut -d ":" -f 2) curl -L https://raw.githubusercontent.com/kubernetes-sigs/sig-windows-tools/master/hostprocess/flannel/flanneld/flannel-overlay.yml | sed 's/FLANNEL_VERSION/v0.21.5/g' | sed "s/KUBERNETES_SERVICE_HOST_VALUE/$kubernetesServiceHost/g" | sed "s/KUBERNETES_SERVICE_PORT_VALUE/$kubernetesServicePort/g" | kubectl apply -f -
Expected behavior Kind of hope https://hub.docker.com/r/sigwindowstools/flannel/tags?page=1&name=v0.21.5 would actually exist, what with it being referenced in the documentation.
Kubernetes (please complete the following information):
Additional context Just once it would be nice to be able to upgrade flannel on 'doze without tearing my hair out.