Steps to reproduce:

• Deploy designate with customServiceConfig and defaultConfigOverwrite options set.
• Check each pod for the expected files under /etc/designate/designate.conf.d and /etc/designate/conf.d

Expected behavior

• Files exist and are accessible to be loaded by the service

Bug impact

• Workarounds and customizations are not available to the user

Known workaround

• There is no workaround for services where this exist

Additional context

• Found when attempting to work around rbac issues, both by creating configuration to disable RBAC policy checks and creating a policy file to workaround problematic built-in policies

To verify, create a unique entry for customerServiceConfig for each of designateAPI, designateCentral, designateProducer, designateWorker and designateMdns (designateBackendbind9 and designateUnbound don't support the same way). This can be an empty config with a comment e.g.
{{designateAPI: 
  customServiceConfig: |
 #designateAPI custom config
 designateCentral:
 customServiceConfig: |
  # designateCentral custom config}}

etc.

The "oc exec -it <podname> – /bin/cat /etc/designate/designate.conf.d/custom.conf" and verify the contents.