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]
SUSE Telco Cloud Documentation|Setting up the management cluster

Part V Setting up the management cluster

  • 27 Introduction
  • The management cluster is the part of SUSE Telco Cloud that is used to manage the provision and lifecycle of the runtime stacks. From a technical point of view, the management cluster contains the following components:

  • 28 Steps to set up the management cluster
  • The following steps are necessary to set up the management cluster (using a single node):

  • 29 Image preparation for connected environments
  • Edge Image Builder is used to create the image for the management cluster, in this document we cover the minimal configuration necessary to set up the management cluster.

  • 30 Image preparation for air-gap environments
  • This section describes how to prepare the image for air-gap environments showing only the differences from the previous sections. The following changes to the previous section (Image preparation for connected environments (Chapter 29, Image preparation for connected environments)) are required to pr…

  • 31 Image creation
  • Once the directory structure is prepared following the previous sections (for both, connected and air-gap scenarios), run the following command to build the image:

  • 32 Provision the management cluster
  • The previous image contains all components explained above, and it can be used to provision the management cluster using a virtual machine or a bare-metal server (using the virtual-media feature).

  • 33 Dual-stack considerations and configuration
  • The examples shown in the previous sections provide guidance and examples on how to set up a single-stack IPv4 management cluster. Such a management cluster is independent of the operational status of downstream clusters, which can be individually configured to operate in either IPv4/IPv6 single-sta…