search

kubernetes-retired / kpng

[EOL] Reworking kube-proxy's architecture
Apache License 2.0
246 stars 90 forks source link

KPNG ipv6 and ipvs have failing coredns pod #508

Closed knabben closed 7 months ago

knabben commented 1 year ago

What kind of issue is this?

/king bug

Expected behaviour

To have DNS working when using hack/test_e2e.sh to create a cluster

Actual behaviour

coredns-5d78c9869d-td5b9                                   0/1     Running   0               3m53s
coredns-5d78c9869d-tsfgw                                   0/1     Running   0               3m53s

CoreDNS pods are down after the first call to DNS

[INFO] plugin/reload: Running configuration SHA512 = 591cf328cccc12bc490481273e738df59329c62c0b729d94e8b61db9961c2fa5f046dd37f1cf888b953814040d180f52594972691cd6ff41be96639138a43908
CoreDNS-1.10.1
linux/amd64, go1.20, 055b2c3
[ERROR] plugin/errors: 2 3658291695950553688.4197417130289847794. HINFO: dial udp 192.168.0.11:53: connect: network is unreachable
[INFO] Reloading
[INFO] plugin/kubernetes: waiting for Kubernetes API before starting server
[INFO] plugin/kubernetes: waiting for Kubernetes API before starting server
[INFO] plugin/kubernetes: waiting for Kubernetes API before starting server
[INFO] plugin/kubernetes: waiting for Kubernetes API before starting server
[INFO] plugin/kubernetes: waiting for Kubernetes API before starting server
[INFO] plugin/kubernetes: waiting for Kubernetes API before starting server
[INFO] plugin/kubernetes: waiting for Kubernetes API before starting server
[INFO] plugin/kubernetes: waiting for Kubernetes API before starting server
[INFO] plugin/kubernetes: waiting for Kubernetes API before starting server
[WARNING] plugin/kubernetes: starting server with unsynced Kubernetes API
[INFO] plugin/reload: Running configuration SHA512 = 54076864f1b12f95bff4e0e8abfcd67b4e377fb6bd3c7e0642af6252ee2e611075ffa18aa663c2f685d1cf251c3bf093e0db7d12e01399bdb88717dc9feeb7cb
[INFO] Reloading complete
[INFO] plugin/ready: Still waiting on: "kubernetes"
[WARNING] plugin/kubernetes: Kubernetes API connection failure: Get "https://[fd6d:706e:6702::1]:443/version": dial tcp [fd6d:706e:6702::1]:443: connect: connection refused
[INFO] plugin/ready: Still waiting on: "kubernetes"
[WARNING] plugin/kubernetes: Kubernetes API connection failure: Get "https://[fd6d:706e:6702::1]:443/version": dial tcp [fd6d:706e:6702::1]:443: connect: connection refused
[INFO] plugin/ready: Still waiting on: "kubernetes"
[INFO] plugin/ready: Still waiting on: "kubernetes"
[WARNING] plugin/kubernetes: Kubernetes API connection failure: Get "https://[fd6d:706e:6702::1]:443/version": dial tcp [fd6d:706e:6702::1]:443: connect: connection refused
[INFO] plugin/ready: Still waiting on: "kubernetes"
[WARNING] plugin/kubernetes: Kubernetes API connection failure: Get "https://[fd6d:706e:6702::1]:443/version": dial tcp [fd6d:706e:6702::1]:443: connect: connection refused
[INFO] plugin/ready: Still waiting on: "kubernetes"

Steps to reproduce the problem

Run hack/test_e2e.sh and do a first DNS call, observe pods trying to resolve the DNS and go into not ready state

knabben commented 1 year ago

Running on WSL2, it seems the CI is passing and do not have this issue. Will close it after confirmation

aroradaman commented 1 year ago

@knabben may be related to this https://github.com/kubernetes-sigs/kpng/blob/340d8d0d4f2b16076cef1927d749ef63486624ad/hack/test_e2e.sh#L289-L316

k8s-triage-robot commented 9 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 8 months ago

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:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 7 months ago

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:

You can:

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

/close not-planned

k8s-ci-robot commented 7 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/kpng/issues/508#issuecomment-2008201698): >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: >- 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ 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.