This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 44%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJG%3C/text%3E%3C/svg%3E)
Installing the azure backup extension on a new cluster work well, but we try to install it on an existing cluster.
The job dataprotection-microsoft-kubernetes-agent-upgrade-crds fails every time with a OOM. Our analysis shows, that the job fails after applying the CRDs (they all exists after the first run). It seems that kubectl requires more memory, when there are more CRDs available e.g. azure service operator v2 crds.
With more memory the job will complete and also the installation can complete successfully, when we delete the job right after the first failure. Is there any configuration we can do to increase the memory limit of the job?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 31%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Hi @Anonymous , you can try using this command to increase the memory limit for the extension. Do let us know in case if its still not successful
The spec of the job dataprotection-microsoft-kubernetes-agent-upgrade-crds does not use the memory parameters
az k8s-extension update --name azure-aks-backup --cluster-type managedClusters --cluster-name kyma --resource-group kyma-dev --release-train stable --configuration-settings blobContainer=... storageAccount=... storageAccountResourceGroup=... storageAccountSubscriptionId=... memoryLimit=2Gi
kubectl get job -n dataprotection-microsoft dataprotection-microsoft-kubernetes-agent-upgrade-crds -o yaml
but the parameter seems to be applied, when I checked the extension parameters in azure portal
I found a solution, there is a parameter upgradeJobResources.limits.memory for the job. But I don't know if it's possible with az. I'm using terraform.
The result looks good.
@Johannes Göhr Thanks for the update. Glad to know you were able to find the solution.
Thanks once again for sharing it with the community!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 36%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERR%3C/text%3E%3C/svg%3E)
@Anonymous Can you please let us know how many CRDs were there in your cluster? This will help us understand the data better and increase the default limits.