mirror of
https://github.com/gethomepage/homepage.git
synced 2025-05-31 04:04:15 -04:00
Documentation: update Gateway API HttpRoute documentation (#5239)
Co-authored-by: shamoon <4887959+shamoon@users.noreply.github.com>
This commit is contained in:
parent
8b50296dad
commit
41dc2e77cb
@ -163,6 +163,18 @@ If the `href` attribute is not present, Homepage will ignore the specific Ingres
|
|||||||
|
|
||||||
Homepage also features automatic service discovery for Gateway API. Service definitions are read by annotating the HttpRoute custom resource definition and are indentical to the Ingress example as defined in [Automatic Service Discovery](#automatic-service-discovery).
|
Homepage also features automatic service discovery for Gateway API. Service definitions are read by annotating the HttpRoute custom resource definition and are indentical to the Ingress example as defined in [Automatic Service Discovery](#automatic-service-discovery).
|
||||||
|
|
||||||
|
To enable Gateway API HttpRoute update `kubernetes.yaml` to include:
|
||||||
|
|
||||||
|
```
|
||||||
|
gateway: true # enable gateway-api
|
||||||
|
```
|
||||||
|
|
||||||
|
#### Using the unoffocial helm chart?
|
||||||
|
|
||||||
|
If you are using the unofficial helm chart ensure that the `ClusterRole` has required permissions for `gateway.networking.k8s.io`.
|
||||||
|
|
||||||
|
See [ClusterRole and ClusterRoleBinding](../installation/k8s.md#clusterrole-and-clusterrolebinding)
|
||||||
|
|
||||||
## Caveats
|
## Caveats
|
||||||
|
|
||||||
Similarly to Docker service discovery, there currently is no rigid ordering to discovered services and discovered services will be displayed above those specified in the `services.yaml`.
|
Similarly to Docker service discovery, there currently is no rigid ordering to discovered services and discovered services will be displayed above those specified in the `services.yaml`.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user