Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. https://cloudsphere.atlassian.net/wiki/x/ogEIAw

  2. https://cloudsphere.atlassian.net/wiki/x/44IHAw

  3. https://cloudsphere.atlassian.net/wiki/x/cIMGAw

  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.

...

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

...