Validating your deployment

The operator reconciliation loop can take some time. Verify that the operator container is running.

Before you begin

Make sure that you complete the task Applying the custom resource manually or have your custom resource applied through the Content Cortex prerequisite scripts, and then follow the steps that are mentioned in the procedure.

Procedure

  1. Open the operator log to view the progress of the installation.
    # <Must set> Set your project name here 
    export project_name=$your_project_name
    
    # <Must set> Set target operator name here 
    export operator_name=ibm-content-operator
    
    operator_pod_name=$(kubectl get pod|grep $operator_name | awk '{print $1}')
    kubectl exec -i $operator_pod_name -n $project_name -- /bin/bash -c 'cat /tmp/ansible-operator/runner/fncm.ibm.com/v1/*/*/*/artifacts/latest/stdout' > operator-ansible.log 
  2. Look for the status field of each component by running an kubectl get command. The status shows the current state of the component during deployment, and shows the conditions or reasons for failure, if any.
    kubectl get FNCMCluster fncmdeploy -o jsonpath='{.status.components}'
    where, <metadata.name> is the component name from:
    status:
      components:
        ban_initialization:
        ban_verification:
        cmis:
        content_initialization:
        content_verification:
        cpe:
        css:
        extshare:
        graphql:
        navigator:
        prereq:
        tm:
    Each component status has four different states:
    • NotInstalled
    • NotReady
    • Ready
    • Failed
  3. If you chose to initialize and verify your Content Platform Engine and Content Navigator deployment, through the operator, you can check whether this was completed successfully.
    Note: You can enable initialization and verification through the operator by adding the following to the custom resource.
    shared_configuration:
      sc_content_initialization: true
      sc_content_verification: true 
    
    initialize_configuration:
      ...
    
    verify_configuration:
      ...
    1. Check the fncmdeploy-initialization-config configmap to check that each component is true.
      kubectl get cm fncmdeploy-initialization-config -o jsonpath='{.data}'
      {
      "cpe_initialized":"True",
      "cpe_os_number":"1",
      "css_initialized":"True",
      "nav_initialized":"True"
      }
    2. Check the fncmdeploy-verification-config configmap to check that each component is True.
      kubectl get cm fncmdeploy-verification-config -o jsonpath='{.data}'
      {
      "cmis_verified":"True",
      "cpe_verified":"True",
      "css_verified":"True",
      "nav_verified":"True"
      }

What to do next

Some capabilities need you to follow post-deployment steps. For more information, see Completing post-deployment tasks.