AMO 🐶⛺🌳

_From @johnschultz on June 22, 2017 7:2_ @bacongobbler really interested in how you got that to work. Is that blog post up somewhere or can you point me in the...

_From @mariusmarais on June 22, 2017 8:1_ @johnschultz Native ingress via Traefik with its built-in Let Encrypt support is working quite well for us too. Default app names work perfectly,...

_From @ccatlett2000 on July 5, 2017 0:38_ Any progress on this? Yes, I can use native ingresses, but using Deis's router is preferable.

_From @bacongobbler on July 5, 2017 4:56_ No progress. The "hack" I did was merely just manually editing ingress routes and installing the nginx ingress controller, along with kube-lego. No...

_From @ccatlett2000 on July 5, 2017 19:25_ Does anyone who's setup native ingresses know if Deis adds the annotations for TLS (Or if there is a way to configure them)?...

_From @bacongobbler on July 5, 2017 19:27_ It does not; I had to manually edit the ingress resources to add those annotations in.

_From @bacongobbler on March 6, 2017 15:27_ It is not possible to reference the downward API today with pods. However, you can infer the pod namespace by the application name,...

_From @gottfrois on March 6, 2017 15:45_ thanks @bacongobbler for the quick answer. Being able to know POD IP as well as the host the POD is running on might...

_From @gottfrois on March 6, 2017 16:2_ The workaround I see is to manually query the k8s api within the POD using the following command: ``` $ KUBE_TOKEN=$(< /var/run/secrets/kubernetes.io/serviceaccount/token) $...

_From @gottfrois on March 6, 2017 16:13_ It would then be possible to execute a bash script to populate the `HTTP_PROXY` env variable: ``` command: - "/bin/bash" - "-c" -...