Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
himanshu-kun opened this issue Oct 20, 2021 · 4 comments
Open

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

himanshu-kun opened this issue Oct 20, 2021 · 4 comments
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)

Comments

@himanshu-kun
Copy link
Contributor

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 himanshu-kun added kind/enhancement Enhancement, improvement, extension exp/intermediate Issue that requires some project experience effort/2d Effort for issue is around 2 days labels Oct 20, 2021
@gardener-robot gardener-robot added area/robustness Robustness, reliability, resilience related priority/3 Priority (lower number equals higher priority) labels Oct 20, 2021
@himanshu-kun himanshu-kun changed the title Expose additional machineclass fields in shoot API for users ☂️ Expose additional machineclass fields in shoot API for users Oct 20, 2021
@himanshu-kun
Copy link
Contributor Author

/invite @AxiomSamarth

@gardener-robot
Copy link

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

@himanshu-kun
Copy link
Contributor Author

cc @AxiomSamarth

@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Apr 19, 2022
@himanshu-kun
Copy link
Contributor Author

himanshu-kun commented Aug 24, 2022 •
edited
Loading

throughput made configurable for gp3 volumes in provider-aws
gardener/gardener-extension-provider-aws#590

@himanshu-kun himanshu-kun added area/usability Usability related needs/planning Needs (more) planning with other MCM maintainers and removed lifecycle/stale Nobody worked on this for 6 months (will further age) exp/intermediate Issue that requires some project experience effort/2d Effort for issue is around 2 days labels Feb 23, 2023
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Nov 2, 2023
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gardener-robot @himanshu-kun