From d6068f42a5d67aaf5a4d3dc34b674e3427be0d2f Mon Sep 17 00:00:00 2001 From: Wilson Mitchell Date: Fri, 24 Nov 2023 18:42:42 -0800 Subject: [PATCH] Use annotations directly instead of forking posthog chart unnecessarily. --- apps/prod/posthog/merge-values.yaml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/apps/prod/posthog/merge-values.yaml b/apps/prod/posthog/merge-values.yaml index b37363ce0..5c027292f 100644 --- a/apps/prod/posthog/merge-values.yaml +++ b/apps/prod/posthog/merge-values.yaml @@ -174,5 +174,8 @@ spec: effect: "NoSchedule" ingress: # -- Ingress handler type. Defaults to `nginx` if nginx is enabled and to `clb` on gcp. + # We're using our own so this doesn't actually do anything but we then put the ingress class annotation on the ingress which makes it get picked up by our posthog-specific nginx controller type: "posthog-nginx" + annotations: + kubernetes.io/ingress.class: "posthog-nginx" hostname: "posthog.prod.cluster.compose.ai"