switch to http if letsencrypt #180
Merged
+15
−2
Conversation
This file contains 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
make sure that if requests are terminated in the ingress controller via letsencrypt the service runs via http. architect is currently replacing the SHAs in our helm charts. it's hardcoded that architect will template files called deployment.yaml. this is why i renamed the deployment.yaml to happa-deployment.yaml. the problem is now that architect doesn't replace the SHA anymore. so helm doesn't apply this against the cluster anymore. the temporary fix is to install the latest version of happa image. also distinguish lego secrets by a name. otherwise lego complains about the duplicate ingresses. ``` the secret giantswarm/ is used multiple times. These linked TLS ingress elements where ignored: ingress giantswarm/api (hosts: api.g8s.heisenberg.eu-central-1.aws.gigantic.io), ingress giantswarm/desmotes (hosts: desmotes.g8s.heisenberg.eu-central-1.aws.gigantic.io), ingress giantswarm/happa (hosts: happa.g8s.heisenberg.eu-central-1.aws.gigantic.io), ingress giantswarm/passage (hosts: passage.g8s.heisenberg.eu-central-1.aws.gigantic.io) ``` See: jetstack/kube-lego#35
|
FYI |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
make sure that if requests are terminated in the ingress controller via
letsencrypt the service runs via http.
architect is currently replacing the SHAs in our helm charts. it's
hardcoded that architect will template files called deployment.yaml.
this is why i renamed the deployment.yaml to
happa-deployment.yaml. the problem is now that architect doesn't
replace
the SHA anymore. so helm doesn't apply this against the cluster anymore.
the temporary fix is to install the latest version of happa image.
also distinguish lego secrets by a name. otherwise lego complains about
the
duplicate ingresses.
See: jetstack/kube-lego#35