File Watcher job configuration in Kubernetes environment - AutoSys

Products

• Autosys Workload Automation
• Workload Automation Agent

Issue/Introduction

This article provides instructions for configuring AutoSys File Watcher (FW) jobs within a Kubernetes (K8s) or OpenShift environment.

Environment

• AutoSys Workload Automation AE 12.x / 24.1
• Workload Automation Agent for Kubernetes Plugin 12.1 or higher

Resolution

Instructions

To monitor files within a Kubernetes cluster, utilize the Workload Automation Agent for Kubernetes Plugin. This allows the AutoSys Agent to interface with the cluster and its storage.

Deployment Options

There are two primary methods for monitoring files in K8s:

1. External Agent: Install the agent outside the Kubernetes Pod to monitor Persistent Volumes (PV) accessible to the host.
2. Internal Agent (Pod): Install the agent directly inside a Pod to monitor the local container file system.

Note: When deploying the agent in a container, it runs only as the deployed user. Alternate user execution (owner) is not supported in this configuration.

Prerequisites

Ensure the Kubernetes Plugin is installed and configured. For detailed steps, see Install the Plugin Extension for K8s.

Example File Watcher JIL

Use the following JIL template to define a File Watcher job for a Kubernetes-integrated machine:

jil

insert_job: FW-K8S
job_type: FW
machine: <K8S_AGENT_MACHINE>
owner: <DEPLOYED_USER>
date_conditions: 0
condition: s(PREVIOUS_JOB)
application: K8S_MONITORING
watch_file: "/path/to/persistent/volume/file"
watch_interval: 10

Additional Information

• For general K8s job definitions, refer to Kubernetes Job
• To speak with a customer representative or a Support Engineer, see Contact Support - Broadcom Software.  Scroll to the bottom of the page and click on your respective region.