In transition phase we have plans/instances driven only by KIM and plans/instances driven by provisioner but with Runtime CR managed by KEB.
In effect some instances are not know to provisioner and we fail on /runtimes endpoint where trying to fetch information from provisioner for given instance.
Adjust behavior for:
--gardener_config switch. gardener_config query parameter (to be removed after integration)
--cluster_config switch, cluster_config query parameter (should it be left after integration?)
Add --runtime_config switch, runtime_config query parameter, fetching Runtime CR spec for given instances.
AC:
[x] we do not fail for KIM driven instances, we do not return the structure (e.g. gardener_config if unavailable)
[x] we return runtime_config structure for --runtime_config switch/runtime_config query parameter
Consider scenarios with KIM only driven instances and provider driven ones, provider created but KIM driven etc.
In transition phase we have plans/instances driven only by KIM and plans/instances driven by provisioner but with Runtime CR managed by KEB.
In effect some instances are not know to provisioner and we fail on
/runtimesendpoint where trying to fetch information from provisioner for given instance.Adjust behavior for:
--gardener_configswitch.gardener_configquery parameter (to be removed after integration)--cluster_configswitch,cluster_configquery parameter (should it be left after integration?)Add
--runtime_configswitch,runtime_configquery parameter, fetching Runtime CR spec for given instances.AC:
gardener_configif unavailable)runtime_configstructure for--runtime_configswitch/runtime_configquery parameterConsider scenarios with KIM only driven instances and provider driven ones, provider created but KIM driven etc.