Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-2868

Using openshift-operators as a targetNamespace should not be allowed

    XMLWordPrintable

Details

    • 2
    • False
    • None
    • False
    • Hide
      `targetNamespace` restriction introduced in OpenShift environment. `openshift-operators` namespace is not allowed as `targetNamespace`. If you are have configured `openshift-operators` as targetNamespace, change the targetNamespace to different one, then upgrade your tekton operator instance. If you upgrade with your pipeline components on `openshift-operators`, after upgrade you are not allowed to change anything in our TektonConfig CR (except targetNamespace)
      Show
      `targetNamespace` restriction introduced in OpenShift environment. `openshift-operators` namespace is not allowed as `targetNamespace`. If you are have configured `openshift-operators` as targetNamespace, change the targetNamespace to different one, then upgrade your tekton operator instance. If you upgrade with your pipeline components on `openshift-operators`, after upgrade you are not allowed to change anything in our TektonConfig CR (except targetNamespace)
    • Pipelines Sprint 237, Pipelines Sprint 238, Pipelines Sprint 239, Pipelines Sprint 240, Pipelines Sprint 245, Pipelines Sprint 246, Pipelines Sprint 247

    Description

      Description of problem:

      When setting targetNamespace to openshift-operators leads to some possible very weird behavior for other operators that are installed here.

      See https://issues.redhat.com/browse/ROX-15440?focusedCommentId=21836652&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-21836652

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      • Install the operator
      • Update tektonconfig to set the targetNamespace to openshift-operators

      Actual results:

      It is allowed, and it might break other operators or upgrades.

      Expected results:

      It is disallowed.

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

      We should just update the tektonconfig_validation.go and disallow a set of hardcoded namespaces (like openshift-operators)

      Attachments

        Issue Links

          is cloned by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. RHDEVDOCS-5495 Using openshift-operators as a targetNamespace should not be allowed

          • Critical - To be worked on immediately following BLOCKER issues.
          • Pull Request Sent
          is documented by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. RHDEVDOCS-5495 Using openshift-operators as a targetNamespace should not be allowed

          • Critical - To be worked on immediately following BLOCKER issues.
          • Pull Request Sent
          is related to

          Bug - A problem that impairs or prevents the functions of the product. SRVKP-3530 updating "targetNamespace" in tektonConfig CR is not working as expected

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          Web Link The OpenShift Pipelines TektonConfig targetNamespace can cause other workloads to fail

          Activity

            People

              jkandasa-rh Jeeva Kandasamy
              vdemeest Vincent Demeester
              Veeresh Aradhya Veeresh Aradhya
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: