Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Overview

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

  1. Create a Kubernetes Namespace

  2. Kubernetes Secret

  4. https://cloudsphere.atlassian.net/wiki/x/fYMGAw

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

Storage class – allow Kubernetes blueprints to create volumes in the specific class automatically.
Note: Storage Class is not bound to a namespace.

  • Login to the HyperCloud™ Platform with your credentials  Click on Services Orchestration Tab  Click on Containers tab  Click on the Kubernetes Cluster already provisioned

  • Click on Action Button  Click on New Storage Class

    • Enter a Name for the storage Class: Standard

    • Click Save

  • No labels

© 2020 CloudSphere