blocks|key|1430609|text|我认为您应该写到stdout和stderr，而不是写到文件中，以便能够使用kubectl+log。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1430610|entityMap^0|11|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I think you should write to stdout and stderr not to a file to be able to use <code>kubectl log</code>

blocks|key|1430635|text|您可以附加容器启动脚本以包含日志。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1430636|类似于run.sh+&尾巴-f+/var/log/cronlog|1430637|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

you can append the container startup script to include the logs

something like run.sh &amp;&amp; tail -f /var/log/cronlog

blocks|key|2061389|text|首先，为什么不使用工作创建CronJob控制器|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2061390|我认为你应该利用Kubernetes，并利用乔布斯，如果他们应该运行，而不是普通的cronjob。这将消耗更少的资源，并且您将快速检查cron作业是否失败。|2061391|此外，正如以前的答案中已经提到的，您需要将消息/日志发送到stdout。|2061392|下面是一个CronJob的示例，它发送date并打印Hello+from+the+Kubernetes+cluster到stdout，而日志可以由kubectl+logs+job/<JOB_NAME>访问。|style|CODE|2061393|apiVersion:+batch/v1beta1
kind:+CronJob
metadata:
++name:+hello
++namespace:+default
spec:
++schedule:+"*+*+*+*+*"+#+run+every+minute
++startingDeadlineSeconds:+10+#+if+a+job+hasn't+starting+in+this+many+seconds,+skip
++concurrencyPolicy:+Forbid+#+either+allow%7Cforbid%7Creplace
++successfulJobsHistoryLimit:+3+#+how+many+completed+jobs+should+be
++jobTemplate:
++++spec:
++++++template:
++++++++spec:
++++++++++containers:
++++++++++++-+name:+hello
++++++++++++++image:+busybox
++++++++++++++args:
++++++++++++++++-+/bin/sh
++++++++++++++++-+-c
++++++++++++++++-+date;+echo+Hello+from+the+Kubernetes+cluster
++++++++++restartPolicy:+OnFailure|code-block|syntax|javascript|2061394|我希望这能为你提供一些概况。|2061395|entityMap|0|LINK|mutability|MUTABLE|url|https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/|1|https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/^0|9|2|0|D|A|1|0|0|0|J|4|Q|X|21|R|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]|$A|16|B|17|1|18]]|C|$]]|$1|D|3|E|5|6|7|19|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1A|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|1B|8|@$A|1C|B|1D|J|K]|$A|1E|B|1F|J|K]|$A|1G|B|1H|J|K]]|9|@]|C|$]]|$1|L|3|M|5|N|7|1I|8|@]|9|@]|C|$O|P]]|$1|Q|3|R|5|6|7|1J|8|@]|9|@]|C|$]]|$1|S|3|-4|5|6|7|1K|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|11]]]]

First why you don't create <a href="https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/" rel="nofollow noreferrer">Jobs</a> using a <a href="https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/" rel="nofollow noreferrer">CronJob Controller</a>?

I think you should take advantage of using Kubernetes and make use of Jobs if they are supposed to run instead of plain cronjob. This will consume less resources and you will quickly check if cronjob failed.

Also as it was already mentioned in previous answers, you need to send messages/logs to stdout 

Here is an example of a CronJob that does send <code>date</code> and prints <code>Hello from the Kubernetes cluster</code> to stdout, and logs can be accessed by <code>kubectl logs job/&lt;JOB_NAME&gt;</code>

<pre><code>apiVersion: batch/v1beta1
kind: CronJob
metadata:
 name: hello
 namespace: default
spec:
 schedule: "* * * * *" # run every minute
 startingDeadlineSeconds: 10 # if a job hasn't starting in this many seconds, skip
 concurrencyPolicy: Forbid # either allow|forbid|replace
 successfulJobsHistoryLimit: 3 # how many completed jobs should be
 jobTemplate:
 spec:
 template:
 spec:
 containers:
 - name: hello
 image: busybox
 args:
 - /bin/sh
 - -c
 - date; echo Hello from the Kubernetes cluster
 restartPolicy: OnFailure
</code></pre>

I hope this provide a bit of overview for You.

Currently I have a Kubernetes pod that is running a cron job. The cron job writes to a log file at <code>/var/log/cronlog</code>. However, when I type <code>kubectl log my-pod-name</code>, the contents of <code>/var/log/cronlog</code> is not included.

How do I make it so that the contents of <code>/var/log/cronlog</code> is included with the output of <code>kubectl log my-pod-name</code>?

How to make Kubernetes manage my pods log files?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

目前，我有一个库伯内特斯吊舱，正在运行一个cron的工作。cron作业写入/var/log/cronlog的日志文件。但是，当我键入kubectl log my-pod-name时，不包含/var/log/cronlog的内容。如何使/var/log/cronlog的内容包含在kubectl log my-pod-na...

问如何使Kubernetes管理我的荚日志文件？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使Kubernetes管理我的荚日志文件？EN