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.

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

Configure mcm-settings from worker to machine-deployment. #148

Closed
3 tasks
hardikdr opened this issue Jul 24, 2020 · 1 comment · Fixed by #149
Closed
3 tasks

Configure mcm-settings from worker to machine-deployment. #148

hardikdr opened this issue Jul 24, 2020 · 1 comment · Fixed by #149
Assignees
Labels
area/usability Usability related kind/enhancement Enhancement, improvement, extension platform/aws Amazon web services platform/infrastructure

Comments

@hardikdr
Copy link
Member

hardikdr commented Jul 24, 2020

How to categorize this issue?

/area usability
/kind enhancement
/priority normal
/platform aws

What would you like to be added: Machine-controller-manager now allows configuring certain controller-settings, per machine-deployment. Currently, the following fields can be set:

Also, with the PR gardener/gardener#2563 , these settings can be configured via shoot-resource as well.

We need to enhance the worker-extensions to read these settings from worker-object and set respectively on MachineDeployment.

Dependencies:

Why is this needed:
To allow a fine configuration of MCM via worker-object.

@hardikdr hardikdr added the kind/enhancement Enhancement, improvement, extension label Jul 24, 2020
@gardener-robot gardener-robot added area/usability Usability related platform/aws Amazon web services platform/infrastructure priority/normal labels Jul 24, 2020
@hardikdr
Copy link
Member Author

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/usability Usability related kind/enhancement Enhancement, improvement, extension platform/aws Amazon web services platform/infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants