Support to propagate properties in-place from MachineDeployments to Machines

[enxebre]

User Story

As a cluster operator I would like to change the NodeDrainTimeout/NodeDeletionTimeout for the Machines belonging to a MachineDeployment.

Detailed Description

Today this would trigger a rolling upgrade honouring current NodeDrainTimeout in Machines which defeats the purpose of the change. We should consider NodeDrainTimeout to propagate in-place from MachineDeployments to Machines.

Anything else you would like to add:
If we do this, base code should be scalable to have a clean way to include fields.
This might be relevant for #6255 as well

[Miscellaneous information that will assist in solving the issue.]

/kind feature

[fabriziopandini]

/milestone v1.1

[enxebre]

/milestone v1.2

[sbueringer]

Note: there's now also a NodeDeletionTimeout which we should treat the same way.

[enxebre]

/retitle support to propagate properties in-place from MachineDeployments to Machines

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[vincepri]

/lifecycle frozen

[vincepri]

/milestone Next

[fabriziopandini]

/triage accepted
/assign @fabriziopandini

[fabriziopandini]

moving out from the milestone because this will land later when also label propagation is fully addressed (hopefully in 1.4)

[sbueringer]

@ykakarap Can you please double-check if this issue is now done with our recent implementations and close the issue if it makes sense.

[fabriziopandini]

/unassign
/assign @ykakarap

[ykakarap]

This issue is addressed in the in-place propagation work (#7731).

The feature is merged and available.

We can close this issue.

/close

[k8s-ci-robot]

@ykakarap: Closing this issue.

In response to this:

This issue is addressed in the in-place propagation work (#7731).

The feature is merged and available.

We can close this isuse.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.