Kubernetes Job Monitoring

The following table describes important issues when a Kubernetes job is running in the Monitoring domain:

Feature

Description

Status Monitoring

The Kubernetes job in Control-M monitors the status of the job entity in Kubernetes until it ends running in one or more Application pods.

Normally, tracking continues even if the Agent pod is restarted, provided that the restart occurred after the job entity was created in Kubernetes.

In rare cases, if the restart occurred before the job entity was created in Kubernetes, its status cannot be monitored, and the Control-M job fails. If this occurs, check whether each of the Application pods ran and whether it completed successfully, and proceed as follows:

  • If the Application pod ran and completed successfully, set Control-M job completion status to OK.
  • If the Application pod ran and failed, remove the job entity in Kubernetes and rerun the Control-M job.
  • If the Application pod did not run, rerun the Control-M job. 

Kill a Job

Control-M enables you to kill the job while it is still running. This also kills the pod(s) in Kubernetes.

For more information, see Job Management.