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

Using openshift-operators as a targetNamespace should not be allowed

XMLWordPrintable

    • 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 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)

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

                Created:
                Updated:
                Resolved: