How to collect Control Plane component logs for an RKE cluster when logging based on determined or selected namespaces

This document (000020959) is provided subject to the disclaimer at the end of this document.


By default, rancher-logging allows you to collect logs from all the control plane and node components for any clusters. However, you may want to select which namespaces to collect logs from, which for RKE clusters introduces an issue as the control plane components are deployed as containers and are not in any namespaces.


The simplest way to resolve this is by using the container_names directive with the logging app when creating the flow. This will allow you to list all the control plane or node components deployed as containers with the RKE clusters.
Below is an example of a cluster flow collecting logs based on a list of selected namespaces, which will not, without the container_names directive, collect the control plane components.
For this example, we have a cluster output cattle-logging-cluster-test-output forwarding logs to an endpoint of our choice, and you will have to do the same to see the logs in your logging infrastructure.

Note: Below is not an exhaustive list of all the RKE control plane containers and system namespaces, but the most common ones.
kind: ClusterFlow
  name: cattle-logging-cluster-test-flow
  namespace: cattle-logging
    - select:
           - kube-janitor
           - kube-node-lease
           - kube-public
           - kube-system
           - calico-system
           - cattle-fleet-system
           - cattle-impersonation-system
           - cattle-system
           - cattle-logging
           - default
           - opa
           - kube-apiserver
           - etcd
           - kubelet
    - cattle-logging-cluster-test-output


The control plane components are deployed as containers for an RKE cluster which makes the logging based on selected namespaces not pick their logs up.


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:000020959
  • Creation Date: 06-Feb-2023
  • Modified Date:06-Feb-2023
    • SUSE Rancher

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center