You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
I am trying to connect an existing Ingress service on Google Cloud with my ArangoDB instance (using the operator). I do not choose LoadBalancer as an external service since this is going to create a new LoadBalancer (which I do not want), so I create a manual NodePort service which I assign to my Ingress controller yaml. However the Ingress cannot see the service.
...
Ok I found the issue here. The Google Cloud Ingress creates a Level 7 LoadBalancer for HTTP and HTTPS traffic. It demands a health check for all containers. The ArangoDB coordinator containers include a readiness probe, however the schema is set to HTTPS. However the default connection between an Ingress resource defaults to HTTP when communicating with a Service and the Ingress controller cannot access the readinessProbe. The solution is to default the Service with this annotation:
Theo in Community Slack (about k8s cluster):
I am trying to connect an existing Ingress service on Google Cloud with my ArangoDB instance (using the operator). I do not choose LoadBalancer as an external service since this is going to create a new LoadBalancer (which I do not want), so I create a manual NodePort service which I assign to my Ingress controller yaml. However the Ingress cannot see the service.
...
Ok I found the issue here. The Google Cloud Ingress creates a Level 7 LoadBalancer for HTTP and HTTPS traffic. It demands a health check for all containers. The ArangoDB coordinator containers include a readiness probe, however the schema is set to HTTPS. However the default connection between an Ingress resource defaults to HTTP when communicating with a Service and the Ingress controller cannot access the readinessProbe. The solution is to default the Service with this annotation:
This enables the Ingress to connect with the readiness probe.
The text was updated successfully, but these errors were encountered: