Epic Goal

• tracking ticket for https://github.com/kubernetes/kubernetes/issues/105298

Many config options were migrated to the KubeletConfiguration, but --register-with-taints was missed. A user might want to register their node with taints based on the yaml config file instead of passing on the command line.

This issue is to track supporting RegisterWithTaints within the KubeletConfiguration structure and preserving the behavior of --register-with-taints.

Why is this important?

• on-prem customers want to provision nodes without allowing workloads to be scheduled until the node configuration is verified

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>