在 GKE 迁移到 containerd 后，容器运行时的日志量显着增加
[英]The amount of container-runtime's logs increased significantly after migration to containerd at GKE
问题描述
After we migrated our Kubernetes cluster at GKE to the containerd-based node image type, the amount of logs produced by container-runtime has increased drastically (see a screenshot).
在我们将 GKE 的 Kubernetes 集群迁移到基于容器的节点映像类型后， container-runtime产生的日志量急剧增加（见截图）。 Most of those log records are of info type and log some containerd's operations.这些日志记录大部分是info类型，记录了一些 containerd 的操作。 The amount of produced logs is huge - some millions records per day, that creates additional costs each day.产生的日志数量巨大——每天有数百万条记录，每天都会产生额外的成本。
Screenshot: Increased amount of logs after migration to containerd屏幕截图：迁移到 containerd 后日志量增加
Is it possible somehow to configure the logging severity level of containerd at GKE?是否有可能以某种方式在 GKE 上配置 containerd 的日志记录严重性级别？ Or what could be the way of reducing the amount of such logs?或者有什么方法可以减少此类日志的数量？
The Kubernetes cluster is running on the latest available at GKE version (from v1.21) 1.21.11-gke.1900 atm. Kubernetes 集群在 GKE 版本（从 v1.21 起）1.21.11-gke.1900 atm 的最新版本上运行。
I would appreciate any assistance in these regards.我将不胜感激在这些方面的任何帮助。
1 个解决方案
解决方案1
0 2022-08-02 09:50:02
GKE container logs are removed when their host Pod is removed and when there is out of space or they will be replaced with new logs on a regular basis and cluster logs are removed after one hour. GKE 容器日志会在其主机 Pod 被移除且空间不足时被移除，或者它们将定期被新日志替换，并且集群日志会在一小时后被移除。 You can control the collection of your application logs .您可以控制应用程序日志的收集。 Please check this document for the best practices.请查看此文档以了解最佳实践。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.