Could not resolve the hostname of the ingress, falling back to the static IP

[rchojn]

Is there an existing issue for this?

• [X] I have searched the existing issues

What happened?

During configuration of cluster-mesh following errors with ingress appeared:

Hostname based ingress detected, trying to resolve it
Could not resolve the hostname of the ingress, falling back to the static IP. Error: lookup internal-a6bf6966baa884706b333c86ed381546-1120202735.eu-central-1.elb.amazonaws.com on 192.168.0.1:53: no such host
✅ Cluster access information is available:
  - :2379
✅ Service "clustermesh-apiserver" of type "LoadBalancer" found
⌛ [arn:aws:eks:eu-central-1:729148576793:cluster/cluster-a] Waiting for deployment clustermesh-apiserver to become ready...
🔌 Cluster Connections:
🔀 Global services: [ min:0 / avg:0.0 / max:0 ]
Hostname based ingress detected, trying to resolve it
Could not resolve the hostname of the ingress, falling back to the static IP. Error: lookup internal-a98d614cfbaae4b68a9ff14be5dee82e-107606502.eu-central-1.elb.amazonaws.com on 192.168.0.1:53: no such host
✅ Cluster access information is available:
  - :2379
✅ Service "clustermesh-apiserver" of type "LoadBalancer" found
⌛ [arn:aws:eks:eu-central-1:729148576793:cluster/cluster-b] Waiting for deployment clustermesh-apiserver to become ready...
🔌 Cluster Connections:
🔀 Global services: [ min:0 / avg:0.0 / max:0 ]

Cilium Version

cilium-cli: v0.12.2 compiled with go1.19 on linux/amd64
cilium image (default): v1.12.1
cilium image (stable): v1.12.1
cilium image (running): unknown. Unable to obtain cilium version, no cilium pods found in namespace "kube-system"

Kernel Version

Linux rwauwprlc0089 5.4.0-124-generic cilium/cilium#140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Kubernetes Version

WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.2", GitCommit:"f66044f4361b9f1f96f0053dd46cb7dce5e990a8", GitTreeState:"clean", BuildDate:"2022-06-15T14:22:29Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4

Sysdump

No response

Relevant log output

No response

Anything else?

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[sayboras]

The loadbalancer name (e.g. internal-a98d614cfbaae4b68a9ff14be5dee82e-107606502.eu-central-1.elb.amazonaws.com) seems to be internal, and might be only resolved within private subnets only.

Just want to confirm if you are running cilium CLI in the same VPC.

[rchojn]

Yes, it's the same VPC. By default amazon is launching the cluster in private and public vpc (3 availability zones). In privateNetworking: true setup the error is the same