Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-8878

RN - BuildConfigs cannot be created in namespaces with injection enabled

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • OSSM 3.0.0
    • None
    • Sail Operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Release Notes
    • Hide
      There is currently a known issue where OpenShift builder pods cannot be created in namespaces with injection enabled.

      Workaround: add injection labels to your workloads instead of the namespace when you need to create BuildConfigs in that namespace.

      Additional Resources:
      [BuildConfig|https://docs.openshift.com/container-platform/4.17/cicd/builds/understanding-buildconfigs.html#builds-buildconfig_understanding-builds]
      Show
      There is currently a known issue where OpenShift builder pods cannot be created in namespaces with injection enabled. Workaround: add injection labels to your workloads instead of the namespace when you need to create BuildConfigs in that namespace. Additional Resources: [BuildConfig| https://docs.openshift.com/container-platform/4.17/cicd/builds/understanding-buildconfigs.html#builds-buildconfig_understanding-builds ]
    • Known Issue

      BuildConfigs cannot be created in namespaces with injection enabled.

      The issue is that when the build container gets created inside a namespace with injection enabled, a proxy will get injected into the build container preventing it from communicating with external endpoints like github. There's also no way to add labels to the BuildConfig pod to prevent the proxy from being injected.

      The workaround is to label your workloads for injection and not the namespace when you need to create BuildConfigs in that namespace.

              Unassigned Unassigned
              nfox@redhat.com Nick Fox
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: