Skip to content
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

keda-metrics-apiserver connection no such host #587

Open
duydo-ct opened this issue Jan 10, 2024 · 0 comments
Open

keda-metrics-apiserver connection no such host #587

duydo-ct opened this issue Jan 10, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@duydo-ct
Copy link

Expected Behavior

My config value.yaml file

image:
  keda:
    # -- Image name of KEDA operator
    repository: ghcr.io/kedacore/keda
    # -- Image tag of KEDA operator. Optional, given app version of Helm chart is used by default
    tag: "2.12.1"
  metricsApiServer:
    # -- Image name of KEDA Metrics API Server
    repository: ghcr.io/kedacore/keda-metrics-apiserver
    # -- Image tag of KEDA Metrics API Server. Optional, given app version of Helm chart is used by default
    tag: "2.12.1"
  webhooks:
    # -- Image name of KEDA admission-webhooks
    repository: ghcr.io/kedacore/keda-admission-webhooks
    # -- Image tag of KEDA admission-webhooks . Optional, given app version of Helm chart is used by default
    tag: "2.12.1"
  # -- Image pullPolicy for all KEDA components
  pullPolicy: Always

# -- Kubernetes cluster domain
clusterDomain: cluster.local

.....

Actual Behavior

W0110 08:27:16.921345       1 logging.go:59] [core] [Channel #1 SubChannel #3] grpc: addrConn.createTransport failed to connect to {Addr: "keda-operator.keda-system.svc.cluster.local:9666", ServerName: "keda-operator.keda-system.svc.cluster.local:9666", }. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup keda-operator.keda-system.svc.cluster.local on 169.254.169.254:53: no such host"
W0110 08:29:02.140973       1 logging.go:59] [core] [Channel #1 SubChannel #3] grpc: addrConn.createTransport failed to connect to {Addr: "keda-operator.keda-system.svc.cluster.local:9666", ServerName: "keda-operator.keda-system.svc.cluster.local:9666", }. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup keda-operator.keda-system.svc.cluster.local on 169.254.169.254:53: no such host"
W0110 08:30:49.930598       1 logging.go:59] [core] [Channel #1 SubChannel #3] grpc: addrConn.createTransport failed to connect to {Addr: "keda-operator.keda-system.svc.cluster.local:9666", ServerName: "keda-operator.keda-system.svc.cluster.local:9666", }. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup keda-operator.keda-system.svc.cluster.local on 169.254.169.254:53: no such host"
W0110 08:33:03.039554       1 logging.go:59] [core] [Channel #1 SubChannel #3] grpc: addrConn.createTransport failed to connect to {Addr: "keda-operator.keda-system.svc.cluster.local:9666", ServerName: "keda-operator.keda-system.svc.cluster.local:9666", }. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup keda-operator.keda-system.svc.cluster.local on 169.254.169.254:53: no such host"
W0110 08:35:09.734630       1 logging.go:59] [core] [Channel #1 SubChannel #3] grpc: addrConn.createTransport failed to connect to {Addr: "keda-operator.keda-system.svc.cluster.local:9666", ServerName: "keda-operator.keda-system.svc.cluster.local:9666", }. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup keda-operator.keda-system.svc.cluster.local on 169.254.169.254:53: no such host"

Steps to Reproduce the Problem

I deployed Keda via helm chart

Specifications

  • KEDA Version: v2.12.1
  • Kubernetes Version: 1.25
@duydo-ct duydo-ct added the bug Something isn't working label Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant