jensg-st opened a new issue, #1602:
URL: https://github.com/apache/apisix-ingress-controller/issues/1602
### Issue description
This is is more FYI than a bug but I think it is worthwhile reporting. We
are running k3s (v1.24.7+k3s1) on Ubuntu 22.04.01. We are getting DNS errors
and the ingress controller does not work. Weirdly it works on some notebooks
with Ubuntu, so we could not pinpoint the issue.
We have changed the Dockerfile to run it on Debian and Ubuntu and this
problem goes away and the ingress controller works as expected. My main
question is if there is something I should be aware of changing the base of the
Dockerfile? Is there a specific reason to use centos? Have you experienced this
behaviour as well?
Other than that you can close the issue because we are building our own
image on Ubuntu now because centos is not longer supported/maintained and we
need UTC as timezone. This is just FYI.
### Environment
- version:
```
Version: 1.6.0
Git SHA: no-git-module
Go Version: go1.19.4
Building OS/Arch: linux/amd64
Running OS/Arch: linux/amd64
```
- kubernetes:
```
Server Version: version.Info{Major:"1", Minor:"24",
GitVersion:"v1.24.7+k3s1",
GitCommit:"7af5b16788afe9ce1718d7b75b35eafac7454705", GitTreeState:"clean",
BuildDate:"2022-10-25T19:31:34Z", GoVersion:"go1.18.7", Compiler:"gc",
Platform:"linux/amd64"}
```
- uname: 5.15.0-58-generic 64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64
x86_64 x86_64 GNU/Linux
```
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"
```
```ldd (Ubuntu GLIBC 2.35-0ubuntu3.1) 2.35```
### Minimal test code / Steps to reproduce
Basic k3s installation on Ubuntu
### Actual result
Internal services are not getting resolved
### Error log
```
2023-01-17T01:26:46+08:00 warn providers/controller.go:175 found a
new leader apisix-ingress-controller-b675bd778-chwb2
2023-01-17T01:26:46+08:00 info providers/controller.go:359
controller tries to leading ... {"namespace": "apisix", "pod":
"apisix-ingress-controller-b675bd778-chwb2"}
2023-01-17T01:26:46+08:00 warn apisix/cluster.go:344 waiting cluster
default to ready, it may takes a while
2023-01-17T01:26:46+08:00 info apisix/cluster.go:172 syncing cache
{"cluster": "default"}
2023-01-17T01:26:46+08:00 info apisix/cluster.go:384 syncing schema
{"cluster": "default"}
2023-01-17T01:26:46+08:00 error apisix/plugin.go:46 failed to list
plugins' names: Get
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins?all=true":
dial tcp: lookup apisix-admin.apisix.svc.cluster.local: no such host
2023-01-17T01:26:46+08:00 error apisix/cluster.go:404 failed to list
plugin names in APISIX: Get
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins?all=true":
dial tcp: lookup apisix-admin.apisix.svc.cluster.local: no such host
2023-01-17T01:26:46+08:00 error apisix/cluster.go:367 failed to sync
schema: Get
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins?all=true":
dial tcp: lookup apisix-admin.apisix.svc.cluster.local: no such host
2023-01-17T01:26:46+08:00 error apisix/route.go:118 failed to list
routes: Get
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes": dial
tcp: lookup apisix-admin.apisix.svc.cluster.local: no such host
2023-01-17T01:26:46+08:00 error apisix/cluster.go:222 failed to list
routes in APISIX: Get
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes": dial
tcp: lookup apisix-admin.apisix.svc.cluster.local: no such host
2023-01-17T01:26:48+08:00 error apisix/route.go:118 failed to list
routes: Get
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes": dial
tcp: lookup apisix-admin.apisix.svc.cluster.local: no such host
2023-01-17T01:26:48+08:00 error apisix/cluster.go:222 failed to list
routes in APISIX: Get
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes": dial
tcp: lookup apisix-admin.apisix.svc.cluster.local: no such host
2023-01-17T01:26:50+08:00 error apisix/route.go:118 failed to list
routes: Get
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes": dial
tcp: lookup apisix-admin.apisix.svc.cluster.local: no such host
2023-01-17T01:26:50+08:00 error apisix/cluster.go:222 failed to list
routes in APISIX: Get
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes": dial
tcp: lookup apisix-admin.apisix.svc.cluster.local: no such host
2023-01-17T01:26:52+08:00 error apisix/route.go:118 failed to list
routes: Get
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes": dial
tcp: lookup apisix-admin.apisix.svc.cluster.local: no such host
2023-01-17T01:26:52+08:00 error apisix/cluster.go:222 failed to list
routes in APISIX: Get
"http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes": dial
tcp: lookup apisix-admin.apisix.svc.cluster.local: no such host```
### Expected result
_No response_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
