Skip to content

Commit

Permalink
Documentation: additional explainer for the pod-selector (#4316)
Browse files Browse the repository at this point in the history
  • Loading branch information
mrsimonemms authored Nov 22, 2024
1 parent 2b8647b commit 5697253
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions docs/configs/kubernetes.md
Original file line number Diff line number Diff line change
Expand Up @@ -100,6 +100,8 @@ If you are using multiple instances of homepage, an `instance` annotation can be

If you have a single service that needs to be shown on multiple specific instances of homepage (but not on all of them), the service can be annotated by multiple `instance.name` annotations, where `name` can be the names of your specific multiple homepage instances. For example, a service that is annotated with `gethomepage.dev/instance.public: ""` and `gethomepage.dev/instance.internal: ""` will be shown on `public` and `internal` homepage instances.

Use the `gethomepage.dev/pod-selector` selector to specify the pod used for the health check. For example, a service that is annotated with `gethomepage.dev/pod-selector: app.kubernetes.io/name=deployment` would link to a pod with the label `app.kubernetes.io/name: deployment`.

### Traefik IngressRoute support

Homepage can also read ingresses defined using the Traefik IngressRoute custom resource definition. Due to the complex nature of Traefik routing rules, it is required for the `gethomepage.dev/href` annotation to be set:
Expand Down

0 comments on commit 5697253

Please sign in to comment.