Issue with HTTPS Ingress on AKS - Unable to Access Service via HTTPS

148 Views Asked by At

I have an AKS cluster on Azure, and I've deployed my application from an ACR container registry. The assigned address for my application is in HTTP, and to resolve this, I've attempted to create an Ingress with TLS termination using a certificate from Azure Key Vault.

However, after successfully creating the Ingress, I'm still unable to access my application via HTTPS. The Ingress seems to be created, but the traffic is not being redirected correctly.

Ingress Configuration:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kubernetes.azure.com/tls-cert-keyvault-uri: https://mykeyvaultwebsite.vault.azure.net/certificates/poctodocertificat
  name: poctodoingress
  namespace: default-1705418607683
spec:
  ingressClassName: webapprouting.kubernetes.azure.com
  rules:
    - host: webclient.robotist.poc.com
      http:
        paths:
          - backend:
              service:
                name: todolist-frontend-service
                port:
                  number: 3000
            path: /
            pathType: Prefix
  tls:
    - hosts:
        - webclient.robotist.poc.com
      secretName: mysecretname

Additional Information:

  • The TLS certificate in the Azure Key Vault is verified and accessible.
  • The todolist-frontend-service is running and accessible within the cluster on port 3000.
  • The Ingress is in the correct namespace (default-1705418607683).

Observations:

When trying to access the application via HTTPS, it doesn't work, and there are no error messages. The Ingress status seems to indicate that it's created.

Versions: Azure Kubernetes Service (AKS): version 1.27.7

Any assistance in identifying and resolving the issue would be greatly appreciated.

Steps Taken:

  • Checked Ingress controller logs - no apparent issues.
  • Verified TLS certificate and Key Vault settings.
  • Confirmed the service is running.

Expected Outcomes:

  • Expecting the application to be accessible via HTTPS after setting up Ingress with TLS termination.
0

There are 0 best solutions below