cannot create net-attach-def resource when one of namespace failed to create/update

[sunya-ch]

• [ ] checked https://foundation-model-stack.github.io/multi-nic-cni/user_guide/troubleshooting/.
• [ ] titled with the bug issue (if applicable).
• [ ] provided corresponding information regarding the troubleshooting guidelines (CR list/detail, multi-nic cni controller and/or daemon status/log).

Describe the bug A clear and concise description of what the bug is.

When any of namespace is in terminating state which causing an error to create/update net-attach-def in that namespace, multi-nic-cni may not be able to continue updating net-attach-def for the other newly-created namespace due to that error.

https://github.com/foundation-model-stack/multi-nic-cni/blob/fba59cff7b7c320fcd12c712209303f0caa7f4ca/plugin/net_attach_def.go#L120-L131

To Reproduce Steps to reproduce the behavior:

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

• manager container of controller and multi-nicd DS status:
• multinicnetwork CR:
• hostinterface list/CR:
• cidr CR (multiNICIPAM: true):
• ippools CR (multiNICIPAM: true):
• log of manager container:
• log of failed multi-nicd pod:

Environment (please complete the following information):

• platform: [e.g. self-managed k8s, self-managed OpenShift, EKS, IKS, AKS]
• node profile:
• operator version :
• cluster scale (number of nodes, pods, interfaces):

Additional context Add any other context about the problem here.

[sunya-ch]

handled by https://github.com/foundation-model-stack/multi-nic-cni/pull/114