Aws-load-balancer-controller: different healthcheck PATH for different target group

Created on 30 Oct 2019 · 9Comments · Source: kubernetes-sigs/aws-load-balancer-controller

I am running multiple pods , node app, java app on k8s and using ALB ingress controller with different paths, but I have different healthcheck urls like /health for TG1, /actuator for TG2, /status for TG3.

I have tried using this annotation alb.ingress.kubernetes.io/healthcheck-path: /ping but this add /ping to all the TGs, how can i pass different healthcheck-path for different target group, pls advice

lifecyclrotten

Source

saravana-code

👍5

Most helpful comment

Absolutely, instead of set the annotation into kind Ingress

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    ...
    alb.ingress.kubernetes.io/healthcheck-path: /ping
    ...

You can set health check into the kind Service, in the same way

apiVersion: v1
kind: Service
metadata:
  annotations:
    ...
    alb.ingress.kubernetes.io/healthcheck-path: /ping
    ...

Eraac on 8 Nov 2019

👍10 ❤2

All 9 comments

You should set the annotation at the Service Object level, not Ingress Object

Eraac on 4 Nov 2019

@Eraac thanks for the response, can you give me more info/example please? you mean the service.yml needs to be defined with healthchecks instead of ingress ?

saravana-code on 8 Nov 2019

Absolutely, instead of set the annotation into kind Ingress

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    ...
    alb.ingress.kubernetes.io/healthcheck-path: /ping
    ...

You can set health check into the kind Service, in the same way

apiVersion: v1
kind: Service
metadata:
  annotations:
    ...
    alb.ingress.kubernetes.io/healthcheck-path: /ping
    ...

Eraac on 8 Nov 2019

👍10 ❤2

Thanks @Eraac problem resolved for me on other issue. https://github.com/kubernetes-sigs/aws-alb-ingress-controller/issues/1073

teochenglim on 20 Nov 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 18 Feb 2020

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 19 Mar 2020

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 18 Apr 2020

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.