search

gardener / machine-controller-manager

Declarative way of managing machines for Kubernetes cluster
Apache License 2.0
257 stars 117 forks source link

☂️ Expose additional machineclass fields in shoot API for users #649

Open himanshu-kun opened 3 years ago

himanshu-kun commented 3 years ago

How to categorize this issue?

/area robustness /kind enhancement /priority 3

What would you like to be added: exposing any fields of machine class for the user to configure. Why is this needed: Many times the user will want to configure more and more options of the underlying MachineClass. Example : Gardener supports live migration on GCP , which automatically migrates your instance away from an infrastructure maintenance event, and your instance remains running during the migration . GCP Machineclass has a field providerSpec.onHostMaintainence for this, which is MIGRATE by default, but a user might not want it to be that everytime.

Many other fields on need basis could be exposed on the shoot API for the user's convenience. This is an umbrella issue to track these enhancements.

himanshu-kun commented 3 years ago

/invite @AxiomSamarth

gardener-robot commented 3 years ago

@himanshu-kun Command /invite is not allowed for issue but only for pullrequest.

himanshu-kun commented 3 years ago

cc @AxiomSamarth

himanshu-kun commented 2 years ago

throughput made configurable for gp3 volumes in provider-aws https://github.com/gardener/gardener-extension-provider-aws/pull/590