Skip to main content
Question

ifs cloud HA setup 25.1.5

  • December 31, 2025
  • 0 replies
  • 2 views

Forum|alt.badge.img+1

Hi All,

having issues getting a cluster setup for HA.  i managed to get microk8s deployed on all 3 nodes and then joined into a cluster. The issue comes on installing ifs-ingress, 2 of the nodes can’t seem to start the proxy-injector and destination pods

 

PS E:\svt\ifsroot> kubectl get pods -n ifs-ingress
NAME                                     READY   STATUS             RESTARTS          AGE
ingress-ingress-nginx-controller-24rfd   1/1     Running            0                 141m
ingress-ingress-nginx-controller-q97k9   1/1     Running            0                 141m
ingress-ingress-nginx-controller-rt42d   1/1     Running            0                 141m
linkerd-destination-8799fff4b-55kpb      4/4     Running            0                 141m
linkerd-destination-8799fff4b-5rkqb      0/4     CrashLoopBackOff   139 (2m39s ago)   141m
linkerd-destination-8799fff4b-hrxfv      0/4     CrashLoopBackOff   138 (2m19s ago)   141m
linkerd-identity-5fc98769b4-cx88m        2/2     Running            0                 141m
linkerd-identity-5fc98769b4-hj42m        2/2     Running            0                 141m
linkerd-identity-5fc98769b4-rpblm        2/2     Running            0                 141m
linkerd-proxy-injector-8c9688db5-9tdmt   2/2     Running            0                 141m
linkerd-proxy-injector-8c9688db5-dm8r9   0/2     CrashLoopBackOff   60 (2m29s ago)    141m
linkerd-proxy-injector-8c9688db5-wxvrk   0/2     CrashLoopBackOff   60 (2m59s ago)    141m

 

      Message:       t: Failed to connect error=endpoint 127.0.0.1:8090: Connection refused (os error 111) error.sources=[Connection refused (os error 111)]
[   149.103556s]  WARN ThreadId(01) dst:controller{addr=localhost:8086}:endpoint{addr=127.0.0.1:8086}: linkerd_reconnect: Failed to connect error=endpoint 127.0.0.1:8086: Connection refused (os error 111) error.sources=[Co
nnection refused (os error 111)]
[   149.136920s]  WARN ThreadId(01) policy:controller{addr=localhost:8090}:endpoint{addr=127.0.0.1:8090}: linkerd_reconnect: Failed to connect error=endpoint 127.0.0.1:8090: Connection refused (os error 111) error.sources=
[Connection refused (os error 111)]
[   149.604620s]  WARN ThreadId(01) dst:controller{addr=localhost:8086}:endpoint{addr=127.0.0.1:8086}: linkerd_reconnect: Failed to connect error=endpoint 127.0.0.1:8086: Connection refused (os error 111) error.sources=[Co
nnection refused (os error 111)]
[   149.637908s]  WARN ThreadId(01) policy:controller{addr=localhost:8090}:endpoint{addr=127.0.0.1:8090}: linkerd_reconnect: Failed to connect error=endpoint 127.0.0.1:8090: Connection refused (os error 111) error.sources=
[Connection refused (os error 111)]
[   150.014372s]  WARN ThreadId(01) linkerd_app: Waiting for identity to be initialized...
[   150.014552s]  INFO ThreadId(02) identity:identity{server.addr=linkerd-identity-headless.ifs-ingress.svc.cluster.local:8080}:controller{addr=linkerd-identity-headless.ifs-ingress.svc.cluster.local:8080}: linkerd_proxy_b
alance_queue::worker: Unavailable; entering failfast timeout=30.0
[   150.014594s] ERROR ThreadId(02) identity:identity{server.addr=linkerd-identity-headless.ifs-ingress.svc.cluster.local:8080}: linkerd_proxy_identity_client::certify: Failed to obtain identity error=status: Unknown, mess
age: "controller linkerd-identity-headless.ifs-ingress.svc.cluster.local:8080: service in fail-fast", details: [], metadata: MetadataMap { headers: {} } error.sources=[controller linkerd-identity-headless.ifs-ingress.svc.c
luster.local:8080: service in fail-fast, service in fail-fast]

Anyone faced the same.  Any pointers as to what I should check?

Thanks