Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GKE Ingress Health Check Fails Due to Default Path #19

Open
zacchenit opened this issue Dec 5, 2024 · 0 comments
Open

GKE Ingress Health Check Fails Due to Default Path #19

zacchenit opened this issue Dec 5, 2024 · 0 comments

Comments

@zacchenit
Copy link

If I want to deploy OpenLit on GKE and expose it externally via Ingress, I encounter an issue. The default health check path for the GCP Load Balancer is /, and OpenLit redirects from / with a 307 status to another page, causing the health check to fail.

However, I can resolve this issue by setting up a GCP BackendConfig. Therefore, I would like to have the ability to add custom annotations in the values.yaml service configuration.

For example:

# Kubernetes Service configuration for OpenLIT
service:
  # Custom annotations
  annotations:
    cloud.google.com/backend-config: '{"ports": {"80":"openlit-backendconfig"}}'
  # Type of service (e.g., LoadBalancer, NodePort)
  type: ClusterIP
  # Port on which the service is exposed
  port: 3000
  # Session affinity configuration
  sessionAffinity: None

Do you have any better suggestions? Or if assistance is needed, I can try to take it up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant