title | type |
---|---|
Upgrade shoots |
Tutorials |
This tutorial shows how to upgrade Gardener Shoot clusters for Kyma Runtimes.
NOTE: To access Runtime Provisioner, forward the port on which the GraphQL server is listening.
To upgrade a Gardener Shoot cluster used to host the Runtime of a given ID, make a call to Runtime Provisioner with a tenant header using a mutation like this:
mutation {
upgradeShoot(
id: "61d1841b-ccb5-44ed-a9ec-45f70cd1b0d3"
config: {
gardenerConfig: {
kubernetesVersion: "1.15.11"
volumeSizeGB: 35
machineType: "Standard_D2_v3"
diskType: "pd-standard"
machineImage: "gardenlinux"
machineImageVersion: "27.0.0"
purpose: "testing"
autoScalerMin: 2
autoScalerMax: 4
maxSurge: 4
maxUnavailable: 1
enableKubernetesVersionAutoUpdate: false
enableMachineImageVersionAutoUpdate: false
exposureClassName: ""
providerSpecificConfig: {
azureConfig: {
zones: ["1", "2"]
}
}
}
}
) {
id
operation
state
message
}
}
All the gardenerConfig
fields are optional here. If you don't include them, their values remain the same as before the upgrade.
A successful call returns the ID of the upgrade operation:
{
"data": {
"upgradeShoot": {
"id": "708202f7-bc8f-43b5-883c-7add36fba0aa",
"operation": "UpgradeShoot",
"state": "InProgress",
"message": "Starting Gardener Shoot upgrade"
}
}
}
The upgrade operation is asynchronous. Use the upgrade operation ID (upgradeShoot
) to check the Runtime operation status and verify that the upgrade was successful. Use the Runtime ID (id
) to check the Runtime status.