-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
0
-
False
-
-
False
-
?
-
rhos-connectivity-neutron-gluon
-
None
-
-
-
-
Moderate
Currently the way to customize configuration for services deployed on edpm nodes is:-
- Create a config map/secret map with the desired config and configured file pattern
- Create a Custom dataplane service(copy the default dataplane service for the service which needs to be customized and extend with the config map)
- Patch OpenstackDataplaneNodeset(services) or OpenstackDataplaneDeployment(servicesOverride) to point to this new custom service
But it would quite easier if this can be avoided by providing an optional configmap/secret in the default dataplane service so step 2/3 can be avoided. Can define some consistent naming(like <service/role-name>extra-config) Example: neutron-metadata-extra-config, neutron-ovn-extra-config, neutron-dhcp-extra-config etc