search

Azure / application-gateway-kubernetes-ingress

This is an ingress controller that can be run on Azure Kubernetes Service (AKS) to allow an Azure Application Gateway to act as the ingress for an AKS cluster.
https://azure.github.io/application-gateway-kubernetes-ingress
MIT License
678 stars 422 forks source link

Ingress hostname not reachable when deployed using AGIC #1290

Closed Srkvmv closed 3 years ago

Srkvmv commented 3 years ago

Describe the bug I am trying to expose my keycloak service using AGIC. I am using bitnami chart(https://github.com/bitnami/charts/tree/master/bitnami/keycloak/#installing-the-chart) for keycloak installation. I am able to access the service via the IP address when the host name is not configured, however both the hostname and the IP are not accessible when the host name is configured.

To Reproduce I am feeding the below values to the bitnami chart.

auth: adminPassword: User@123 adminUser: user managementPassword: managementUser: manager externalDatabase: database: postgres host: keycloak-ingress.postgres.database.azure.com password: user: keycloak@keycloak-ingress postgresql: enabled: false service: type: ClusterIP ingress: enabled: true hostname: "keycloak.local" annotations: kubernetes.io/ingress.class: azure/application-gateway appgw.ingress.kubernetes.io/use-private-ip: "true"

Ingress Controller details

Output of kubectl describe ingress -n keycloak Name: my-keycloak Namespace: keycloak Address: 40.127.184.84 Default backend: default-http-backend:80 (<error: endpoints "default-http-backend" not found>) Rules: Host Path Backends

keycloak.local / my-keycloak:http (10.3.5.43:8080)

Annotations: kubernetes.io/ingress.class: azure/application-gateway meta.helm.sh/release-name: my-keycloak meta.helm.sh/release-namespace: keycloak Events: Type Reason Age From Message

Warning PortResolutionError 5m13s azure/application-gateway Code="ErrorServiceResolvedToInvalidPort" Message="service keycloak/my-keycloak and service port http was resolved to an invalid service-backend port 65536, defaulting to port 80"

Srkvmv commented 3 years ago

resolved

VincentVerweij commented 2 years ago

Hi @Srkvmv

It is good to see that you did resolve the issue. Any chance of sharing what you did to resolve this issue? Currently I am getting the same error message as the warning you posted at the bottom of your issue (ErrorServiceResolvedToInvalidPort). Google pointed me to this issue 😄 So if you have any information on how this can be resolved, would be great!

Thanks in advance!

HujinoKun commented 1 week ago

Same error @Srkvmv