Configurable ability to add Root CA or allow unverified https to object store

[carraher]

Need the ability to add root certificates authorities to containers that want to access object storage (database, builder, registry). This is needed to host secure-https on-prem object storage that is signed by a non-public CA.

Currently a non-public signed https object storage system results in
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:645)

1. Allow private/internal CAs to be added to containers.
2. Allow https to turn off verification, similar to curl -k

[bacongobbler]

this was added in v2.10.0: deis/controller#1158

Alternatively you can fork the controller and add your root CA to the cert for now.

Will that work for you?

[bacongobbler]

I just re-read your issue and the ticket I linked is different. That one is for communication from the controller to kubernetes, not from db/registry/builder to the object store. Sorry!

[bacongobbler]

If you're willing to take a crack at a PR, we'd likely accept it.

[Cryptophobia]

This issue was moved to teamhephy/workflow#44