Epic Goal

Logs should be available for all pods regardless of cluster type. Currently for non-OCP clusters the user will need to configure a LoadBalancer to expose the service required to retrieve pod logs. We want to enable this by default.

Why is this important?

In keeping with our message of Kubernetes management, we should be able to manage all Kube resources out of the box where possible. To provide users with a clear understanding of pod health on all clusters they should be able to access all pod logs regardless of cluster type.

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.
Logs service is exposed correctly on cluster import.
Search logs page is seamless in getting logs for all pods. OR Search displays an alert/message for how to configure the cluster correctly (TBD).

Can the backend expose the service correctly on cluster import so that the UI is seamless in getting logs for all cluster types? Or will the UI need to display an alert/ message to docs to guide the user in creating the appropriate resources to expose the service?

CI - CI is running, tests are automated and merged.
Release Enablement <link to Feature Enablement Presentation>
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Polarion: <link or reference to Polarion>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>