Uploaded image for project: 'Multiple Architecture Enablement'
  1. Multiple Architecture Enablement
  2. MULTIARCH-5367

The validating webhook for the ClusterPodPlacementConfig should deny deletion if any PodPlacementConfig is deployed in the cluster

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • MTO Sprint 272, MTO Sprint 273, MTO Sprint 275

      According to https://github.com/openshift/multiarch-tuning-operator/blob/main/docs/enhancements/MTO-0002-local-pod-placement.md#changes-to-the-multiarch-tuning-operator, the validating webhook for the ClusterPodPlacementConfig should deny the deletion of the singleton ClusterPodPlacementConfig unless all the PodPlacementConfigs are deleted first.

      Acceptance criteria:

      • The deletion of ClusterPodPlacementConfig is denied if any PodPlacementConfig is stored in the cluster's db
      • Unit tests are created for each new function that has no dependencies on external services
      • Integration tests might be skipped here as they might be unable to test the validating webhook behavior (double check first)
      • E2E tests are implemented

              lwan-wanglin Lin Wang
              rhn-support-adistefa Alessandro Di Stefano
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: