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

[enterprise-4.13] Issue in file welcome/oke_about.adoc - Unclear support of logging in OKE

XMLWordPrintable

    • +
    • Important
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Customer Escalated, Customer Facing

      Description of problem:

      Unclear support of logging | log aggregation in Red Hat Kubernetes Engine

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

      N/A

      How reproducible:

      N/A

      Steps to Reproduce:

      1. Go to the OCP Documentation, About OpenShift Kubernetes Engine : https://docs.openshift.com/container-platform/4.13/welcome/oke_about.html 
      2. Search "Logging Platform"

      Actual results:

      Table 1. "Product comparison for OpenShift Kubernetes Engine and OpenShift Container Platform" shows that Platform Logging is supported/included in OKE as in OCP.
      
      Table 2. "Features in OpenShift Kubernetes Engine and OpenShift Container Platform" explicitly shows Platform Logging with "Red Hat OpenShift Logging Operator" is "Not included".
      
      In the paragraph "Advanced cluster management", it says "An OpenShift Kubernetes Engine subscription does not offer a cluster-wide log aggregation solution or support Elasticsearch, Fluentd, or Kibana based logging solutions."
      
      To me, Table 1 contradicts Table 2 and the paragraph ACM.

      Expected results:

      Correct Table 1.
      Or the wording is unclear. Maybe Table 1 show that OKE is **compatible** with the Red Hat OpenShift Logging Operator BUT does not include the license for it; that is, it should be a separate purchase.
      Or the tables are redundant.

      Additional info:

       

              rdlugyhe Rolfe Dlugy-Hegwer
              md6-sylvain-bentz Sylvain Bentz (Inactive)
              Anping Li Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: