How to specify an additional DNS Alias beside hostname

[jheinitz]

How to specify an additional DNS Alias beside hostname

[kurokobo]

@jheinitz
Hi,

I've never tried that, but the customization of Ingress resource by using AWX Operator is highly limited since AWX Operator just templates manifest based on this file: ingress.yaml.j2.

So, if your requirements can be achieved by manually created Ingress, I recommend you to:

• Do not create Ingress using AWX Operator. Remove ingress_* and hostname.
• Create Ingress resource manually.

Maybe I don't fully understand your requirements, but hou about create the following resource, for example?

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: awx-custom-ingress
  namespace: awx
spec:
  rules:
    - host: ansible.example.com
      http:
        paths:
          - backend:
              service:
                name: awx-service
                port:
                  number: 80
            path: /
            pathType: Prefix
    - host: ansible01.example.com
      http:
        paths:
          - backend:
              service:
                name: awx-service
                port:
                  number: 80
            path: /
            pathType: Prefix
    - host: ansible02.example.com
      http:
        paths:
          - backend:
              service:
                name: awx-service
                port:
                  number: 80
            path: /
            pathType: Prefix
  tls:
    - hosts:
        - ansible.example.com
        - ansible01.example.com
        - ansible02.example.com
      secretName: awx-secret-tls

[jheinitz]

Hello @kurokobo !

That's exactly what I want and it works fine. To be more precise. We are running two servers in parallel and by changing the DNS Alias ansible.example.com between ansible1.example.com and ansible2.example.com we can switch between these two instances. We use this to test a new version before taking that into production. So, basically I would create two custom ingress on both servers that include their own hostname itself and the alias ansible.example.com.

By the way, it all works even with the standard awx-ingress in place. Still searching for the command to remove the awx-ingress resource .... :-)

Thanks for your help. I'm going to close the issue.

Best regards

Jens

[jheinitz]

Hi @kurokobo ,

another short question. You mentioned that I should not create ingress through awx-operator by removing ingress... and hostname. Remove the matching lines from base/kustomization.yaml?

Thanks Jens

[kurokobo]

@jheinitz
Ah sorry for less infomation.

You mentioned that I should not create ingress through awx-operator by removing ingress... and hostname. Remove the matching lines from base/kustomization.yaml?

This is the steps to swap Ingress by AWX Operator for manually created one:

1. Deploy custom Ingress by using YAML file in my comment above.
2. Remove the three lines for ingress_type, ingress_tls_secret, hostname from your base/awx.yaml
3. Apply new configuration by kubectl apply -k base. This makes AWX Operator no longer keep awx-ingress deployed. It's ok that your awx-ingress still exists on your namespace at this step.
4. Remove old Ingress manually by kubectl -n awx delete ingress awx-ingress