Open
Conversation
7dc23c5 to
020a251
Compare
020a251 to
44338c9
Compare
88994e4 to
ac9354d
Compare
e059c1e to
d052469
Compare
d052469 to
72cd5b8
Compare
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
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.
Fixes: simplyblock/vela#169
The database connection endpoint connects to PGBouncer service. So the changes in PR sets up TLS termination for at PGBouncer.
As a part of this changes, we create the certificate:
On the vela-os side, we first start the PGBouncer without TLS and the then certificates are available, we reload the PGbouncer with Certificates.
It can be observed below that the PGBouncer has intially connect in TLS mode and after a minute, it's connected with TLS.
and on the vela-os side (PR: simplyblock/vela-os#22)
we wait for certificate and then load then when they become available.