Jesse Hu
Jesse Hu
Thanks @jjlimepoint. Your case "172.18.x.x" makes sense. "add something to bootstrap options as a IP filter list" is a good solution. I will update it later.
Hi @jjlimepoint , I have updated the patch to use bootstrap options for the IP filter. Please take a look.
hi @fabriziopandini could we add the option MergeFromWithOptimisticLock to CAPI patch helper?
https://github.com/kubernetes-sigs/cluster-api/issues/8706 is exactly we meant. We hit bugs in the described scenario when using CAPI patchHelper.
@sbueringer Thanks very much for the summary. I totally agree on bullet 1/2/3. - To archive 1 (the ideal solution), it probably requires more work and more extensive change (as...
I observed the issue when upgrading CAPI components. Would it be able to produce the ClusterCacheTracker lock scenario when rolling update KCP controller deployment?
I'm sorry for the confusion that the forked repo was deleted by others today by mistake. I will create a new PR to handle the MS status update issue first...
🐛 Delete out of date machines with unhealthy control plane component conditions when rolling out KCP
LGTM! Waiting for CAPI team to take a look. Thanks!