Thanks Jarek I register a bit of a mixed message.
Re this Maybe I am wrong but I think the separation should be solved together, > there is a good reason why some k8s settings are in core. > Are you saying I should not proceed with this plan *(add warnings in KPO that push users to start using K8s Hook connection for config instead of "core" k8s config settings before 3.0)* until we figure out the other things you referenced, or that you are in favor of doing this deprecation but you also think that we should resolve those other concerns too by the time we actually remove support? Thanks
