clusterLogForwarder outputs with no secrets incorrectly define bearer token auth in RHOCP 4

Solution Verified - Updated -

Issue

  • When defined an output in the clusterLogForwarder with not secret, it's added automatically a serviceaccount bearer token
  • Able to see in the collector configuration a bearer token auth not defined in the clusterLogForwarder configuration

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat OpenShift Logging (RHOL)
    • 5.8

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content