Enterprise SKRs use 80 GiB worker volumes

ebensom commented 3 weeks ago

Description

Migrate to use 80Gi volumes for aws, azure, gcp and plan Kyma runtimes instead of the current 50 GiB. Use these volume types:

Provider	Old disk type	New disk type	Old disk (50 Gi) cost / month	New disk (80 Gi) cost / month
AWS	gp2	gp3	5 USD	6.4 USD
Azure	Standard_LRS	StandardSSD_LRS	3.01 USD	9.60 USD
GCP	pd-standard	pd-balanced	2.4 USD	9.6 USD

Changes proposed in this pull request:

Change aws, azure and gcp plan provider codes (both for legacy provisioner and KIM integration) to create 80 GiB worker volumes accourding to the above table
For AWS trial and free, use gp3 instead of gp2 as it's more cost effective volume type.

Related issue(s)

https://github.tools.sap/kyma/backlog/issues/6109

github-actions[bot] commented 3 weeks ago

Add one of following labels

- kind/feature -> Use it when you want to submit a new feature

- kind/enhancement -> Use it when you modify or improve an existing feature

- kind/bug -> Use it when you fix a bug

ebensom commented 3 weeks ago

/label kind/enhancement

kyma-bot commented 3 weeks ago

@ebensom: The label(s) /label kind/enhancement cannot be applied. These labels are supported: tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, Epic. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to [this](https://github.com/kyma-project/kyma-environment-broker/pull/1096#issuecomment-2337718286): >/label kind/enhancement Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

kyma-project / kyma-environment-broker

Enterprise SKRs use 80 GiB worker volumes #1096