Skip to main content

Configure Managed Kubernetes Clusters

Permanently deleted user
  • Updated

Overview

Once you’ve deployed a Managed Kubernetes Cluster, you’ll need to configure the following:

  1. Create a Kubernetes Namespace

  2. Kubernetes Secret

  3. Kubernetes Storage Class

  4. Kubernetes Persistent Volumes

Create a Kubernetes Namespace

Kubernetes lets you create multiple virtual clusters called Namespaces on a single physical cluster. Namespaces let you distribute your cluster resources across multiple users by creating resource quotas. Kubernetes Namespace – acts as a workspace with optional quotas and limits for each pod (containers). Creating a Namespace lets you support environments with multiple users (10 or more users) who are spread across many teams, projects, or regions. Namespaces provide a scope for names so that you can add unique resource-names within a Namespace. You’ll need to separately add these resource-names to each Namespace as these cannot be added on a global level.

You cannot nest Namespaces inside one another and you can have only one Kubernetes resource for a Namespace. You don’t have to create multiple namespaces for segregating slightly varying resources. Example: Different versions of the software within the same Namespace.
In such cases, you can add labels for various versions to differentiate between your resources.

 

Kubernetes best practice

  • It is recommended that you create a dedicated namespace for your applications.

  • Avoid using the default namespace.

To create a Namespace:

  1. Login to your HyperCloud™ Platform (HCP) account.

  2. Click Service Orchestration and navigate to Containers > Click open your provisioned Kubernetes Cluster.

  3. Click Action > Click New Namespace.

  4. Enter a Name for your Namespace in the New Namespace dialog.

  5. Click Save.

Kubernetes Secret

Kubernetes Secret lets you store and manage your passwords, OAuth tokens, and SSH Keys. It is recommended that you store your credentials in a Secret than defining it in a Pod or a container image. Your Secret credentials are hidden configurations and can be referenced by containers during runtime.

 

Notes

  • You can create a Kubernetes Secret within a namespace.

  • Once you create a Secret within a namespace, it can be accessed only by the deployments within the current namespace.

  • Refer to the Kubernetes Secret Overview, for more details

To create a Kubernetes Secret on your HCP portal:

  1. Login to your HCP Portal account.

  2. Click Service Orchestration and navigate to Containers > Click open your provisioned Kubernetes Cluster > Click Action > Click New Secret.

  3. Enter these details in the New Secret dialog:

    1. Enter a Name for your Kubernetes Secret.

    2. From the Namespace drop-down list, select a namespace for which you want to create the Secret.

    3. Select the Secret Type from the drop-down list.

  4. Click Save.

  5. To view your newly created Kubernetes Secret:

    1. Click Kubernetes Namespace.

    2. Click open the Namespace where you created the Kubernetes Secret.

Kubernetes Storage Class

Kubernetes StorageClass lets administrators define classes for the storages they offer. Storage classes can be of the following type:

  • Quality-of-service levels

  • Backup policies

  • Arbitrary policies defined by the cluster administrators.

You can automatically create volumes for a Storage Class using Kubernetes Blueprints.

 

Note
Storage Classes are not bound to Namespaces.

To create a Storage Class:

  1. Login to your HCP portal Account.

  2. Click Service Orchestration and navigate to Containers > Click open your provisioned Kubernetes Cluster > Click Action > Click New Storage Class.

  3. Enter a Name for your storage Class.

  4. Click Save.

Kubernetes Persistent Volumes

Persistent Volumes (PV) are pre-created volumes that can be attached to containers during runtime. PV is a piece of storage in a Cluster provisioned by an Administrator or dynamically provisioned using storage classes. In other words, a PV is a resource in the cluster and is a volume plugin like Volumes. However, the lifecycle of a PV is independent of any individual Pod using PV. The PersistentVolume subsystem:

  • Abstracts the details of how storage is provided and consumed and,

  • Provides an API for users and administrators.

To create a new Persistent Volume:

  1. Login to your HCP portal account.

  2. Click Service Orchestration and navigate to Containers > Click open your provisioned Kubernetes Cluster > Click Action > Click New.

  3. Enter these details in the New Persistent Volume dialog:

    1. Enter a name for your Persistent Volume Name.

    2. Select the Storage Class from the drop-down list.

    3. Select the Reclaim Policy from the drop-down list.

    4. Select one of these Disk options to create a PV:

      • New: enter a Volume Size in GB

      • Existing: you’ll need to provide a URI for an existing volume

  4. Click Save.

Comments

0 comments

Please sign in to leave a comment.