ip-range-start or control-port must be configured in the bundle. Pacemaker will create an implicit ocf:pacemaker:remote resource for the connection, launch Pacemaker Remote within the container, and monitor and manage the primitive resource via Pacemaker Remote.
masters greater than zero.
Note
options attribute.
storage-mapping element to map a file on the host as /etc/pacemaker/pcmk-init.env in the container. Pacemaker Remote will parse this file as a shell-like format, with variables set as NAME=VALUE, ignoring blank lines and comments starting with "#".
Important
primitive, Pacemaker on all cluster nodes must be able to contact Pacemaker Remote inside the bundle’s containers.
network should not be set to "none" with a primitive).
ip-range-start. Any firewall must allow access from all cluster nodes to the control-port on the container IPs.
network to "host"), a unique control-port should be specified for each bundle. Any firewall must allow access from all cluster nodes to the control-port on all cluster and remote node IPs.