Allow Connections to Remote Docker via secured TLS #6
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.
With this the agent can connect to docker system that use Certificates to expose a secured TLS Connection, so you don't need to expose an unprotected Docker system.
Added a new section to the application.yml file
Currently only PEM_FILES support is implemented, there should be little reason for people to use a Keystore since it would require the pem files in the first place.
Official guide how to create the certificates: https://docs.docker.com/engine/security/https/
closes #4
As a little bonus allows to set
to disable orchestrator without having to remove configuration