XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo

      By default, DVM routes are default labeled

       dvm         dvm-mtc.apps.lperezbe-cluster1.sbr-shift.gsslab.brq2.redhat.com                dvm         6443    passthrough     None       app.kubernetes.io/part-of=openshift-migration,app=directvolumemigration-rsync-transfer,directvolumemigration=aac8ea9f-20ae-4a5a-bf35-07be60b0ec9a,migration.openshift.io/migrated-by-migplan=6ee8233a-4672-4743-81c4-059fe633f177,owner=directvolumemigration,purpose=rsync
      dvm-block   dvm-block-mtc.apps.lperezbe-cluster1.sbr-shift.gsslab.brq2.redhat.com          dvm-block   6443    passthrough     None       app.kubernetes.io/part-of=openshift-migration,app=directvolumemigration-rsync-transfer-block,directvolumemigration=aac8ea9f-20ae-4a5a-bf35-07be60b0ec9a,migration.openshift.io/migrated-by-migplan=6ee8233a-4672-4743-81c4-059fe633f177,owner=directvolumemigration,purpose=rsync

      Since some customers are using custom IngressControllers for ingress traffic, there might be some scenarios where routes require to be labeled (when a routeSelector is specified on the IngressController)

          routeSelector:
            matchExpressions:
            - key: xxxx
              operator: In
              values: 

              rhn-engineering-dymurray Dylan Murray
              rhn-support-lperezbe Luis Perez Besa
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: