-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KIM migration - KEB: Migrate from provisioner to Kyma Infrastructure Manager #791
Comments
Technical detail: Do not use InputCreator for creating Runtime CR. All information we need to create the CR we have in the Operationb and Provisioning Parameters. |
@kyma-project/framefrog We need to clarify some fields (presence, values):
Provider specific fields (sent to provisioner):
|
@kyma-project/framefrog I have a questions regarding a time of migration and the update.
|
@jaroslaw-pieszka Please see my comments below We agreed the following:
For more details on the components responsibilities please see this ADR document. Answers:
|
Acceptance Criteria
Phase 1: (driving system Provisioner for creation, Runtime CR spec is not passed to gardener, Runtime CR status is already present)
and create GardenerCluster(for later: do not create GardenerCluster CR, just watch a secret by convention name)support upgrade cluster operation which call Provisionerand delete Runtime CR (this one we need to double check, cause with Runtime CR SRE will upgrade cluster just by modifying Runtime CR directly) KIM Integration - double check that upgrade operation is done directly on Runtime CR #1072 Upgrade would be handled by SREruntimes
endpoint to support instances not known to provisioner (KIM driven) and to support fetching Runtime CR spec. KIM Integration - adjust kcp CLI in transition phase #1070Expected result from phase 1:
Phase 2: (driving system KIM for creation, Provioner spec is not passed to gardener, Runtime CR status is already present)
Expected result from phase 2:
Phase 3:
Expected result from phase 3:
The text was updated successfully, but these errors were encountered: