-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Togglable TLS Redirect #1322
Togglable TLS Redirect #1322
Conversation
Hey there @Legogris, while we discuss merging this PR, would setting
|
@dimroc I would actually like the inverse; having |
@Legogris did this work for your setup? |
@j16r It did achieve exactly what's under scope here and I do think this is going to be a somewhat common deployment scenario. But to solve it fully for our specific scenario it's not sufficient; because we are using a Google Cloud Load Balancer on a Kubernetes Ingress, which enforces a health check that is hard on But in the end we went with using a sidecard container which proxies all requests except those ones to the Chainlink node and returns an HTTP code based on the health of the Chainlink node container. |
Would you mind adding this new variable to the presenter: https://github.com/smartcontractkit/chainlink/blob/develop/core/store/presenters/presenters.go#L149 |
Sure! |
@Legogris any update on this? Looks like it needs a rebase at this point. |
closing in favor of #1546 |
@se3000 Thanks for taking the time to sort this out :) |
Add a flag
TLS_REDIRECT
(default off) which can be used to enforce TLS redirection for unencrypted HTTP connections.