Automation Suite on EKS/AKS installation guide

Description​

Solution​

1. Capture the existing coredns configmap from the running cluster:

   assignment

   kubectl get configmap -n kube-system coredns -o yaml > coredns-config.yaml
   kubectl get configmap -n kube-system coredns -o yaml > coredns-config.yaml
   

2. Edit the coredns-config.yaml file to append the FQDN rewrite to the config.

   1. Rename the configmap to coredns-custom.
   2. Apply the correct configuration depending on your platform:
      • For AKS, define a new CoreDNS zone for the FQDN, as shown in the following example:
        assignment

        apiVersion: v1
        kind: ConfigMap
        metadata:
          name: coredns-custom
          namespace: kube-system
        data:
          <FQDN>.server: |
            <FQDN>:53 {
                errors
                log
                health
                rewrite stop {
                    name exact <FQDN> istio-ingressgateway.istio-system.svc.cluster.local
                }
                kubernetes cluster.local in-addr.arpa ip6.arpa {
                  pods insecure
                  fallthrough in-addr.arpa ip6.arpa
                }
                prometheus :9153
                forward . /etc/resolv.conf
                cache 30
                loop
                reload
                loadbalance
            }
        apiVersion: v1
        kind: ConfigMap
        metadata:
          name: coredns-custom
          namespace: kube-system
        data:
          <FQDN>.server: |
            <FQDN>:53 {
                errors
                log
                health
                rewrite stop {
                    name exact <FQDN> istio-ingressgateway.istio-system.svc.cluster.local
                }
                kubernetes cluster.local in-addr.arpa ip6.arpa {
                  pods insecure
                  fallthrough in-addr.arpa ip6.arpa
                }
                prometheus :9153
                forward . /etc/resolv.conf
                cache 30
                loop
                reload
                loadbalance
            }
        

      • For EKS, it is enough to add only the rewrite block to the existing CoreDNS Corefile:
        assignment

        rewrite stop {
            name exact <FQDN> istio-ingressgateway.istio-system.svc.cluster.local
        }
        rewrite stop {
            name exact <FQDN> istio-ingressgateway.istio-system.svc.cluster.local
        }
        

3. Create the coredns-custom configmap:

   assignment

   kubectl apply -f coredns-config.yaml
   kubectl apply -f coredns-config.yaml
   

4. Replace the volume reference from coredns to coredns-custom in the coredns deployment in kube-system namespace:

   assignment

   volumes:
     - emptyDir: {}
       name: tmp
     - configMap:
         defaultMode: 420
         items:
         - key: Corefile
           path: Corefile
         name: coredns-custom
       name: config-volume
   volumes:
     - emptyDir: {}
       name: tmp
     - configMap:
         defaultMode: 420
         items:
         - key: Corefile
           path: Corefile
         name: coredns-custom
       name: config-volume
   

5. Restart the coredns deployment and ensure the coredns pods are up and running without any issues:

   assignment

   kubectl rollout restart deployment -n kube-system coredns
   kubectl rollout restart deployment -n kube-system coredns
   

6. You should now be able to launch Automation Hub and Apps.