DBZ-8206 introduces a compatibility issue with different config volume path. This poses a problem with backward compatibility. There are several options

1) Since this is a major version bump we could disregard the backwards compatibility
2) We could introduce a bit of branching logic and use different values based on version, this would however still pose a problem when custom images are used and thus tag is unreliable for decision making
3) We rework the way configuration is loaded on K8s – currently we create a config map with single `application.properties` key and a multiline value matching that of a regular property file. This config map key is then mapped as a file to the right location. We should be able to do the following

• enable the k8s config extension via environment variables and then let the k8s config extension to fully load the configuration directly from the config map
• an alternative is to map all configuration as envrioment variables