Antoine Cotten

@drybjed I don't think the issue is related to these variables, they are both explicitly set to a string value: ``` json TASK [DEBUG kubernetes_services_net] ******************************************* ok: [nemo] => {...

Sure thing: ``` json TASK [Print 'custom_pki_realms' on each node] ********************************** ok: [nemo] => { "custom_pki_realms": [ { "name": "k8s", "subject_alt_names": [ "ip:192.168.3.1", "ip:10.0.0.1", "dns:kubernetes.default.svc.my.cluster", "dns:kubernetes.default.svc", "dns:kubernetes.default", "dns:kubernetes" ] },...

Done, I left only the 3 last _dns:_ entries, without success.

It works when `custom_pki_realms` contains a single entry (single dictionary).

It also works with multiple entries (see first post) if I call the role as follows: ``` yaml - role: debops.pki tags: [ 'role::pki' ] pki_dependent_realms: '{{ custom_pki_realms }}' ```...

Oh, I see, thanks for the quick answer @drybjed !

@drybjed for some reason it doesn't work with the following addition: ``` yaml roles: - role: debops.pki/env tags: [ 'role::pki' ] pki_dependent_realms: - '{{ kubernetes_pki_dependent_realms }}' - role: debops.secret tags:...

@drybjed: Got it. That's because I'm passing my variable as a list like this: ``` yaml - role: debops.pki/env tags: [ 'role::pki' ] pki_dependent_realms: - '{{ kubernetes_pki_dependent_realms }}' ``` However...

@drybjed: Sure, on my side it's easy to work around that. What I was pointing out is that the behavior of the `debops.pki/env` role is not what the user might...

I'm not familiar with winston, but the UDP input isn't enabled by default: https://github.com/deviantony/docker-elk/blob/4df8c50ba8a1891c2cb4cd502ffc11868aec8cf1/logstash/pipeline/logstash.conf#L6-L8 In case your client doesn't support TCP, your can enable the UDP input inside the pipeline...