-
Overview
-
Practical sheets
-
- Add a NetBackup User
- Backing up a VM
- Backup : Agent-Level B&R via NSS for IAAS offer
- Checking Backup Prerequisites
- Daily Reporting
- Deleting a VM Backup
- Identifying Your Backup Master Server
- NetBackup Portal
- NSS Home Page
- NSS Swagger APIs
- Restoring a VM
- Troubleshooting Netbackup Errors
- VM Agent Restoration Mode
-
-
- Aucun article
-
-
- Aucun article
-
-
-
- Backup : Agent-Level B&R via NSS for IAAS offer
- Backup : Create VCOD Backup
- Backup : Netbackup Agent Installation for Linux
- Backup : Netbackup Agent Installation for Windows
- Backup : Overall Design for VCOD Offer
- Backup : User's Guide for VCOD Offer
- NSX-T : Configuring a Distributed Firewall
- NSX-T : Create VPN Ipsec
- NSX-T : Creation of T1
- NSX-T : DNAT configuration
- NSX-T : How to configure a Gateway Firewall
- NSX-T : SNAT configuration
- NSX-T: Create and Configure a Geneve Overlay Segment
- NSX-T: How to configure an IPSEC solution
- vCenter : Clone a VM
- VCenter : Create a new VM
- VCenter : Create a snapshot of a VM
- VCenter : Reset cloudadmin password
- VCenter : Storage Vmotion on a VM
- VCenter : Upgrade Vmware tools on a VM
-
-
Q & A
-
Services
-
-
- Aucun article
-
- Aucun article
-
- Aucun article
-
- Aucun article
-
- Aucun article
-
- Aucun article
-
- Aucun article
-
-
-
- Aucun article
-
- Aucun article
-
- Aucun article
-
-
-
- Aucun article
-
Update your hosted OpenShift cluster
This guide explains how to perform an automatic update of your OpenShift cluster using the CAVControlPlane resource available.
Voici la traduction en anglais du texte présent sur votre capture :
1. Overview of the CAVControlPlane resource
- The CAVControlPlane resource is automatically created for your cluster when it starts. It is essential for the management and operation of your cluster.
- This resource is unique and must always exist. Its name is always local.
- Do not delete the CAVControlPlane resource. If it disappears and you cannot recreate it, please contact support immediately.
To check the status of your control plane, retrieve the Kubernetes resource CAVControlPlane (or cavcp for short):
bash
$ kubectl get cavcontrolplane
NAME VERSION UPDATED ISO UPLOADED
local 4.19.19 True True
Voici la traduction en anglais du contenu affiché (texte des sections et commandes comprises).
2. How to update your cluster
To update your cluster, you need to modify the spec.version field of the CAVControlPlane resource to the desired OpenShift/Kubernetes version.
Step-by-step instructions
a. Locate the CAVControlPlane resource
The resource should be named local in your cluster.
bash
$ kubectl get cavcontrolplane local -o yaml
b. Modify the spec.version field
Update the spec.version field with the target version. For example, to upgrade to version 4.19.0:
yaml
apiVersion: containers.orange-business.com/v1
kind: CAVControlPlane
metadata:
name: local
spec:
version: 4.19.19
You can edit the resource directly:
bash
$ kubectl edit cavcontrolplane local
Or apply a manifest:
bash
$ kubectl apply -f updated-cavcontrolplane.yaml
c. The operator will detect the change
The CAV Hypershift operator will automatically orchestrate the update process for your control plane and node pools.
d. Monitor the update process
You can track the update status by checking the status conditions of the resource:
bash
$ kubectl describe cavcontrolplane local
Look for status updates and conditions indicating progress or completion of the update.
For more details, describe your OpenShift resources:
bash
$ kubectl describe clusterversion version
$ kubectl get clusteroperator
Voici la traduction en anglais du contenu affiché :
3. Troubleshooting & Support
- If the CAVControlPlane resource is missing and you cannot recreate it, contact support.
- For any issue during the update process, check the resource status to find error messages.
4. Warnings & Best Practices
- Only set the spec.version field with officially supported versions.
- Always monitor the update process and make sure it completes successfully before making any other changes.
- During the update, each node will restart one by one, which may temporarily affect cluster availability.