NotManagedByMCM annotation incorrectly added by MCM to Node #863
Labels
area/quality
Output qualification (tests, checks, scans, automation in general, etc.) related
kind/bug
Bug
priority/2
Priority (lower number equals higher priority)
status/closed
Issue is closed (either delivered or triaged)
How to categorize this issue?
/area quality
/kind bug
/priority 2
What happened:
Node associated with machines that are managed by the
machine-controller
are being annotated with theNotManagedByMCM
(node.machine.sapcloud.io/not-managed-by-mcm="1"
) annotation. This can occur plane migration when the Node creation time stamps predate the Machine creation time stamps after control plane migration.What you expected to happen:
Ideally, Nodes should not be incorrectly tagged with this annotation. If they have this annotation, the annotation must be removed. A proper fix is described at #774 . Unfortunately, the solution proposed there will take more time since now even gardener code shoot health check is relying on the process of this
NotManagedByMCM
annotation.Solution Proposal
AnnotateNodesUnmanagedByMCM
(invoked by the safety reconciler), remove annotation if theNode
is already associated withMachine
, yet has this annotation set.30m
. Consider reducing to5m
after checking that all calls go through informer cache.How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
all mcm versions
kubectl version
): allWhat you expected to happen:
The text was updated successfully, but these errors were encountered: