Upgrading Services on the Management Cluster

The management cluster runs the services that provide the administrative and user-facing functionality of the appliance. Commands are provided to upgrade these outside of the full rack upgrade workflow, in case the circumstances require it.

Upgrading the Kubernetes Cluster

The Kubernetes container orchestration environment upgrade is decoupled from the host OS. With a single command, all Kubernetes packages, such as kubeadm, kubectl and kubelet, are upgraded on the three management nodes and all the compute nodes. For dependency reasons, Kubernetes must be upgraded after the management node host OS. Note that this upgrade does not include the microservices running within the Kubernetes cluster.

Using the Service Web UI

  1. In the navigation menu, go to the Maintenance section and click Upgrade Plan. This provides an overview of current and target component versions.

  2. Click Upgrade & Patching to display the Upgrade Jobs page.

  3. In the top-right corner of the Upgrade Jobs page, click Create Upgrade or Patch.

    The Create Request window appears. Choose Upgrade as the Request Type.

  4. Select the appropriate upgrade request type: Upgrade Rack.

  5. Fill out the upgrade request parameters:

    • Action: To perform the upgrade or patch operation, select Apply.

    • Type: For upgrade, select ISO. The ULN option applies to patching.

    • Component: For the Kubernetes cluster, select Kubernetes.

    • Qualifier: This parameter is not required when upgrading the Kubernetes cluster.

    • Verify Only: Enable this option to run the operation in verification only mode.

    • Force: Enable this option to force the operation. Use only when instructed by Oracle.

  6. Click Create Request.

    The new upgrade request appears in the Upgrade Jobs table.

  7. Confirm that the upgrade process is completed without errors.

    For more information, see Browse the Job Framework.

Using the Service CLI

  1. Enter the upgrade command.

    PCA-ADMIN> upgradeRack type=ISO action=APPLY component=KUBERNETES
JobId: 6b796a4a-89ac-4fcc-a5c7-efb0eb9dceac
Data: Service request has been submitted. Upgrade Job Id = 1737620352375-kubernetes-660839 Upgrade Request Id = UWS-dd3cdaf7-5302-4b57-8858-caff924c2dcf

  2. Use the job ID to check the status of the upgrade process.

    PCA-ADMIN> getUpgradeJob upgradeJobId=1737620352375-kubernetes-660839
Data:
  Upgrade Request Id = UWS-dd3cdaf7-5302-4b57-8858-caff924c2dcf
  Name = kubernetes
  Pid = 660839
  Host = pcamn01
  Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_kubernetes_cluster_2025_01_23-08.19.12.log
  Arguments = {"component_names":null,"diagnostics":false,"display_task_plan":false,"dry_run_tasks":false,"expected_iso_checksum":null,"fail_halt":false,"fail_upgrade":null,"image_location":null,"online_upgrade":null,"precheck_status":false,"repo_config_override":null,"result_override":null,"task_time":0,"test_run":false,"upgrade":false,"upgrade_to":null,"user_uln_base_url":null,"verify_only":false,"host_ip":null,"log_level":null,"switch_type":null,"epld_image_location":null,"checksum":null,"composition_id":null,"request_id":"UWS-dd3cdaf7-5302-4b57-8858-caff924c2dcf","uln":null,"patch":"false"}
  Status = Passed
  Execution Time(sec) = 249
[...]

  3. Confirm that the upgrade process is completed without errors.

    For more information, see Browse the Job Framework.

Upgrading the Microservices

The microservices upgrade covers both the internal services of the platform layer, and the administrative and user-level services exposed through the infrastructure services layer. The containerized microservices have their own separate upgrade mechanism. A service is upgraded if a new Helm deployment chart and container image are found in the ISO content. When a new deployment chart is detected during the upgrade process, the pods running the services are restarted with the new container image.

Note:

In specific circumstances it is possible to upgrade certain platform services individually, by adding an optional JSON string to the command. This option should not be used unless Oracle provides explicit instructions to do so.

Using the Service Web UI

  1. In the navigation menu, go to the Maintenance section and click Upgrade Plan. This provides an overview of current and target component versions.

  2. Click Upgrade & Patching to display the Upgrade Jobs page.

  3. In the top-right corner of the Upgrade Jobs page, click Create Upgrade or Patch.

    The Create Request window appears. Choose Upgrade as the Request Type.

  4. Select the appropriate upgrade request type: Upgrade Rack.

  5. Fill out the upgrade request parameters:

    • Action: To perform the upgrade or patch operation, select Apply.

    • Type: For upgrade, select ISO. The ULN option applies to patching.

    • Component: For the platform and infrastructure microservices, select Platform.

    • Qualifier: This parameter is not required when upgrading the microservices.

    • Verify Only: Enable this option to run the operation in verification only mode.

    • Force: Enable this option to force the operation. Use only when instructed by Oracle.

  6. Click Create Request.

    The new upgrade request appears in the Upgrade Jobs table.

  7. Confirm that the upgrade process is completed without errors.

    For more information, see Browse the Job Framework.

Using the Service CLI

  1. Enter the upgrade command.

    PCA-ADMIN> upgradeRack type=ISO action=APPLY component=PLATFORM
JobId: 30116885-57e3-4737-b6a2-9f429f084fb5
Data: Service request has been submitted. Upgrade Job Id = 1737620370636-platform-666460 Upgrade Request Id = UWS-26312768-855d-4f31-90b9-cbb0559d1d7f

  2. Use the job ID to check the status of the upgrade process.

    PCA-ADMIN> getUpgradeJob upgradeJobId=1737620370636-platform-666460
Data:
  Upgrade Request Id = UWS-26312768-855d-4f31-90b9-cbb0559d1d7f
  Name = platform
  Pid = 666460
  Host = pcamn01
  Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_platform_services_2025_01_23-08.19.30.log
  Arguments = {"component_names":null,"diagnostics":false,"display_task_plan":false,"dry_run_tasks":false,"expected_iso_checksum":null,"fail_halt":false,"fail_upgrade":null,"image_location":null,"online_upgrade":null,"precheck_status":false,"repo_config_override":null,"result_override":null,"task_time":0,"test_run":false,"upgrade":false,"upgrade_to":null,"user_uln_base_url":null,"verify_only":false,"host_ip":null,"log_level":null,"switch_type":null,"epld_image_location":null,"checksum":null,"composition_id":null,"request_id":"UWS-26312768-855d-4f31-90b9-cbb0559d1d7f","uln":null,"patch":"false"}
  Status = Passed
  Execution Time(sec) = 536
[...]

  3. Confirm that the upgrade process is completed without errors.

    For more information, see Browse the Job Framework.