UiPath Documentation
automation-suite
2022.10
false
Automation Suite installation guide

Unable to launch Automation Hub and Apps with proxy setup

Description​

If you use a proxy setup, you may run into issues when trying to launch Automation Hub and Apps.

Solution​

You can fix the issue by taking the following steps:

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

    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.

    Once you have completed these steps, your file should resemble the following sample:

    apiVersion: v1
    data:
      Corefile: |
        .:53 {
            errors
            log
            health
            rewrite stop {
                name exact mycluster.autosuite.com 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
        }
    kind: ConfigMap
    metadata:
      name: coredns-custom
      namespace: kube-system
    apiVersion: v1
    data:
      Corefile: |
        .:53 {
            errors
            log
            health
            rewrite stop {
                name exact mycluster.autosuite.com 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
        }
    kind: ConfigMap
    metadata:
      name: coredns-custom
      namespace: kube-system
    
    1. Rename the configmap to coredns-custom.

    2. Add the following code block to your coredns-config.yaml file. Make sure the code block comes before the kubernetes cluster.local in-addr.arpa ip6.arp line.

      rewrite stop {
                  name exact <cluster-fqdn> istio-ingressgateway.istio-system.svc.cluster.local
              }
      rewrite stop {
                  name exact <cluster-fqdn> istio-ingressgateway.istio-system.svc.cluster.local
              }
      
    3. Replace <cluster-fqdn> with the actual value.

  3. Create the coredns-custom configmap:

    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:

    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:

    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.

  • Description​
  • Solution​

Was this page helpful?

Connect

Need help? Support(opens in new window)

Want to learn? UiPath Academy(opens in new window)

Have questions? UiPath Forum(opens in new window)

Stay updated