It’s known issue, does not influences either updater or storagenode and can be safely ignored.
It’s not related to the config.yaml itself, it’s related to the storagenode-updater, which doesn’t aware of keys for storagenode. You do not need to modify your config.yaml
What is the real problem?
Is the node offline?
If so, please, check all points from the checklist: