Incorrect SR-IOV removal steps, manual webhook removal can result in namespace termination.

    100%

    1. $ oc delete mutatingwebhookconfigurations.admissionregistration.k8s.io sriov-operator-webhook-config     
    2. wait ~2-3 min
    3. $ oc delete ns openshift-sriov-network-operator   

      NamespaceDeletionContentFailure              True    Thu, 07 Mar 2024 07:00:45 -0500  ContentDeletionFailed   Failed to delete all resource types, 2 remaining: Internal error occurred: failed calling webhook "operator-webhook.sriovnetwork.openshift.io": failed to call webhook: Post "https://operator-webhook-service.openshift-sriov-network-operator.svc:443/validating-custom-resource?timeout=10s": service "operator-webhook-service" not found, Internal error occurred: failed calling webhook "operator-webhook.sriovnetwork.openshift.io": failed to call webhook: Post "https://operator-webhook-service.openshift-sriov-network-operator.svc:443/validating-custom-resource?timeout=10s": service "operator-webhook-service" not found

    Webhooks should be disabled in SriovOperatorConfig:


$ oc get sriovoperatorconfigs.sriovnetwork.openshift.io -n openshift-sriov-network-operator default -oyaml
apiVersion: sriovnetwork.openshift.io/v1
kind: SriovOperatorConfig
metadata:
  creationTimestamp: "2024-02-20T08:53:07Z"
  generation: 3
  name: default
  namespace: openshift-sriov-network-operator
  resourceVersion: "16547895"
  uid: cf3a6849-be95-4e71-bd86-baf755d53fa3
spec:
  enableInjector: false
  enableOperatorWebhook: false
  logLevel: 2