You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have noticed resources of kinds that are configured as AllowPropagate being deleted during our infrastructure provisioning process (even if the resources are not configured to propagate with HNC) if they share the name of a resource of the same kind in the parent namespace.
We were able to reproduce the issue reliably with a build of HNC from the master branch with this small patch that inserts a sleep to make sure the race condition can be reliably hit.
We have noticed resources of kinds that are configured as AllowPropagate being deleted during our infrastructure provisioning process (even if the resources are not configured to propagate with HNC) if they share the name of a resource of the same kind in the parent namespace.
We were able to reproduce the issue reliably with a build of HNC from the master branch with this small patch that inserts a sleep to make sure the race condition can be reliably hit.
Steps to Reproduce:
HNCConfiguration
configuringconfigmaps
tomode: AllowPropagate
.parentns
) and child namespace (childns
).testmap
inparentns
(with no labels that would configure it to propagate with HNC)HierarchyConfiguration
tochildns
settingparentns
as the parent ofchildns
SLEEPING
log line output from the patch above.testmap
inchildns
(with no labels that would configure it to propagate with HNC)DONE SLEEPING
log line.The text was updated successfully, but these errors were encountered: