Setting up dedicated nodes for your Informix deployment
You can dedicate one or more worker nodes to your Informix service. The nodes are then used exclusively by the database containers or pods.
About this task
Red Hat® OpenShift® uses the concepts of taint and toleration to dedicate a service such as Informix® to particular nodes. Nodes are tainted and labeled:
- A taint prevents pods from being deployed on a tainted node.
- A label allows for a pod with a matching toleration to be treated as an exception.
Taint and toleration work together to provide node exclusivity to deploying Informix on particular nodes
Perform these steps for each worker node that you plan to dedicate to the database deployment. The steps use Red Hat OpenShift CLI commands. The node_name is the name of a worker node on which you plan to host Informix.
Considerations for software-defined storage (such as OpenShift Container Storage)
When storage and compute share the same nodes, some additional considerations apply so that Informix and software-defined storage can be properly scheduled on the same worker nodes. See the optional Step 2 below.