Overview
Once you’ve deployed a Managed Kubernetes Cluster, you’ll need to configure the following:
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:
Login to your HyperCloud™ Platform (HCP) account.
Click Service Orchestration and navigate to Containers > Click open your provisioned Kubernetes Cluster.
Click Action > Click New Namespace.
Enter a Name for your Namespace in the New Namespace dialog.
Click Save.
Kubernetes Secret
Kubernetes Secrets let you store and manage sensitive information, such as passwords, OAuth tokens, and ssh keys. Storing confidential information in a Secret is safer and more flexible than putting it verbatim in a Pod definition or in a container image. See Secrets design document for more information. Secret can be credentials/ hidden configuration which can be referenced by containers during runtime
Note: Kubernetes Secrets must be created within a namespace. This secret can be used by deployments in the current namespace only.
Refer the Kubernetes Secret Overview for more details
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 Secret
Enter a name: app1-secret1
Select Namespace: production
From the Type Drop-down: Select the Secrete type
Click Save to create a secret in the namespace
To view the secret, click on the Kubernetes Namespace tab Click on the same space which was selected to create the secret.