Skip to content

Upgrade notes 1.x to 2.x#

Pelagia 1.x must be upgraded to version 2.x. For Pelagia release notes, refer to Pelagia Releases.

Breaking changes#

  • The default Ceph release is set to Ceph Tentacle.

  • Rook is upgraded to v1.19. For upgrade details, see Rook upgrade.

  • Ceph CSI operator is enabled by default.

    Previously, the CSI driver was automatically configured by Rook. Now, the CSI operator has been factored out of Rook to run independently to manage the Ceph-CSI driver. For details, see Ceph CSI operator README.

  • CephDeployment API is refactored and now uses pure Rook API for several fields. For details, see CephDeployment resource. CephDeployment is automatically migrated to a new API during upgrade, no manual steps are required.

  • After changing the CephDeployment API, Pelagia supports multiple ObjectStore (Ceph RGW) instances. Consider the following changes:

    • The RGW name of StorageClass created by default has changed to <object-store-name>-bucket.

      The previously created StorageClass for a single ObjectStore (RGW) instance named rgw-storage-class is still present in the environment for backward compatibility. All existing buckets are not affected, but for newly created ones a new StorageClass must be used. Removal of StorageClass with old names must be done manually.

    • The self-signed ObjectStore (RGW) SSL certificate is regenerated and renamed from rgw-ssl-certificate to <object-store-name>-ssl-certificate.

      If the current description of ObjectStore (RGW) provides certificates in the SSLCert or SSLCertInRef section (for details, see CephDeployment CephRGW params), these certificates will continue to be used and will be moved to the corresponding new sections. The SSLCert and SSLCertInRef sections will be removed. Specifying plain SSL certificates directly in the CephDeployment spec is now prohibited, use a secret reference instead.

    • The multisite realm cannot provide plain realm keys in the spec anymore, for security reasons. You must create the corresponding secret as described in Rook documentation: Getting Realm Access Key and Secret Key. For existing environments, no actions are required.

    • Serving RGW DNS names must be now set using the ObjectStore (RGW) spec definition. This enables a more flexible configuration. For details, see Rook documentation: Hosting Settings. Existing environments do not require pre-upgrade steps, but consider switching to the new flow after upgrade.

  • Gateway API support.

    Ingress NGINX controller is deprecated, but continues operating after Pelagia upgrade. However, its support will be removed in following release. Therefore, consider switching to the Gateway API after upgrade. For details, see the post-upgrade steps below.

Pre-upgrade steps#

No specific pre-upgrade steps are required for the 1.x → 2.x upgrade.

Post-upgrade steps#

Complete the following steps after upgrading Pelagia to 2.x. For description of the changes that require these steps, see the Breaking changes section above.

  1. Optional. Manually remove the existing StorageClass for the ObjectStore (RGW) instances named rgw-storage-class.
  2. Switch to setting RGW DNS names using the ObjectStore (RGW) spec definition. This enables a more flexible configuration. For details, see Rook documentation: Hosting Settings.

  3. Switch to the Gateway API due to the deprecation of the Ingress NGINX controller. The Gateway object and Controller must be configured separately.

    To configure Pelagia after switching to the Gateway API, use the corresponding Gateway object. For details, see Configuration Reference and CephDeployment resource.