...
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
...
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.
opaque
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.
...