Skip to content

Creating a Cluster

This topic summarizes the workflow to create and deploy a cluster, followed by details. After your cloud credentials have been added to Megaport ONE, you can deploy a cluster.

To begin, the basic steps are:

  1. Create a cluster.

    • Configure provider connection details - Megaport ONE provides seamless access to hybrid and multicloud environments: Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform, Equinix Bare Metal, Oracle Cloud, and DigitalOcean. Megaport ONE automates connections by predicting and applying best practice configurations. You deploy a Kubernetes cluster to any Megaport ONE provider that your account credentials allow.
    • Configure a node pool - A cluster unifies a node grouping of individual virtual or physical machines deployed in the same region into a pool. The nodes in a cluster are the machines that run the end-user applications.
  2. Deploy the cluster.

  3. Add containerized applications to the cluster. For details, see Applications.

To create a new cluster

  1. Log in to the Megaport ONE Portal.
  2. Choose Compute > Clusters.

  3. Click Deploy New Cluster.

    Create Cluster

  4. Enter a unique cluster name, using a minimum of 5 lowercase alphanumeric characters and hyphens and a maximum of 38.

  5. Select a cloud, colocation, or edge provider from the Provider drop-down list.
    The list includes available providers based on your account credentials.

  6. Select a data center location for the cluster from the Location drop-down list.

    The list includes available data center locations based on your account.

    A GPU ENABLED flag appears next to locations with GPUSpecialized processors that provide computing power to process many pieces of data simultaneously, accelerating the workload and increasing performance. capabilities. Use GPUs for high-performance acceleration of a specific Kubernetes workload.

  7. A Kubernetes version is preselected for you based on available versions for your provider and location.

    The default selection is the best choice if you don’t have a specific need for an earlier version.

The next step is to configure provider connection details. Configuration details vary by provider.

To configure provider connection details

  • The configuration options reflect the required settings for your provider.

    This information connects the cluster compute resources with the service resource provider. The cluster can connect to any consumable endpoint, whether that is on-premises, public cloud, or bare metal.

    • Amazon Web Services - Select at least two AWS subnets for the cluster.
    • DigitalOcean - No additional configuration details needed.
    • Equinix - Select your Equinix Metal project SSHSecure Shell protocol. key from the drop-down list. This is a public project key previously added to your Equinix Metal account. This key is specific to your single project.
    • Google Cloud Platform - No additional configuration details needed.
    • Microsoft Azure - No additional configuration details needed.
    • Oracle Cloud - Under Oracle Configuration, provide these details to connect to your preconfigured Oracle Cloud Infrastructure. The fields are prepopulated based on your configuration. All fields are required:

      • Virtual Cloud Network (VCN) Oracle ID - Select the VCN in which your cluster will reside.
      • Load Balancer Subnets - Select the subnets where the load balancers will be provisioned.
      • Kubernetes Master Endpoint Subnet Oracle ID - Select the OCID of the Kubernetes control plane node endpoint subnet. You access the Kubernetes API on the cluster control plane through this endpoint, which is hosted in a subnet of the VCN the cluster resides in. Your Kubernetes endpoint will reside in this subnet.
      • Node Pool Subnet ID - Select the ID of the subnet used to process the node pool within a cluster.
      • Node Pool Availability Domain - Select the regional node pool availability domainOne or more data centers located in a region. that the Kubernetes endpoint will reside in.

The next step is to configure the node machine compute type that will run the underlying cluster.

Configure Node Pool

The machine type definition includes the CPU and memory specifications. Use the filter to limit the number of compute options returned by the provider.

Filters provide a way to find a GPU-enabled provider for high-performance acceleration of a specific Kubernetes workload. Select a resource from the GPU capabilities drop-down list to narrow your search.

All nodes in a pool group must be the same machine type.

For details on GPU resources, see Discover GPU Resources.

To configure a node pool

  1. Select the number of CPU nodes and the minimum RAM.

  2. Select whether the node pool will have GPU capabilities, indicated by the location description.

  3. Select the machine type.

    A verification appears when the machine type is available in the selected location.

    A GPU type is automatically selected based on the machine type.

  4. Select the number of nodes in the pool.

  5. Enable or disable autoscaling.
    Autoscaling adjusts the size of a Kubernetes cluster based on metrics such as CPU and RAM to meet the current needs. After enabling autoscaling, set the minimum and maximum number of nodes in the pool.

  6. Select Yes to use the Kubernetes DashboardAn official web-based user interface (UI) designed especially for Kubernetes clusters to give Kubernetes administrators complete control of the clusters. to control the cluster in Megaport ONE using the browser.

Tip

You can also access the Kubernetes Dashboard by clicking the cluster name on the Megaport ONE dashboard and then selecting Actions > Launch Kubernetes Dashboard.

Deploying a cluster

After creating a cluster, the next step is to deploy it. The cluster will be provisioned on the account connected with the Megaport ONE instance. Deploying a cluster connects it to the provider and provisions the cluster.

To deploy a cluster

  1. Click Deploy Cluster.

    Review Cluster Config

  2. Review the configuration.

  3. Click Confirm to deploy the cluster or Cancel to change settings.

The cluster starts communicating with the provider and proceeds through the deployment process, which can take approximately 10 to 25 minutes, depending on traffic on the underlying provider. Click the status indicator to view the cluster deployment states.

Cluster Deployment States

After a successful cluster deployment, it can be controlled completely from the Megaport ONE platform.

Troubleshooting

If the deployment state of a cluster indicates an issue, the cluster could not be deployed. The status indicator reports any provisioning errors and where in the provisioning process the error occurred.

Cluster Deployment Error

To see status error details

  • Click the state indicator and click More Information.

The cause of the failure is listed to pinpoint the problem.

Next steps

  • Once you have deployed a Kubernetes cluster, it can receive cloud-native applications with Helm charts. For details, see Applications.

  • You can set alerts to monitor the cluster. For details, see Configuring a Cluster.


Last update: 2022-10-14