Oracle Cloud Infrastructure Documentation

Install the Add-on for an Existing Cluster

On Compute Cloud@Customer, you can install an add-on for an existing cluster.

Outside Certificates

To install the WebLogic Kubernetes Operator add-on on an existing cluster that is using a certificate that's not the certificate that's specific to the Compute Cloud@Customer, perform the following steps on the cluster where you want to install the add-on:

  1. Perform certificate rotation. See Certificate Authority Bundles.

  2. Perform any updates to node pool configuration that are required, such as boot volume size change or shape changes, for example.

  3. Cycle worker nodes as described in Node Cycling an OKE Node Pool.

  4. Enable or install the WebLogic Kubernetes Operator add-on as described in this procedure.

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

    2. In the clusters list, select the name of the cluster in which you want to install the add-on.

    3. On the cluster details page, under Resources, select Add-ons.

    4. In the add-ons list, for the WLS Operator add-on, select the Actions menu (An image of the three dot icon.), and select Edit. On the WLS Operator dialog box, select the Enable Add-on WLS Operator checkbox to do one of the following:

      • Deploy and enable the WebLogic Kubernetes Operator add-on if the add-on hasn't been enabled on this cluster before.

      • Enable the WebLogic Kubernetes Operator add-on if the add-on was previously deployed for this cluster but is currently disabled.

    5. Configure the add-on.

      1. Add-on version updates: Select the method you want to use to update the version of the add-on as newer versions of the add-on become available and as newer versions of OKE 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: Select Add configuration to select a configuration option and specify a value. See the descriptions in Configuration Parameters for the WebLogic Kubernetes Operator Add-on.

        To set another configuration parameter, select Add configuration.

    6. Select Save Changes.

  • Use the oci ce cluster install-addon command and required parameters to install the add-on.

    oci ce cluster install-addon --cluster-id <cluster_OCID> --addon-name <addon_name> [OPTIONS]

    Procedure

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

    2. Construct an argument for the --configurations option.

      Use the --configurations option to specify one or more key/value pairs in JSON format to pass as arguments to the cluster add-on.

      For descriptions of the configuration parameters, see Configuration Parameters for the WebLogic Kubernetes Operator Add-on.

      The inline syntax is shown in the example in the next step of this procedure. You might find it easier to use a file:

      --configurations file://./weblogic-cfg.json

      The format and content of the configuration file is given by the following command:

      $ oci ce cluster install-addon --generate-param-json-input configurations
[
  {
    "key": "string",
    "value": "string"
  },
  {
    "key": "string",
    "value": "string"
  }
]

      In the following example, both requests and limits are specified because the memory limit is lower than the default memory request. If a limit is less than the corresponding request, the deployment fails.

      Double quotation marks within a value must be escaped with a single backslash.

      [
    {
        "key": "weblogic-operator.ContainerResources",
        "value": "{
            \"requests\": {
                \"cpu\": \"250m\",
                \"memory\": \"150Mi\"
            },
            \"limits\": {
                \"cpu\": \"500m\",
                \"memory\": \"200Mi\"
            }
        }"
    },
    {
        "key": "weblogic-operator-webhook.ContainerResources",
        "value": "{
            \"limits\": {
                \"cpu\": \"150m\",
                \"memory\": \"200Mi\"
            }
        }"
    },
    {
        "key": "numOfReplicas",
        "value": "1"
    }
]

    3. Run the install add-on command.

      Syntax:

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

      Example:

      If you specify a version, you're selecting the Stay on the specific version option for updating the add-on version, described in Version Updates for Add-ons. If you set the version to null, or you omit the --version-parameterconflict option, you're selecting the default behavior Automatically update the add-on.

      Note that the version string must begin with a v.

      Enclose the configurations argument in single quotation marks so that you don't need to escape every double quotation mark in the argument value.

      $ oci ce cluster install-addon --cluster-id ocid1.cluster.unique_ID \
--addon-name WeblogicKubernetesOperator --version-parameterconflict "v4.2.13" \
--configurations '[{"key": "weblogic-operator.ContainerResources", "value": "{\"limits\": {\"cpu\": \"500m\", \"memory\": \"512Mi\"}}"}, \
{"key": "weblogic-operator-webhook.ContainerResources", "value": "{\"limits\": {\"cpu\": \"150m\", \"memory\": \"200Mi\"}}"}]'

{
 "opc-work-request-id": "ocid1.cccworkrequest.unique_ID"
}

  • Use the InstallAddon operation to install an add-on.

    For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.