Summary:
We must ensure hooks in argocd can block further execution. This is especially important for post-controlplane hook, where we must hold until all of the pods are removed. This action is done in the background, directly managed by the openstack-operator and k8s itself, and argocd has no way to know about those actions.

Goal:

• Answer the main question, with actual documentation pointers

TimeBox:

• ~1 day

Deliverables/Outcomes:

• Yes/No answer
• Pointers to doc if available