Updating the WebLogic Kubernetes Operator Add-on

You can update how you want the version of the WebLogic Kubernetes Operator add-on to be updated, and you can update the number of replicas and the resource usage limits as described in Installing the WebLogic Kubernetes Operator Add-on.

Add-on update remains in Accepted state and waits until the cluster is in the Active state.

Using the Compute Web UI

  1. On the dashboard, select Containers / View Kubernetes Clusters (OKE).

  2. In the clusters list, select the name of the cluster for which you want to update an add-on.

  3. On the cluster details page, scroll to the Resources section, and select Add-ons.

  4. In the add-ons list, for the WLS Operator add-on, select the Actions menu, and select the Edit Add-on option.

  5. In the dialog that opens, configure the add-on.

    1. Add-on version updates: Select how you want the version of the add-on to be updated as newer versions of the add-on become available and as newer versions of Kubernetes are supported for OKE: either Automatic Updates or Choose a Version. See descriptions of these options in Version Updates for Add-ons.

      If you select Choose a Version, then you must select a version from the list.

    2. Add-on configuration: Optionally select a configuration parameter and a value for that parameter. See the descriptions in Configuration Parameters for the WebLogic Kubernetes Operator Add-on.

      To set another configuration parameter, select the Add configuration button.

  6. Select the Save Changes button in the dialog.

Using the OCI CLI

  1. Get the OCID of the cluster for which you want to update an add-on: oci ce cluster list

  2. Run the update add-on command.

    Syntax:

    $ oci ce cluster update-addon --cluster-id cluster_OCID \
    --addon-name addon_name

    Example:

    $ oci ce cluster update-addon --cluster-id ocid1.cluster.unique_ID \
    --addon-name WeblogicKubernetesOperator \
    --configurations file://./weblogic-cfg.json --force
    
    {
     "opc-work-request-id": "ocid1.cccworkrequest.unique_ID"
    }