The Secure Agent can either wait to shut down the cluster after an idle timeout, or the agent can perform a smart shutdown that is based on historical data.

The Secure Agent also stops the cluster in the following situations:

The cluster fails to start or fails to stop.
The agent cannot reach the Kubernetes API server within a certain amount of time.

After the Secure Agent stops the cluster, the agent verifies that all cluster resources are deleted, except for some Informatica binaries that remain in the staging location in the

infa_rpm.tar

file. The binaries are required in order to run jobs on the cluster, and the file is reused the next time that the agent starts the cluster.

The agent deletes the

infa_rpm.tar

file in the following situations:

You clear the runtime environment in the
advanced configuration
.
You associate the
advanced configuration
with a different runtime environment.
The agent process on the Secure Agent machine shuts down.

The agent restarts the cluster when a developer runs another job in the same runtime environment.