☂️ Expose additional machineclass fields in shoot API for users #649
Labels
area/robustness
Robustness, reliability, resilience related
area/usability
Usability related
kind/enhancement
Enhancement, improvement, extension
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
needs/planning
Needs (more) planning with other MCM maintainers
priority/3
Priority (lower number equals higher priority)
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 isMIGRATE
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.
The text was updated successfully, but these errors were encountered: