You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For preparing the rollout of KIM on our KCP landscape DEV + STAGE (not on PROD!), please configure in KEB for all plans following behaviour:
the controlling system for Shoot-Clusters is still the Provisioner (kyma-project.io/controlled-by-provisioner: "true", see PR)
please create / update also the RuntimeCR when sending a call to Provisioner
This will simulate the real behaviour later on production. But KIM will only run in "Dry-Run" mode (creating Shoot-Specs but these specs won't be considered by Gardener) and we can compare KIM's produced Shoot-Spec with the Shoot-Spec which was created by the Provisioner.
Reasons
Allow testing of KIM by enabling it to create/update Shoot-Specs.
Description
For preparing the rollout of KIM on our KCP landscape DEV + STAGE (not on PROD!), please configure in KEB for all plans following behaviour:
kyma-project.io/controlled-by-provisioner: "true"
, see PR)RuntimeCR
when sending a call to ProvisionerThis will simulate the real behaviour later on production. But KIM will only run in "Dry-Run" mode (creating Shoot-Specs but these specs won't be considered by Gardener) and we can compare KIM's produced Shoot-Spec with the Shoot-Spec which was created by the Provisioner.
Reasons
Allow testing of KIM by enabling it to create/update Shoot-Specs.
Attachments
Related to
The text was updated successfully, but these errors were encountered: