Uploaded image for project: 'Maistra'
  1. Maistra
  2. MAISTRA-1621

Gateways in non-cp namespaces are never pruned

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • maistra-2.1.0
    • None
    • None
    • None
    • Sprint 8, Sprint 9, Sprint 10

      When deploying a gateway to a namespace other than the control plane namespace, like so:

      apiVersion: maistra.io/v1
kind: ServiceMeshControlPlane
metadata: 
  name: mesh
  namespace: cp
spec: 
  istio: 
    gateways: 
      istio-ingressgateway: 
        namespace: other-namespace
  global: 
    istioNamespace: cp

      If you later remove the namespace: other-namespace, the gateway will be deployed to the cp namespace again, but the one in other-namespace will not be pruned.

      Use cases:

      • user removes gateway from smcp resource => gateway resources should be removed from "other-namespace"
      • user changes namespace for gateway => gateway resources should be removed from "other-namespace" and gateway should be installed in "new-namespace"
      • user removes namespace definition from gateway => gateway resources should be removed from "other-namespace" and gateway should be installed in cp namespace

              dgrimm@redhat.com Daniel Grimm
              dgrimm@redhat.com Daniel Grimm
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: