Kubernetes, the foundation of Cloud Z CP, supports multiple virtual clusters supported by the same physical cluster. These virtual clusters are called namespaces.

For more details, see Namespaces

• View namespace
  • View in card format
  • View as list
• Namespace Secret Management
  • Go to the Secret Management screen
  • Add Secret
  • Secret Inquiry
  • Delete Secret
  • Secret Search
  • Secret management using kubectl CLI

View namespace

Existing namespaces can be viewed in card or list format.

You can view resource usage such as CPU Request, Memory Request, CPU Limit, and Memory Limit by namespace.

You can go to the dashboard where you can see the current status of the namespace and more detailed information about the namespace.

View in card format

If you want to view the namespaces intuitively, you can view them in card format.

To view namespaces as cards:

1. Select Namespaces from the side menu.
2. Click the button.

카드형에서는 네임스페이스 별로 다음의 정보를 볼 수 있습니다.

• Namespace Name: A unique value to distinguish the Namespace. Clicking the link allows you to change the details of the Namespace.
• Creation Date: The date and time the namespace was created.
• Number of users: The number of users with permissions to the namespace.
• situation
  • Green (Active): The namespace is in use.
  • Gray (Terminating): The namespace is being deleted and cannot be used for new Objects.
• Resource Utilization
  • (The value actually being used / the value set in Resource Quotas) is displayed.
  • If it is below 50%, it is displayed in green, if it is above 50%, it is displayed in blue, and if it is above 80%, it is displayed in red.
  • The following four Resources are displayed:
    • CPU Request: The percentage of the Namespace set to Resource Quotas.
    • CPU Limit: 
    • Memory Request: 
    • Memory Limit: 
• Namespace Management
  • Go to Dashboard screen: Go to the Dashboard screen where you can view more detailed information about the Namespace.
  • Delete Namespace: Deletes a Namespace.

View as list

If you want to see more information about a namespace at once, you can view it in list form.

To view the namespaces as a list:

1. Select Namespaces from the side menu.
2. Click the button.
   

In list form, you can see the following information:

• Namespace Name: Click on the link to see detailed information.
• Resource Utilization
  • (The value actually being used / the value set in Resource Quotas) is displayed.
  • If it is below 50%, it is displayed in green, if it is above 50%, it is displayed in blue, and if it is above 80%, it is displayed in red.
  • The following four Resources are displayed:
    • CPU Request: Based on the CPU Request value set in Resource Quotas.
    • CPU Limit: Based on the CPU Limit value set in Resource Quotas.
    • Memory Request: Based on the Memory Request value set in Resource Quotas.
    • Memory Limit: Based on the Memory Limit value set in Resource Quotas.
• Number of users: The number of users with permissions to the Namespace.
• Status: The current status of the Namespace.
  • Active: The namespace is in use.
  • Terminating: The namespace is being deleted and cannot be used for new Objects.
• Creation Date: The date and time the namespace was created.
• management
  • Delete: Deletes a Namespace.

Namespace Secret Management

Secrets are meant to hold sensitive information such as passwords, OAuth tokens, and ssh keys. Putting this information in a Secret is more secure and flexible than putting it directly in a Pod definition or Docker Image.

The Cloud Z CP console allows you to manage the following types of Secrets that are commonly used across multiple applications in a namespace:

(Secrets for each application are managed separately in the respective project.)

• Docker Registry : 특정 Docker Registry에서 이미지를 가져오기 위한 서버 및 인증 정보를 포함합니다.
• TLS: Manage certificate and key files used for HTTPS setup.

For more details, see Secrets 

Go to the Secret Management screen

1. Select Namespaces from the side menu.
2. Click the link associated with the Namespace name.
3. When the Namespace management screen appears, click the Secret tab.

Add Secret

1. Click the (Add Secret) button at the top right of the Secret list.
2. When the Add Secret pop-up appears, enter the information appropriate to the type and click the Register button.

Field Description

• Docker Registry
  • docker-server (required): Docker Registry server information. Example: registry.cloudzcp.io
  • docker-username (required): Docker login user ID
  • docker-password (required): Docker login user password
  • docker-email : Docker login user email
• TLS
  • certificate : 
  • key : 

Secret Inquiry

1. Clicking on the Secret tab of a namespace will display a list of registered Secrets.
2. Clicking on a Secret Name will display a pop-up with details about the Secret.
3. For TLS type, you can click to download the file.

Delete Secret

1. In the Secret list, click in the Manage column of the Secret you want to delete.
2. Enter the Secret Name you want to delete for confirmation and click the Delete button.

Secret Search

You can search the registered Secret list by Secret Name.

1. Enter your search term in the search field at the top right of the Secret list.
2. Click or press Enter.

Secret management using kubectl CLI

Secrets can be managed using the kubectl CLI rather than the console. Secrets of type Docker Registry are used in ImagePullSecrets in Pods.

A Secret of type Docker Registry is created with the following command. The Secret will be created with the name my-docker-secret .

kubectl create secret docker-registry my-docker-secret --docker-server=DOCKER_REGISTRY_SERVER --docker-username=DOCKER_USER --docker-password=DOCKER_PASSWORD --docker-email=DOCKER_EMAIL

• DOCKER_REGISTRY_SERVER: Docker Registry server information. Example) registry.cloudzcp.io
• DOCKER_USER: Docker login user ID

• DOCKER_PASSWORD : Docker login user password

• DOCKER_EMAIL : Docker login user email

You can check if it was created properly in yaml format.

$ kubectl get secret my-docker-secret --output=yaml apiVersion: v1 data:  .dockerconfigjson: eyJodHRwczovL2luZGV4L ... J0QUl6RTIifX0= kind: Secret metadata:  ...  name: my-docker-secret  ... type: kubernetes.io/dockerconfigjson

As above, you can check the .dockerconfigjson field under data, which is the content that displays Docker Credentials in base64.

To check if the information you entered is correct, run the following command.

$ kubectl get secret my-docker-secret --output="jsonpath={.data.\.dockerconfigjson}" | base64 --decode 

{"auths":{"registry.cloudzcp.io":{"username":"billygoo","password":"xxxxxxxxxxx","email":"billy.goo@example.com","auth":"c3R...zE2"}}}

The auth field value in the result can also be read by decoding it in base64.

$ echo "c3R...zE2" | base64 --decode billygoo:xxxxxxxxxxx

For more details, see Specifying ImagePullSecrets on a Pod.