Loading
daemons: rework configuration passing in conveyor. #65
Each daemon will now have its own config secret with two sections: "common" and "component". The common is the same for all daemons. I initially thought about having a separate "common" kube secret shared among all daemons, but changed my mind. I consider that having two secrets makes the configuration flow more complex while the benefit (no duplication) is small. As long as values.exportConfigToEnv==True, the change must not impact existing deployments. The new secrets will be generated in kube, mounter into containers, but not used by rucio. The associated change in rucio/containers must be integrated into containers before setting this variable to False. If the new behavior is accepted, all daemons and servers will have to be updated. I also vote for breaking the reverse compatibility in 1.27 and remove code exporting the config as env variables.