What would you like to be added:
Currently, k-s-m expects the file provided in the config parameter to exist at startup. We are planning to take dependency on the config file by mounting it as an optional configmap which users can use to optionally override k-s-m configuration.

Why is this needed:
We are planning to take dependency on the config file but mounting it as an optional configmap. In this case, the users can create a configmap with options at any time and the k-s-m pod should be able to do a hot reload(already supported in k-s-m).

Describe the solution you'd like
k-s-m should continue to run when file doesnt exist and watch for file creation(file create watch functionality already exists today)

Additional context