oc-ex-ipfailover - Man Page

Install an IP failover group to a set of nodes


oc ex ipfailover [Options]


Configure or view IP Failover configuration

This command helps to setup an IP failover configuration for the cluster. An administrator can configure IP failover on an entire cluster or on a subset of nodes (as defined via a labeled selector).

If an IP failover configuration does not exist with the given name, the --create flag can be passed to create a deployment configuration that will provide IP failover capability. If you are running in production, it is recommended that the labeled selector for the nodes matches at least 2 nodes to ensure you have failover protection, and that you provide a --replicas= <n> value that matches the number of nodes for the given labeled selector.



Run the check-script at this interval (seconds)


Run this script at the check-interval to verify service is OK


If true, create the configuration if it does not exist.


If true, show the result of the operation without performing it.


The image to base this IP failover configurator on - ${component} will be replaced based on --type.

-i,  --interface=""

Network interface bound by VRRP to use for the set of virtual IP ranges/addresses specified.


Add a rule to this iptables chain to accept multicast packets if no rule exists. When iptables-chain is empty do not change iptables.


If true, attempt to use the latest images instead of the current release


Run this script when state changes.

-o,  --output=""

Output results as yaml or json instead of executing, or use name for succint output (resource/name).


The preferred API versions of the output objects

--preemption-strategy="preempt_delay 300"

Normlly VRRP will preempt a lower priority machine when a higher priority one comes online. 'nopreempt' allows the lower priority machine to maintain its MASTER status. The default 'preempt_delay 300' causes MASTER to switch after 5 min.

-r,  --replicas=1

The replication factor of this IP failover configuration; commonly 2 when high availability is desired. Please ensure this matches the number of nodes that satisfy the selector (or default selector) specified.

-l,  --selector="ipfailover=<name>"

Selector (label query) to filter nodes on.


Name of the service account to use to run the ipfailover pod.

-a,  --show-all=false

When printing, show all resources (default hide terminated pods.)


When printing, show all labels as the last column (default hide labels column)


If non-empty, sort list types using this field specification.  The field specification is expressed as a JSONPath expression (e.g. '{.metadata.name}'). The field in the API resource specified by this JSONPath expression must be an integer or a string.


Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [ ⟨http://golang.org/pkg/text/template/#pkg-overview⟩].


The type of IP failover configurator to use.


Number of groups to create for VRRP, if not set a group will be created for each virtual ip given on --virtual-ips.


A set of virtual IP ranges and/or addresses that the routers bind and serve on and provide IP failover capability for.


Offset to use for setting ids of VRRP instances (default offset is 0). This allows multiple ipfailover instances to run within the same cluster.

-w,  --watch-port=80

Port to monitor or watch for resource availability.

Options Inherited from Parent Commands


Allow a SignatureVerifier to use keys which are technically non-compliant with RFC6962.


log to standard error as well as files


Max number of application metrics to store (per container)


Username to impersonate for the operation


Group to impersonate for the operation, this flag can be repeated to specify multiple groups.


Path to the file containing Azure container registry configuration information.


Comma-separated list of files to check for boot-id. Use the first one that exists.


Default HTTP cache directory


Path to a cert file for the certificate authority


Path to a client certificate file for TLS


Path to a client key file for TLS


CIDRs opened in GCE firewall for LB traffic proxy health checks


The name of the kubeconfig cluster to use


location of the container hints file


containerd endpoint


The name of the kubeconfig context to use


Indicates the tolerationSeconds of the toleration for notReady:NoExecute that is added by default to every pod that does not already have such a toleration.


Indicates the tolerationSeconds of the toleration for unreachable:NoExecute that is added by default to every pod that does not already have such a toleration.


docker endpoint


use TLS to connect to docker


path to trusted CA


path to client certificate


path to private key


a comma-separated list of environment variable keys that needs to be collected for docker containers


Only report docker containers in addition to root stats


DEPRECATED: docker root is read from docker info (this is a fallback, default: /var/lib/docker)


Whether to enable cpu load reader


Max length of time for which to store events (per type). Value is a comma separated list of key values, where the keys are event types (e.g.: creation, oom) or "default" and the value is a duration. Default is applied to all non-specified event types


Max number of events to store (per type). Value is a comma separated list of key values, where the keys are event types (e.g.: creation, oom) or "default" and the value is an integer. Default is applied to all non-specified event types


Interval between global housekeepings


Interval between container housekeepings


If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure


Path to the kubeconfig file to use for CLI requests.


Maximum number of seconds between log flushes


when logging hits line file:N, emit a stack trace


Whether to log the usage of the cAdvisor container


If non-empty, write log files in this directory


log to standard error instead of files


Comma-separated list of files to check for machine-id. Use the first one that exists.


Require server version to match client version

-n,  --namespace=""

If present, the namespace scope for this CLI request


The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.

-s,  --server=""

The address and port of the Kubernetes API server


logs at or above this threshold go to stderr


Writes in the storage driver will be buffered for this duration, and committed to the non memory backends as a single transaction


database name


database host:port


database password


use secure connection with database


table name


database username


Bearer token for authentication to the API server


The name of the kubeconfig user to use

-v,  --v=0

log level for V logs


Print version information and quit


comma-separated list of pattern=N settings for file-filtered logging


  # Check the default IP failover configuration ("ipfailover"):
  oc ex ipfailover
  # See what the IP failover configuration would look like if it is created:
  oc ex ipfailover -o json
  # Create an IP failover configuration if it does not already exist:
  oc ex ipfailover ipf --virtual-ips="" --create
  # Create an IP failover configuration on a selection of nodes labeled
  # "router=us-west-ha" (on 4 nodes with 7 virtual IPs monitoring a service
  # listening on port 80, such as the router process).
  oc ex ipfailover ipfailover --selector="router=us-west-ha" --virtual-ips=",," --watch-port=80 --replicas=4 --create
  # Use a different IP failover config image and see the configuration:
  oc ex ipfailover ipf-alt --selector="hagroup=us-west-ha" --virtual-ips="" -o yaml --images=myrepo/myipfailover:mytag

See Also



June 2016, Ported from the Kubernetes man-doc generator

Referenced By


Openshift CLI User Manuals June 2016