Dinko Korunic

Dear @dhyanKaro, it's already [included](https://github.com/dkorunic/iSMC/blob/9850551304f494ee1822739b4a4fc279f6144d5c/src/temp.txt#L166) and it should work, as long as the value can be parsed.

@jeid64 I went forth and overhauled the whole project (doesn't use root inside Docker, uses Compose, uses recent Ubuntu Xenial 16.04 LTS, updated docs, uses NodeJS 9.x etc.): [https://github.com/dkorunic/slackbridge](https://github.com/dkorunic/slackbridge). Cheers.

Each RUN creates another layer and there is no need to do that. I would recommend using boolean `&&` to merge multiple commands into a single chain that should fail...

Closing as resolved (through community chat).

Please if possible open an issue in [dataplaneapi issue tracker](https://github.com/haproxytech/dataplaneapi/issues), but in the meantime I'll ping DPAPI devs right away. Thanks!

We are internally discussing best way to move forward and `aws-lc` is being thoroughly tested.

This is actively being worked on.

@Roxyrob Can you try with the following custom settings, where `controller.defaultTLSSecret.secretNamespace` refers to your custom namespace? ``` controller: defaultTLSSecret: enabled: true secretNamespace: namespace ```

I haven't been able to reproduce your issue, it works for me without any issues. Configuration override used: ``` controller: defaultTLSSecret: enabled: true secretNamespace: testspace ``` Helm command to install:...

In fact, I was wrong in thinking that we need to match `controller.defaultTLSSecret.secretNamespace`, it contains `'{{ include "kubernetes-ingress.namespace" . }}'` which will correctly render into string with `{{ tpl .Values.controller.defaultTLSSecret.secretNamespace...