Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-39604

Shared Ingress Resources Remain After Hypershift Operator Uninstallation

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Low
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Steps to Reproduce:

      1. Create AKS MC
      2. Install HO (shared ingress enabled)
      3. Uninstall HO
      hypershift install render ... --format=yaml --outputs resources | oc delete -f -
      hypershift install render ... --format=yaml --outputs crds | oc delete -f -    
      4. Check resources within the hypershift-sharedingress namespace

      Actual results:

      oc get all -n hypershift-sharedingress
      NAME                          READY   STATUS    RESTARTS   AGE
      pod/router-77447779b4-z7vkt   1/1     Running   0          60m
      
      
      NAME             TYPE           CLUSTER-IP    EXTERNAL-IP      PORT(S)                        AGE
      service/router   LoadBalancer   10.0.131.51   52.171.236.158   443:31878/TCP,6443:31103/TCP   132m
      
      
      NAME                     READY   UP-TO-DATE   AVAILABLE   AGE
      deployment.apps/router   1/1     1            1           132m
      
      
      NAME                                DESIRED   CURRENT   READY   AGE
      replicaset.apps/router-5cff59ccf7   0         0         0       96m
      replicaset.apps/router-758c9bdc9c   0         0         0       98m
      replicaset.apps/router-77447779b4   1         1         1       132m

              hypershift-automation hypershift-team automation
              fxierh Feilian Xie (Inactive)
              None
              None
              He Liu He Liu
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: