How do I provision Ingress vs Gateway API in Azure with Ansible?

Provisioning Ingress and Gateway API in Azure using Ansible can be a seamless process with the right playbooks. Both Ingress and Gateway API serve different purposes in managing traffic for your applications hosted on Kubernetes. Ingress is typically used for managing external access to services, while the Gateway API provides more advanced traffic management capabilities.

# Example Ansible playbook to provision Ingress

- name: Provision Azure Kubernetes Ingress
  hosts: localhost
  tasks:
    - name: Create Kubernetes Ingress Resource
      azure_rm_kubernetes_ingress:
        resource_group: myResourceGroup
        name: my-ingress
        namespace: default
        annotations:
          kubernetes.io/ingress.class: nginx
        rules:
          - host: myapp.example.com
            http:
              paths:
                - path: /
                  pathType: Prefix
                  backend:
                    service:
                      name: my-service
                      port:
                        number: 80

# Example Ansible playbook to provision Gateway API

- name: Provision Azure Kubernetes Gateway API
  hosts: localhost
  tasks:
    - name: Create Gateway API Resource
      azure_rm_kubernetes_gateway:
        resource_group: myResourceGroup
        name: my-gateway
        namespace: default
        gatewayClassName: my-gateway-class
        requisition:
          - host: myapi.example.com
            backend:
              services:
                - name: my-service
                  port:
                    number: 80