Conversation
For sidecar injection to happen Istio needs to be running before our app is. To make this happen, this commit splits the config into a seed config that creates namespaces, secrets and installs Istio, and then an normal overlay that installs the app. Also included here is an overlay called test, that is very close to prod, but uses a self signed cert. The process to bring up a cluster (using test as an example) is now the following: ```sh kustomize build overlays/seed/test | kubectl apply -f - watch kubectl get po -A kustomize build overlays/test | kubectl apply -f - watch kubectl get po -A kubectl get svc -n istio-system istio-ingressgateway -o json | jq '.status.loadBalancer.ingress' ```
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
For sidecar injection to happen Istio needs to be running before our app is. To make this happen, this commit splits the config into a seed config that creates namespaces, secrets and installs Istio, and then an normal overlay that installs the app.
Also included here is an overlay called test, that is very close to prod, but uses a self signed cert.
The process to bring up a cluster (using test as an example) is now the following: