About Suspending Management of a TimesTenClassic Object

The TimesTen Operator examines the state of the TimesTen instances and the databases associated with each TimesTenClassic object. It takes actions to repair anything that is broken. You may have a situation in which you want to manually perform maintenance operations. In such a situation, you do not want the TimesTen Operator to interfere and attempt to perform repair operations.

You could stop the TimesTen Operator by deleting the timesten-operator Deployment. This action prevents the Operator from interfering. See Revert to Manual Control. However, if you have more than one TimesTenClassic object and you delete the TimesTen Operator, this interferes with the management of all the TimesTenClassic objects, when perhaps only one of them needs manual intervention.

You can direct the TimesTen Operator to take no action for one or more TimesTenClassic objects by specifying the .spec.ttspec.stopManaging datum in the TimesTenClassic object's definition. The TimesTen Operator examines the value of .spec.ttspec.stopManaging and if it has changed since the last time the Operator examined it, the Operator changes the state of the TimesTenClassic object to ManualInterventionRequired. This causes the Operator to no longer examine the status of the TimesTen Pods, the containers, the instances, and the databases associated with the TimesTenClassic object. The Operator takes no action on the object or its Pods.

When you want the TimesTen Operator to manage the TimesTenClassic object again, you use the .spec.ttspec.reexamine datum. These actions enable you to perform manual operations on TimesTen without deleting the TimesTen Operator.

For an example, see Suspend Management.