Open PK85 opened 4 months ago
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):
spec.shoot.provider.workers.name
- described as optional, but required - what name should we provide, will we select workers group later on by name or index (assigning parameters to workers[0] or worker of specific name)LicenceType
- it is the CRD spec, do you use it, is it optional, should it be in the spec or should it be a labelNetworking.Filter.Egress.Enabled
- value based on LicenceType
- is the value the same as ShootNetworkingFilterDisabled
in provisioner contract?euAccess
- present in provisioner contract, not in Runtime CRD - should we add it as a label or should the spec be extended?ExposureClassName
- we passed it for sap-converged-cloud - should we somehow support it?EnableKubernetesVersionAutoUpdate
- was in the contract with provisioner - not used/forgotten?EnableMachineImageVersionAutoUpdate
- was in the contract with provisioner - not used/forgotten?Provider specific fields (sent to provisioner):
@kyma-project/framefrog I have a questions regarding a time of migration and the update. Let's imagine a scenario:
@kyma-project/framefrog We need to clarify some fields (presence, values):
spec.shoot.provider.workers.name
- described as optional, but required - what name should we provide, will we select workers group later on by name or index (assigning parameters to workers[0] or worker of specific name)LicenceType
- it is the CRD spec, do you use it, is it optional, should it be in the spec or should it be a labelNetworking.Filter.Egress.Enabled
- value based onLicenceType
- is the value the same asShootNetworkingFilterDisabled
in provisioner contract?euAccess
- present in provisioner contract, not in Runtime CRD - should we add it as a label or should the spec be extended?ExposureClassName
- we passed it for sap-converged-cloud - should we somehow support it?EnableKubernetesVersionAutoUpdate
- was in the contract with provisioner - not used/forgotten?EnableMachineImageVersionAutoUpdate
- was in the contract with provisioner - not used/forgotten?Provider specific fields (sent to provisioner):
- Azure: VnetCidr,EnableNatGateway, IdleConnectionTimeoutMinutes)
- AWS: VpcCidr, EnableIMDSv2
- sap-converged-cloud: FloatingPoolName, CloudProfileName, LoadBalancerProvider
@jaroslaw-pieszka Please see my comments below
We agreed the following:
For more details on the components responsibilities please see this ADR document.
Answers:
spec.shoot.provider.workers.name
you can use any string, Provisioner has hardcoded cpu-worker-0
LicenceType
is not required ; when passed in the CR it will be used for setting infrastructuremanager.kyma-project.io/licence-type
annotation ; basically it is equivalent to licenceType
field in GraphQLNetworking.Filter.Egress.Enabled
is a negation of Provisioner's ShootNetworkingFilterDisabled
euAccess
annotation (please see this code)ExposureClassName
(please see this code)EnableKubernetesVersionAutoUpdate
and EnableMachineImageVersionAutoUpdate
is handled by KIM (please see the code and configuration
Acceptance Criteria
Phase 1: (driving system Provisioner for creation, Runtime CR spec is not passed to gardener, Runtime CR status is already present)
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) #1072 Upgrade would be handled by SREruntimes
endpoint to support instances not known to provisioner (KIM driven) and to support fetching Runtime CR spec. #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: