I have problem with the address of the kibana

Hi,
I have a question about ingress:
this is my kibana:

apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: quickstart
spec:
  version: 7.6.2
  count: 1
  elasticsearchRef:
    name: cdbridgerpayelasticsearch
  http:
    service:
        spec:
            type: LoadBalancer

and this is my ingress:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: tls-bcd-ingress-bcdmmm
spec:
  ingressClassName: bcdbcdbcdingressclassbcdbcdbcd
  tls:
  - hosts:
      -  kibana.some.com
    secretName: bcdsecret
  rules:
  - host: kibana.some.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: quickstartcd-kb-http
            port:
              number: 5601

and this in my ingressclass:

apiVersion: networking.k8s.io/v1
kind: IngressClass
metadata:
  labels:
    app.kubernetes.io/component: controller
  name: bcdbcdbcdingressclassbcdbcdbcd
  annotations:
    ingressclass.kubernetes.io/is-default-class: "true"
spec:
  controller: k8s.io/ingress-nginx

when I ran kubectl get ingress I got:

$ kubectl get ingress
W0616 09:31:56.287938 697 gcp.go:120] WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.25+; use gcloud instead.
To learn more, consult Kubectl auth changes in GKE v1.25 : gke-gcloud-auth-plugin | Google Cloud Blog
NAME CLASS HOSTS ADDRESS PORTS AGE
...
tls-bcd-ingress-bcdmmm bcdbcdbcdingressclassbcdbcdbcd kibana.some.com 80, 443 6m39s
...
but I whas without ADDRESS,

p.s. when I ran:
kubectl describe ingress tls-bcd-ingress

I got:

kubectl describe ingress tls-bcd-ingress
W0616 09:32:44.479898 747 gcp.go:120] WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.25+; use gcloud instead.
To learn more, consult Kubectl auth changes in GKE v1.25 : gke-gcloud-auth-plugin | Google Cloud Blog
Name: tls-bcd-ingress
Labels:
Namespace: default
Address: 34.95.125.45
Ingress Class:
Default backend:
TLS:
bcd-kibana-testsecret-tls terminates kibana.some.com
Rules:
Host Path Backends


kibana.some.com
/ quickstart-kb-http:5601 (10.0.0.6:5601)
Annotations: ingress.kubernetes.io/backends:
{"k8s-be-30836--5648580d9ac523a4":"HEALTHY","k8s1-5648580d-default-quickstart-kb-http-5601-b20f4828":"UNHEALTHY"}
ingress.kubernetes.io/forwarding-rule: k8s2-fr-ogj1ibfs-default-tls-bcd-ingress-zhwu0ht3
ingress.kubernetes.io/https-forwarding-rule: k8s2-fs-ogj1ibfs-default-tls-bcd-ingress-zhwu0ht3
ingress.kubernetes.io/https-target-proxy: k8s2-ts-ogj1ibfs-default-tls-bcd-ingress-zhwu0ht3
ingress.kubernetes.io/ssl-cert: k8s2-cr-ogj1ibfs-4oof5muqat1ono4r-f0cc35b846b8a8c3
ingress.kubernetes.io/static-ip: k8s2-fr-ogj1ibfs-default-tls-bcd-ingress-zhwu0ht3
ingress.kubernetes.io/target-proxy: k8s2-tp-ogj1ibfs-default-tls-bcd-ingress-zhwu0ht3
ingress.kubernetes.io/url-map: k8s2-um-ogj1ibfs-default-tls-bcd-ingress-zhwu0ht3
Events:
Type Reason Age From Message


Normal Sync 6m26s (x154 over 24h) loadbalancer-controller Scheduled for sync

If you know why its without address-
itll help me.
thanks

@tiagocosta / @jbudz any inputs? Thanks

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.