Skip to content

Latest commit

 

History

History
239 lines (218 loc) · 6.44 KB

File metadata and controls

239 lines (218 loc) · 6.44 KB

Subscribing to the {VirtProductName} catalog by using the CLI

Before you install {VirtProductName}, you must subscribe to the {VirtProductName} catalog. Subscribing gives the {CNVNamespace} namespace access to the {VirtProductName} Operators.

To subscribe, configure Namespace, OperatorGroup, and Subscription objects by applying a single manifest to your cluster.

Prerequisites
  • Install {product-title} {product-version} on your cluster.

  • Install the {oc-first}.

  • Log in as a user with cluster-admin privileges.

Procedure
  1. Create the required Namespace, OperatorGroup, and Subscription objects for {VirtProductName} by running the following command:

    $ oc apply -f <filename>.yaml
Verification

You must verify that the subscription creation was successful before you can proceed with installing {VirtProductName}.

  1. Check that the ClusterServiceVersion (CSV) object was created successfully. Run the following command and verify the output:

    $ oc get csv -n {CNVNamespace}

    If the CSV was created successfully, the output shows an entry that contains a NAME value of kubevirt-hyperconverged-operator-*, a DISPLAY value of {VirtProductName}, and a PHASE value of Succeeded, as shown in the following example output:

    Example output:

    NAME                                       DISPLAY                    VERSION   REPLACES                                   PHASE
    kubevirt-hyperconverged-operator.v{HCOVersion}   {VirtProductName}   {HCOVersion}    kubevirt-hyperconverged-operator.v{HCOVersionPrev}   Succeeded
  2. Check that the HyperConverged custom resource (CR) has the correct version. Run the following command and verify the output:

    $ oc get {HCOCliKind} -n {CNVNamespace} kubevirt-hyperconverged -o json | jq .status.versions

    Example output:

    {
    "name": "operator",
    "version": "{HCOVersion}"
    }
  3. Verify the HyperConverged CR conditions. Run the following command and check the output:

    $ oc get {HCOCliKind} kubevirt-hyperconverged -n {CNVNamespace} -o json | jq -r '.status.conditions[] | {type,status}'

    Example output:

    {
      "type": "ReconcileComplete",
      "status": "True"
    }
    {
      "type": "Available",
      "status": "True"
    }
    {
      "type": "Progressing",
      "status": "False"
    }
    {
      "type": "Degraded",
      "status": "False"
    }
    {
      "type": "Upgradeable",
      "status": "True"
    }