fix: use zarf vendored kubectl during supabase deployment #517
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The supabase deployment uses a short 'hack' to get the configmap for kong set. The 'hack' involves using kubectl to cycle a deployment.
Some of the host machiens running this package might not have
kubectl
installed on their $PATH. Instead of trying to use the $PATH kubectl, we should use the version that zarf vendors with itself.