...
Once you’ve deployed a Managed Kubernetes Cluster, you’ll need to configure the following:
Create a Kubernetes 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 Secret lets you store and manage sensitive information, such as your passwords, OAuth tokens, and ssh keys. Storing confidential information SSH Keys. It is recommended that you store your credentials in a Secret is safer and more flexible than putting defining it verbatim in a a Pod definition or in a a container image. See Secrets design document for more information.Secret can be credentials/ hidden configuration which Your Secret credentials are hidden configurations and can be referenced by containers during runtime
Note: Kubernetes Secrets must be created .
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:
Login to
...
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
...
your HCP Portal account.
Click Service Orchestration and navigate to Containers > Click open your provisioned Kubernetes Cluster > Click Action > Click New Secret.
Enter these details in the New Secret dialog:
Enter a Name for your Kubernetes Secret.
From the Namespace drop-down list, select a namespace for which you want to create the Secret.
Select the Secret Type from the drop-down list.
Click Save.
To view your newly created Kubernetes Secret:
Click Kubernetes Namespace.
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:
Login to your HCP portal Account.
Click Service Orchestration and navigate to Containers > Click open your provisioned Kubernetes Cluster > Click Action > Click New Storage Class.
Enter a Name for your storage Class.
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:
Login to your HCP portal account.
Click Service Orchestration and navigate to Containers > Click open your provisioned Kubernetes Cluster > Click Action > Click New.
Enter these details in the New Persistent Volume dialog:
Enter a name for your Persistent Volume Name.
Select the Storage Class from the drop-down list.
Select the Reclaim Policy from the drop-down list.
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
Click Save.