Set up languagedepot namespace in task setup #803
Merged
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.
This will avoid Skaffold deleting the languagedepot namespace when you run
skaffold delete
, so it doesn't have to be re-created each time.The change to the ingress-deployment.yaml file is necessary because Kustomize was changing the
ingress-nginx
namespaces in there tolanguagedepot
anyway, and therefore Skaffold was still deleting the languagedepot namespace when runningskaffold delete
because it was being created by ingress-deployment.yaml. Now that ingress-deployment.yaml uses the languagedepot namespace instead, and assumes it already exists, runningskaffold delete; task up
goes a lot faster.Fixes #605.