You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 4, 2024. It is now read-only.
Thank you for building this great tool. I am using marathon-lb with DCOS, and the lack of good or clear documentation has stacked me for 2 days.
I think I read the documentation more than 10 times and it still not clear how I pre-load the ssl certificates do marathon-lb. I am launching marathon-lb from dcos catalog and I am having problems passing the certificates. I also tried creating my own image of marathon-lb and its not working as well.
My question is, how do I. pre-load more than one ssl-certificate to marathon-lb, to be able to use the label HAPROXY_0_SSL_CERT ?
The text was updated successfully, but these errors were encountered:
@ntk860 not sure if this is what you're asking for, but here's how I am doing it for multiple domains and their certs:
Firstly, you need to mount your SSL certs into the Docker images as volumes at a specific mount point for each domain, e.g. -v /path/to/ssl/cert/on/host:/target/in/docker/{DOMAIN_NAME}.
Then, pass the --ssl-certs CLI argument to the Docker entrypoint, using the target mount points you specified above, separated by commas, e.g. --ssl-certs /target/in/docker/domain1.com,/target/in/docker/domain2.com,...
Lastly, configure each app to use its appropriate domain name using the HAPROXY_0_VHOST label, e.g. HAPROXY_0_VHOST=domain1.com.
With this all set, Marathon-LB should automatically pick the right SSL cert for the incoming traffic (I believe using SNI), and will decrypt the traffic and forward it on to your configured backends appropriately.
There may be a more direct way to do exactly one cert per app, but I haven't seen it yet.
Hello There,
My question is, how do I. pre-load more than one ssl-certificate to marathon-lb, to be able to use the label HAPROXY_0_SSL_CERT ?
The text was updated successfully, but these errors were encountered: