Warning: file_get_contents(/data/phpspider/zhask/data//catemap/7/kubernetes/5.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Kubernetes Cronjob会立即触发作业,即使超过了时间_Kubernetes_Kubernetes Cronjob - Fatal编程技术网

Kubernetes Cronjob会立即触发作业,即使超过了时间

Kubernetes Cronjob会立即触发作业,即使超过了时间,kubernetes,kubernetes-cronjob,Kubernetes,Kubernetes Cronjob,我有Kubernetes的工作,每天早上5点开始。今天我想把它改成早上6点。我现在的时间是上午10点 当我将时间从早上5点修改到早上6点时,我注意到Kubernetes Cronjob会立即触发作业,即使我当前的时间是上午10点 这是什么原因?是否有任何参数可用于启用/禁用此行为 apiVersion: batch/v1beta1 kind: CronJob metadata: name: do-not-want-to-reveal namespace: default spec:

我有Kubernetes的工作,每天早上5点开始。今天我想把它改成早上6点。我现在的时间是上午10点

当我将时间从早上5点修改到早上6点时,我注意到Kubernetes Cronjob会立即触发作业,即使我当前的时间是上午10点

这是什么原因?是否有任何参数可用于启用/禁用此行为

apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: do-not-want-to-reveal
  namespace: default
spec:
  concurrencyPolicy: Forbid
  failedJobsHistoryLimit: 2
  jobTemplate:
    metadata:
      creationTimestamp: null
    spec:
      backoffLimit: 1
      template:
        metadata:
          creationTimestamp: null
        spec:
          containers:
          - image: myrepo/myimage:mytag
            imagePullPolicy: Always
            name: do-not-want-to-reveal
            resources: {}
            terminationMessagePath: /dev/termination-log
            terminationMessagePolicy: File
          dnsPolicy: ClusterFirst
          restartPolicy: OnFailure
          schedulerName: default-scheduler
          securityContext: {}
          serviceAccount: myjob-sa
          serviceAccountName: myjob-sa
          terminationGracePeriodSeconds: 30
  schedule: 00 5 * * *
  successfulJobsHistoryLimit: 2
  suspend: false


这是
CronJob
的已知行为。它为“错过的”计划创建作业。看看这个公开问题-

没有参数来启用或禁用它,因为这不是预期的行为。删除并重新创建CronJob。我删除了该作业
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:11:31Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.9", GitCommit:"16236ce91790d4c75b79f6ce96841db1c843e7d2", GitTreeState:"clean", BuildDate:"2019-03-25T06:30:48Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}