Kris Reese comments

Results 8 comments of


                                            Kris Reese

Install certificates to worker that all containers could inherit from

Can confirm @mymasse observation that managing secrets externally -AND- creating the `worker-additional-certs` secret does not work.

Install certificates to worker that all containers could inherit from

Also, when `secrets.enabled: true`, the key within the secret is created as `worker-certs`, not `worker-additional-certs`. Typically, it would see that the secret name is the same name as the key...

Installs wrong version on CentOS 7

Same issue here

bigip_vcmp_guest does not set DSC device name

It depends. If the `name` attribute given to `bigip_vcmp_guest` is the **same** as the `hostname` attribute of `bigip_hostname`, then desired state is not reached. This is because `bigip_vcmp_guest`'s name attribute...

The provided name must be a valid FQDN

Curious if this is roadmapped for fixing. cc: @focrensh

bigip_configsync_action with overwrite_config: yes can return "Recommended action: Synchronize to group"

I'm seeing similar behavior but in the `sync_group_to_device` attribute. ``` TASK [cloudfoundry : Sync Most Recent Changes Between LTM Peers] ***************** fatal: [sndltm-int01.blah.com]: FAILED! => {"changed": false, "msg": "Recommended action:...

bigip_vcmp_guest does not set DSC device name

I came across this devcentral article that may also explain what's going on here: https://community.f5.com/t5/technical-forum/device-name-under-device-management/td-p/202247

The provided name must be a valid FQDN

I can confirm this is fixed.