This is a draft document that was built and uploaded automatically. It may document beta software and be incomplete or even incorrect. Use this document at your own risk.

Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Administration Guide › Upgrading SUSE CaaS Platform
ContentsContents
Administration Guide
  2. 1 About This Guide
  3. 2 Cluster Management
  4. 3 Software Management
  5. 4 Cluster Updates
  6. 5 Upgrading SUSE CaaS Platform
  7. 6 Security
  8. 7 Logging
  9. 8 Monitoring
  10. 9 Storage
  11. 10 Integration
  12. 11 GPU-Dependent Workloads
  13. 12 Cluster Disaster Recovery
  14. 13 Backup and Restore with Velero
  15. 14 Miscellaneous
  16. 15 Troubleshooting
  17. 16 Glossary
  18. A Contributors
  19. B GNU Licenses
Navigation←→
Administration Guide › Upgrading SUSE CaaS Platform
Top
←→
Applies to SUSE CaaS Platform 4.5.2

5 Upgrading SUSE CaaS Platform

5.1 Migration to SUSE CaaS Platform 4.5

5.1 Migration to SUSE CaaS Platform 4.5

Warning
Warning: Sequential Upgrade Required

For a successful migration, make sure you are at the latest 4.2 version before migrating your cluster and management workstation to SUSE CaaS Platform 4.5.

For this, please follow the upgrade guide to update all your cluster nodes and management workstation to the latest base OS updates and SUSE CaaS Platform updates. Refer to: https://documentation.suse.com/suse-caasp/4.5/html/caasp-admin/_cluster_updates.html

5.1.1 Updating the operating system

  1. The node should be able to communicate with the servers for SUSE Customer Center or Repository Mirroring Tool (RMT). Other migration scenarios are covered in the SLES upgrade guide.

    Note
    Note

    In order to reconnect your system to the registration server, run:

    SUSEConnect -r <your SCC key> SUSEConnect -p sle-module-containers/15.1/x86_64 -r <your SCC key>

  2. You also need the new zypper migration plugin. This plugin is used to migrate the node itself to the latest version of SUSE CaaS Platform, such as updating the repositories to the new ones, and calling zypper dup. This plugin is provided by the zypper-migration-plugin package. Therefore, you need to install the zypper-migration-plugin package:

    zypper -n in zypper-migration-plugin

  3. Then, run the newly installed zypper-migration plugin (on the management node first, then on the rest of the nodes):

    zypper migration
    Note
    Note

    If you want migration to progress non-interactive, you can add the flags: --non-interactive --auto-agree-with-licenses

  4. Check that all required repositories are enabled again and have the correct version. Run:

    zypper lr -uE

    Verify that all repositories on the following list are present and enabled:

    Note
    Note

    The actual Aliases might be different from the ones shown here if they were configured differently during the initial installation of SUSE Linux Enterprise.

    The URIs will have long UUID strings (update?<UUID>,product?<UUID>) attached to them. The UUIDs identify your personal licensed product or update repositories. These have been omitted from this output example.

    AliasURI

    Basesystem_Module_15_SP2_x86_64:SLE-Module-Basesystem15-SP2-Pool

    https://updates.suse.com/SUSE/Products/SLE-Module-Basesystem/15-SP2/x86_64/

    Basesystem_Module_15_SP2_x86_64:SLE-Module-Basesystem15-SP2-Updates

    https://updates.suse.com/SUSE/Updates/SLE-Module-Basesystem/15-SP2/x86_64/

    Containers_Module_15_SP2_x86_64:SLE-Module-Containers15-SP2-Pool

    https://updates.suse.com/SUSE/Products/SLE-Module-Containers/15-SP2/x86_64/

    Containers_Module_15_SP2_x86_64:SLE-Module-Containers15-SP2-Updates

    https://updates.suse.com/SUSE/Updates/SLE-Module-Containers/15-SP2/x86_64/

    Python_2_Module_15_SP2_x86_64:SLE-Module-Python2-15-SP2-Pool

    https://updates.suse.com/SUSE/Products/SLE-Module-Python2/15-SP2/x86_64/

    Python_2_Module_15_SP2_x86_64:SLE-Module-Python2-15-SP2-Updates

    https://updates.suse.com/SUSE/Updates/SLE-Module-Python2/15-SP2/x86_64/

    SUSE_CaaS_Platform_4.5_x86_64:SUSE-CAASP-4.5-Pool

    https://updates.suse.com/SUSE/Products/SUSE-CAASP/4.5/x86_64/

    SUSE_CaaS_Platform_4.5_x86_64:SUSE-CAASP-4.5-Updates

    https://updates.suse.com/SUSE/Updates/SUSE-CAASP/4.5/x86_64/

    SUSE_Linux_Enterprise_Server_15_SP2_x86_64:SLE-Product-SLES15-SP2-Pool

    https://updates.suse.com/SUSE/Products/SLE-Product-SLES/15-SP2/x86_64/

    SUSE_Linux_Enterprise_Server_15_SP2_x86_64:SLE-Product-SLES15-SP2-Updates

    https://updates.suse.com/SUSE/Updates/SLE-Product-SLES/15-SP2/x86_64/

    Server_Applications_Module_15_SP2_x86_64:SLE-Module-Server-Applications15-SP2-Pool

    https://updates.suse.com/SUSE/Products/SLE-Module-Server-Applications/15-SP2/x86_64/

    Server_Applications_Module_15_SP2_x86_64:SLE-Module-Server-Applications15-SP2-Updates

    https://updates.suse.com/SUSE/Updates/SLE-Module-Server-Applications/15-SP2/x86_64/

  5. Check if skuba was indeed upgraded for 4.5:

    skuba version
    Important
    Important

    The version must be >= skuba-2.1. skuba 2 corresponds to SUSE CaaS Platform 4.5, while skuba 1.0-1.4 corresponds to SUSE CaaS Platform 4.

5.1.2 Upgrade the cluster

  1. And now run the skuba cluster upgrade commands as it’s done below.

    • First, check if there are any addons or components to upgrade before you upgrade the nodes:

      skuba cluster upgrade plan
skuba addon upgrade plan
skuba addon upgrade apply

    • Then, check with cluster status if all nodes have the same Kubernetes version (which must be 1.17.x):

      skuba cluster status
      Note
      Note

      If not all nodes are properly upgraded to the same Kubernetes version, then the ones with an older Kubernetes version must be upgraded before attempting a migration. Refer to the update documentation of the previous version to bring all nodes to the latest update state.

    • Once all nodes have the same Kubernetes version, you must upgrade the CRI-O config:

      skuba cluster upgrade localconfig

    • Run skuba node upgrade:

      skuba node upgrade apply --user sles --sudo --target <IP of the node you’ve migrated>

    • Before repeating the same cycle with the rest of the nodes, please make sure that all the components of the kubernetes stack are running on the freshly upgraded node. You can do this with the following command:

      kubectl get all -n kube-system

  2. Now repeat the above steps for all nodes to bring them to the upgraded state.

  3. After upgrading all the nodes, make sure you run another addon upgrade across the cluster:

    skuba addon upgrade plan
skuba addon upgrade apply

After following all these instructions you should be running SUSE CaaS Platform 4.5. Refer to the release notes for further information on the new features that this release brings. Enjoy!

→Chapter 6 Security←Chapter 4 Cluster Updates
Print this page

© 2021 SUSE