fix: use zarf vendored kubectl during supabase deployment (#517)

defenseunicorns · May 15, 2024 · c236d39 · c236d39
1 parent 47249c4
commit c236d39
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/packages/supabase/zarf.yaml b/packages/supabase/zarf.yaml
@@ -118,12 +118,12 @@ components:
       onDeploy:
         before:
           # Deletes the initial kong config created by the upstream chart
-          - cmd: kubectl delete cm supabase-kong-declarative-config -n leapfrogai
+          - cmd: ./zarf tools kubectl delete cm supabase-kong-declarative-config -n leapfrogai
         after:
           # Restarts supabase-kong after the new kong config has been applied
           # so that it can be loaded into the kong container
-          - cmd: kubectl rollout restart deployment supabase-kong -n leapfrogai
-          - cmd: kubectl rollout status deployment supabase-kong -n leapfrogai
+          - cmd: ./zarf tools kubectl rollout restart deployment supabase-kong -n leapfrogai
+          - cmd: ./zarf tools kubectl rollout status deployment supabase-kong -n leapfrogai
     manifests:
       # Applies an update kong config that includes basic auth, this gets applied
       # after the kong pods have started so the original config needs to be deleted and pod restarted