Continental Innovates with Rancher and Kubernetes
The Banzai Cloud Logging operator now powers Rancher’s logging solution in place of the former, in-house solution.
For an overview of the changes in v2.5, see this section. For information about migrating from Logging V1, see this page.
You can enable the logging for a Rancher managed cluster by going to the Apps page and installing the logging app.
Result: The logging app is deployed in the cattle-logging-system namespace.
Result rancher-logging is uninstalled.
For more information about how the logging application works, see this section.
Rancher logging has two roles, logging-admin and logging-view. For more information on how and when to use these roles, see this page.
To manage Flows, ClusterFlows, Outputs, and ClusterOutputs,
For help with configuring Flows and ClusterFlows, see this page.
For help with configuring Outputs and ClusterOutputs, see this page.
For a list of options that can be configured when the logging application is installed or upgraded, see this page.
Logging support for Windows clusters is available and logs can be collected from Windows nodes.
For details on how to enable or disable Windows node logging, see this section.
For details on using a custom Docker root directory, see this section.
For information on how to use taints and tolerations with the logging application, see this page.
For information on enabling the logging application for SELinux-enabled nodes, see this section.
By default, Rancher collects logs for control plane components and node components for all cluster types. In some cases additional logs can be collected. For details, see this section.
If your cluster previously deployed logging from the global view in the legacy Rancher UI, you may encounter an issue where its cattle-logging namespace is continually being recreated.
The solution is to delete all clusterloggings.management.cattle.io and projectloggings.management.cattle.io custom resources from the cluster specific namespace in the management cluster.
The existence of these custom resources causes Rancher to create the cattle-logging namespace in the downstream cluster if it does not exist.
The cluster namespace matches the cluster ID, so we need to find the cluster ID for each cluster.
# Cluster Management UI
# Cluster Dashboard
Now that we have the <cluster-id> namespace, we can delete the CRs that cause cattle-logging to be continually recreated.
Warning: ensure that logging, the version installed from the global view in the legacy Rancher UI, is not currently in use.
kubectl delete clusterloggings.management.cattle.io -n <cluster-id>
kubectl delete projectloggings.management.cattle.io -n <cluster-id>