Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3639

[RN] Allow to configure subdomain isolation for GitHub Enterprise Server in CheCluster CR

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 3.3.0.GA
    • 3.3.0.GA
    • None
    • None
    • False
    • None
    • False
    • Release Notes
    • Hide
      = Supported subdomain isolation for GitHub Enterprise Server

      With this update, {prod-short} supports link:https://docs.github.com/en/enterprise-server@3.5/admin/configuration/configuring-network-settings/enabling-subdomain-isolation[subdomain isolation] for GitHub Enterprise Server customers. Administrators can enable subdomain isolation in the `CheCluster` custom resource:

      [yaml,source]
      ----
      spec:
        gitServices:
          github:
            - endpoint: 'https://github.com'
              secretName: github-oauth-config
              disableSubdomainIsolation: true
      ----
      Show
      = Supported subdomain isolation for GitHub Enterprise Server With this update, {prod-short} supports link: https://docs.github.com/en/enterprise-server@3.5/admin/configuration/configuring-network-settings/enabling-subdomain-isolation [subdomain isolation] for GitHub Enterprise Server customers. Administrators can enable subdomain isolation in the `CheCluster` custom resource: [yaml,source] ---- spec:   gitServices:     github:       - endpoint: ' https://github.com'         secretName: github-oauth-config         disableSubdomainIsolation: true ----
    • Enhancement
    • Done

    Attachments

      Issue Links

        is documented by

        Patch - An improvement or enhancement to an existing feature or task. Includes patches submitted by community commiters. RHDEVDOCS-4810 Document subdomain isolation for GitHub Enterprise Server customers in CheCluster CR

        • 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

        Web Link https://github.com/eclipse/che/issues/21724

        Activity

          People

            rhn-support-mleonov Max Leonov
            rhn-support-mleonov Max Leonov
            Max Leonov Max Leonov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: