Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-6296

Applications do not cleanup properly after deletion when syncOption: - CreateNamespace=true

XMLWordPrintable

    • None
    • Product / Portfolio Work
    • None
    • False
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      What are the nature and description of the request?

      An Application configured with `spec/syncPolicy/syncOptions/CreateNamespace=true` leave behind the Namespace and Project resources when deleted. There is no direct support for "DeleteNamespace=true" style policy within Argo CD currently

      Why does the customer need this? (List the business requirements here)

      We expect the Operator to properly cleanup resources. This improves the Platform Teams and Developers experience when operating the cluster.

      Having many orphaned Namespaces leads to some confusion and messiness from the users perspective.

      How would the customer like to achieve this? (List the functional requirements here)

      Applications should leave behind no resources that they created when deleted.

              halawren@redhat.com Harriet Lawrence
              rhn-support-gio Ginilekshmi A O (Inactive)
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                None
                None