Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-5474

[4.12]Default CatalogSource aren't created in restricted mode

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Normal
    • 4.12.z
    • 4.13.z, 4.12.z
    • OLM
    • None
    • Moderate
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      The default catalogSources are not being ran in restricted mode.

      Version-Release number of selected component (if applicable):

      4.12.0

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create an 4.12 openshift cluster
2. Check the securityContextConfig for the default catalogSources

      Actual results:

      $ k get catsrc  -n openshift-marketplace -o yaml | grep securityContextConfig
    securityContextConfig: legacy
    securityContextConfig: legacy
    securityContextConfig: legacy
    securityContextConfig: legacy

      Expected results:

      $ k get catsrc  -n openshift-marketplace -o yaml | grep securityContextConfig
      securityContextConfig: restricted
      securityContextConfig: restricted
      securityContextConfig: restricted
      securityContextConfig: restricted

      Additional info:

       

       

       

       

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-5473 [4.13] Default CatalogSource aren't created in restricted mode

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          depends on

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-5473 [4.13] Default CatalogSource aren't created in restricted mode

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          GitHub operator-framework/operator-marketplace#500: [release-4.12] OCPBUGS-5474: Run Default CatalogSource in Restricted mode

          Activity

            People

              agreene1991 Alexander Greene
              agreene1991 Alexander Greene
              Jian Zhang Jian Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: