**已关闭。**此问题为not about programming or software development。目前不接受回答。

此问题似乎与a specific programming problem, a software algorithm, or software tools primarily used by programmers无关。如果您认为此问题与another Stack Exchange site的主题相关，可以发表评论，说明在何处可以回答此问题。
上个月就关门了。
Improve this question的
我使用openshift命令创建了一个作业;

oc create job <my-job> --from=cronjob/<my-cronjob>

字符串
，但它不会自动创建一个pod。我找不到这里缺少了什么。可能需要改变my-cronjob的yaml的东西。所以这里是yaml;

kind: CronJob
apiVersion: batch/v1
metadata:
  annotations:
    meta.helm.sh/release-name: xxx
    meta.helm.sh/release-namespace: xxx
  resourceVersion: '7504720716'
  name: my-cronjob
  uid: xxxx
  creationTimestamp: '2023-02-17T14:27:25Z'
  generation: 3
  managedFields:
    - manager: helm
      operation: Update
      apiVersion: batch/v1
      time: '2023-04-19T09:06:08Z'
      fieldsType: FieldsV1
      fieldsV1:
        'f:metadata':
          'f:annotations':
            .: {}
            'f:meta.helm.sh/release-name': {}
            'f:meta.helm.sh/release-namespace': {}
          'f:labels':
            .: {}
            'f:app.kubernetes.io/managed-by': {}
        'f:spec':
          'f:concurrencyPolicy': {}
          'f:failedJobsHistoryLimit': {}
          'f:jobTemplate':
            'f:spec':
              'f:template':
                'f:spec':
                  'f:containers':
                    'k:{"name":"my-job"}':
                      .: {}
                      'f:envFrom': {}
                      'f:image': {}
                      'f:imagePullPolicy': {}
                      'f:name': {}
                      'f:resources':
                        .: {}
                        'f:limits':
                          .: {}
                          'f:cpu': {}
                          'f:ephemeral-storage': {}
                          'f:memory': {}
                        'f:requests':
                          .: {}
                          'f:cpu': {}
                          'f:ephemeral-storage': {}
                          'f:memory': {}
                      'f:terminationMessagePath': {}
                      'f:terminationMessagePolicy': {}
                  'f:dnsPolicy': {}
                  'f:restartPolicy': {}
                  'f:schedulerName': {}
                  'f:securityContext': {}
                  'f:terminationGracePeriodSeconds': {}
          'f:schedule': {}
          'f:successfulJobsHistoryLimit': {}
          'f:suspend': {}
    - manager: kube-controller-manager
      operation: Update
      apiVersion: batch/v1
      time: '2023-08-16T08:05:04Z'
      fieldsType: FieldsV1
      fieldsV1:
        'f:status':
          'f:lastScheduleTime': {}
      subresource: status
    - manager: Mozilla
      operation: Update
      apiVersion: batch/v1
      time: '2023-12-05T09:10:40Z'
      fieldsType: FieldsV1
      fieldsV1:
        'f:spec':
          'f:jobTemplate':
            'f:spec':
              'f:template':
                'f:spec':
                  'f:containers':
                    'k:{"name":"my-job"}':
                      'f:command': {}
  namespace: ifxbertsearch-staging
  labels:
    app.kubernetes.io/managed-by: Helm
spec:
  schedule: 0 1 * * *
  concurrencyPolicy: Forbid
  suspend: true
  jobTemplate:
    metadata:
      creationTimestamp: null
    spec:
      template:
        metadata:
          creationTimestamp: null
        spec:
          containers:
            - name: my-job
              image: >-
                xxx
              command:
                - python
                - main.py
                - '49'
              envFrom:
                - configMapRef:
                    name: env-variables
              resources:
                limits:
                  cpu: '4'
                  ephemeral-storage: 10Mi
                  memory: 5Gi
                requests:
                  cpu: '2'
                  ephemeral-storage: 10Mi
                  memory: 3Gi
              terminationMessagePath: /dev/termination-log
              terminationMessagePolicy: File
              imagePullPolicy: Always
          restartPolicy: Never
          terminationGracePeriodSeconds: 30
          dnsPolicy: ClusterFirst
          securityContext: {}
          schedulerName: default-scheduler
  successfulJobsHistoryLimit: 3
  failedJobsHistoryLimit: 1
status: {}

型
所以我需要弄清楚，为什么cronjob没有创建作业将在其上工作的pod。