-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Various improvement and fixes found in 1st test deployment #8
Conversation
beb9b45
to
1e04196
Compare
One more thing I was not sure about - the bootstrap installs the |
This optional environment provides all the necessary tools with just a single command.
otherwise helm misbehaves
…space With the bootstrap/cert-manager/kustomization.yaml we have overriden the namespace of all the resources to be `kube-system`, but the cert-manager still has the annotation `cert-manager.io/inject-ca-from-secret` that refers to the default `cert-manager` namespace. As a result, it is not possible for the cainjector to inject the secret. This patch updates the annotation to use `kube-system` instead.
Prior to this commit, the find command did not work because the '-depth' parameter: - cannot be placed before the name - is a boolean flag that does not accept arguments. I believe the intention was to use `-maxdepth 1` here.
Nope. That file isn't even included in kustomize so we need to just delete it. The ingress actually comes from within the base directory. |
This PR addresses some of the issues I have found when trying to deploy this on clean cluster.