Open nickmitchko opened 6 months ago
Following up on this issue:
Found that the yaml for the kong-config isn't properly taking the deployment service name.
Here is the change that fixed it:
Originally posted by @nickmitchko in https://github.com/supabase-community/supabase-kubernetes/issues/60#issuecomment-2092977017
We'll need to change this link to reference the full name of the kong service:
https://github.com/supabase-community/supabase-kubernetes/blob/main/charts/supabase/templates/kong/config.yaml#L179-L180
Following up on this issue:
Found that the yaml for the kong-config isn't properly taking the deployment service name.
Here is the change that fixed it:
Originally posted by @nickmitchko in https://github.com/supabase-community/supabase-kubernetes/issues/60#issuecomment-2092977017
We'll need to change this link to reference the full name of the kong service:
https://github.com/supabase-community/supabase-kubernetes/blob/main/charts/supabase/templates/kong/config.yaml#L179-L180