Debezium Server supports configuration loading from config maps and secrets. However currently we construct the configuration application.properties, which is stored in config map as a while (under single application.properties key) and then mounted as a file. Additional configuration can be loaded from config maps/secrets and referenced in this property file (as it is correctly resolved by smallrye config).

This solution is rather cumbersome. What we should do in k8s is

• enable kuberenetes-config and map/secret sources by defaul via ENVVAR
• have the rest of the configuration only in the config map with each configuration property as it's own entry