ArgoCD, Traefik and Progressing State Part 2

Continuing with the last post of fixing ArgoCD and Ingress, now
i am going to explain how to do it, the right way.

In the last post, we applied a patch that what it does, is just force a “healthy” state
but now, we are going to tell ArgoCD to get the status of the ingress controller.
And because, our ingresscontroller is the only LoadBalancer, it will return healty
and also the ipaddress provided in the LoadBalancer.

Ready?

Change publishedService to true

1
2
3
4
5
6
7
8
9
10
11
12
13
14
providers:
  kubernetesCRD:
    enabled: true
    allowCrossNamespace: false
    allowExternalNameServices: false
    allowEmptyServices: false
    namespaces: []
  kubernetesIngress:
    enabled: true
    allowExternalNameServices: false
    allowEmptyServices: false
    namespaces: []
    publishedService:
      enabled: true

Now, if you ask for your ingress controller, you will get the ip address of the LoadBalancer
instead nothing

1
2
3
4
5
6
7
> k get ingress -A
NAMESPACE    NAME                                                      CLASS     HOSTS                                         ADDRESS         PORTS   AGE
devops       grafana                                                   traefik   grafana.k8s.level5.local                      192.168.88.50   80      42d
devops       kube-ops-view                                             traefik   kubeops.k8s.level5.local                      192.168.88.50   80      35d
monitoring   prometheus-server                                         <none>    prometheus.k8s.level5.local                   192.168.88.50   80      34d
runners      runners-actions-runner-controller-github-webhook-server   traefik   runners.k8s.level5.local,runners.level5.dev   192.168.88.50   80      97d
website      static-website                                            traefik   run.level5.dev                                192.168.88.50   80      87d

Yuhu!

Next time you deploy something, you will get the healthy status because traefik is now reporting the ADDRESS

Comments

⬆︎TOP