-
Notifications
You must be signed in to change notification settings - Fork 123
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
Could not access default Kubernetes Service inside Windows Pod #84
Comments
See if this helps you #80 |
@oe-hbk no |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@xmapst Could you share the logs of the flannel pod? It looks like this could be a duplicate of #103 (comment) |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen Might be related to this kubernetes/kubernetes#100962 but I am unsure due to lack of knowledge how kube-proxy is supposed to behave and how exactly the networking from pod-to-service is supposed to work. Here is hsndiag from the windows node running a pod in an active cluster:
The endpoints seem correct but it seems that routing from the pod itself is somehow broken. I would be grateful if somebody could refer me to something explaining in detail how the routing is supposed to work exactly. Currently running versions:
|
@dropdeadfu: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Executing ````curl.exe -k https://kubernetes.default.svc.cluster.local``` inside a Windows Pod, but get the following msg:

Using Flannel
VxLan
mode to create a Cluster with one control plane (via RKE) and one Windows Node (via https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes/)Executing into the Windows Pod
curl.exe <other service>
is finecurl.exe https://www.google.com
is finecurl.exe -k https://kubernetes.default.svc.cluster.local
, but get timeout errorNodes info:
Kubernetes version (use
kubectl version
):OS (e.g: cat /etc/os-release):
linux
windows:
Microsoft Windows [Version 10.0.18363.778]
windows hnsdiag info(
hnsdiag list all
):The text was updated successfully, but these errors were encountered: