Does version 1.5.0 and greater support TLS certificates?

[SpartanDoll]

Hello there,

I am currently updating our Azure Gateway Ingress Controller version and switching the from api version from extensions/v1beta1 to networking.k8s.io/v1 in the ingress.yaml. We are doing this due to the Kubernetes update of 1.22.*.

Does the Ingress Controller version 1.5.0 and 1.5.1 support hostname and TLS? The reason why I ask is that the listener never got updated in our Gateway with the hostname.

ingress.yaml

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: gateway-ingress
annotations:
kubernetes.io/ingress.class: azure/application-gateway
appgw.ingress.kubernetes.io/request-timeout: "60"
spec:
tls:
- hosts:
- USER_DEFINED_DOMAIN
secretName: ingress-tls.tls
rules:

• host: USER_DEFINED_DOMAIN
• http:
  paths:
  • path: /*
    pathType: Prefix
    backend:
    service:
    name: test-portal
    port:
    number: 80

When I use version 1.5.0-rc and set the ingress.yaml to use extension/v1beta1 everything works as expected. However, when I change the ingress.yaml to use networking.k8s.io/v1 format in version 1.5.0-rc, 1.5.0 and 1.5.1 it does not work.

Should I use 1.5.0-rc and set ingress.yaml to use extension/v1beta1? I have it working with the Kubernetes update.

Kubernetes Version: 1.22.9
AAD-Pod-Identity - 1.8.0

Thank you for your help.

[SpartanDoll]

Correction Kubernetes Version: 1.22.4

When I create a new cluster none of the 1.5.0+ versions work as expected.