Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Run Preflight and Postflight Checks

SUMMARY Learn about CN2 preflight and postflight checks.

Preflight checks allow you to verify that your cluster nodes can support CN2. The checks test for resource capacity, kernel compability, network reachability, and other infrastructure requirements. You run preflight checks prior to installing CN2.

Postflight checks allow you to verify that your CN2 installation is working properly. The checks test for status, pod-to-pod communication, API server reachability, and other basic functions. You run postflight checks after installing CN2. CN2 supports postflight checks starting in release 22.2.

Run Preflight and Postflight Checks in Release 22.4

We provide a custom controller that performs preflight and postflight checks on all cluster nodes. The controller runs the checks defined in custom resources that we provide. You create and run the controller in the same way you run other Kubernetes applications.

  1. Locate the contrail-tools/contrail-readiness directory from the downloaded CN2 Manifests and Tools package.
  2. If you haven't already done so, ensure you've populated the manifests with your repository login credentials. See Configure Repository Credentials for one way to do this.
  3. Apply the ContrailReadiness custom resource definitions.
  4. Create the ConfigMap from the deployer manifest that you want to apply to this cluster. Name the ConfigMap deployer-yaml.
    where <path_to_deployer_manifest> is the full path to the deployer manifest that you want to apply.
  5. Patch the ConfigMap with the registry information.
  6. Create the ContrailReadiness controller.

    Wait for the controller to come up.

  7. Run the checks.
    • To run the preflight checks:You run preflight checks after you create the cluster but before you install CN2.
    • To run the postflight checks:You run postflight checks after you install CN2.

      In a multi-cluster deployment, run postflight checks from the central cluster only.

  8. Read the preflight and postflight check results as applicable.

    Address any errors before proceeding.


    The preflight and postflight checks do not automatically rerun after you've fixed any errors. The output will continue to show errors even after you've fixed them.