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

Notes on tasks to support Service Mesh OpenShift Dedicated

XMLWordPrintable

      The Service Mesh team has been asked to support OSSM on OpenShift Dedicated (in addition to on OpenShift Container Platform).

       

      NOTE - This has changed based on the new OpenShift Dedicated Content Strategy to have a separate repo for managed services docs.  (https://github.com/openshift/managed-openshift-docs )

      This ticket is to track the work that would be required to support publication of the existing OSSM content to the Dedicated output.

      [✔]Check all outgoing cross-references (do any point to content that is not published as part of the Dedicated output?)

      [✔]Figure out how to apply conditions (If/Then) to the cross-references that aren't published to Dedicated.

      [ ]Need to determine if the Elasticsearch configuration topic (from Logging) needs to be pulled in for Jaeger?

      [ ](Dedicated is our PaaS offering)  Need to understand how installing service mesh would work.  Would Operators already be installed, customers would just need to configure/deploy? Do we need to remove installation content? 

      [ ]Add an asterisk/note to mentions of "cluster-admin" permissions to indicate if you're on dedicated you need (need to verify the name) "Dedicated admin" permissions.

      [ ]Find out what changes are required to publish to the Customer Portal? (Add Service Mesh to the Dedicated page, and anything else?)

      [ ]Add "openshift-dedicated" label to content in the _topic_map.yaml file

      [✔]Need to have a Dedicated preview (cannot use the current 4.5 preview) (Preview in the PRs on GitHub supports Dedicated)

      [ ]Check preview of generated output

      [ ]Update the Supported Configurations topic to add support for OpenShift Dedicated

      [ ]Update the Release Notes to mention the new support.   (Question - Are there Release Notes for Dedicated?)

       [ ]We currently have "OpenShift Container Platform" as a variable in our document attributes file, because we're using ProductName for OSSM.  Not sure how we work around that, since the OpenShift team doesn't want "OpenShift" in the docs but prefers to use a variable.

       [ ]What level of support is required from docs for each Support level in this document?   https://docs.google.com/document/d/1OkiVpWmdGHlOY3b3A8__zR7ISRPWIF2rsZeppLsD4vk/edit#heading=h.70pe1zo2iira

              jstickler Julie Stickler (Inactive)
              jstickler Julie Stickler (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: