Product SiteDocumentation Site

10.4.3. rkt Properties

Before configuring a rkt bundle in Pacemaker, the user must install rkt and supply a fully configured container image on every node allowed to run the bundle.
Pacemaker will create an implicit ocf:heartbeat:rkt resource to manage a bundle’s rkt container. The user must ensure that resource agent is installed on every node allowed to run the bundle.

Table 10.14. Properties of a Bundle’s rkt Element

Field Default Description
image
Container image tag (required)
replicas
Value of masters if that is positive, else 1
A positive integer specifying the number of container instances to launch
replicas-per-host
1
A positive integer specifying the number of container instances allowed to run on a single node
masters
0
A non-negative integer that, if positive, indicates that the containerized service should be treated as a multistate service, with this many replicas allowed to run the service in the master role
network
If specified, this will be passed to rkt run as the network setting for the rkt container.
run-command
/usr/sbin/pacemaker_remoted if bundle contains a primitive, otherwise none
This command will be run inside the container when launching it ("PID 1"). If the bundle contains a primitive, this command must start pacemaker_remoted (but could, for example, be a script that does other stuff, too).
options
Extra command-line options to pass to rkt run