Secrets

The Secret dictionary stores sensitive data such as passwords, tokens, and keys as key-value pairs. Currently, it only supports keys for creating private repositories and Ceph CSI related information.

For a detailed description of the Secret dictionary, please see kubernets official documentation - Secrets.

How to use image keys.

1. The user creates the key in the secrets dictionary.
2. Users can select existing keys in the image key when using images in private image repositories when creating deployments, statefulset, jobs, and cronjobs.

Entry: In the cloud management platform, click the top left corner of navigation menu, and click “Containers/Application Configuration/Confidentiality Dictionary” menu item in the left menu bar that pops up to enter the Confidentiality Dictionary page.

View Secrets

This function is used to filter the secret dictionary information based on clusters and namespaces.

1. In the secret dictionary page, by default, you can view the secret dictionary information of all namespaces under a cluster.

2. When there are multiple clusters in the environment, click the cluster input box on the right side of the list and select other clusters to view the confidential dictionary information of all namespaces under other clusters.

3. When there are multiple namespaces under a cluster, click the input box on the right side of the namespace above the list, select the namespace, and view the confidential dictionary information under the specified namespace.

   

Create Secrets

This function is used to create a Secrets for image repository keys and Ceph CSI types.

On the Secrets page, click the “Create” button at the top of the list to enter the Create Secrets page. 2. Configure the following parameters. - Type: Currently, you can create a image repository key and a Ceph CSI. - When the type is set to “Image Repository Key”, set the following parameters. - Name: The name of the confidential dictionary. - Cluster: Select the cluster to which the confidential dictionary belongs. - Namespace: Select the namespace to which the confidential dictionary belongs. The namespace is used to logically divide the cluster. deployment, pod, service, etc. all belong to a namespace. Kubernetes cluster will generate default, kube-system, and kube-public namespaces by default after the cluster is created. - Image repository address: Set the address of the image private repository. Please enter the domain name and IP address according to your needs. - User name: Please enter the actual user name of the image private repository according to your needs. - Password: Please enter the actual login password of the image private repository according to your requirements. - Email: Please set the user email address according to your requirements.
- When the type is set to “Ceph CSI”, set the following parameters. - Name: The name of the confidential dictionary. - Cluster: Select the cluster to which the confidential dictionary belongs. - Namespace: Select the namespace to which the confidential dictionary belongs. The namespace is used to logically divide the cluster. deployment, pod, service, etc. all belong to a namespace. Kubernetes cluster will generate default, kube-system, and kube-public namespaces by default after the cluster is created. - UserId: Please set the UserId of Ceph CSI according to your requirements. - UserKey: Please set the UserKey of Ceph CSI according to your requirements. 3. Click the “OK” button to create the Secrets.

View/Edit

This function is used to view or edit the yaml file of the confidential dictionary.

1. On the Secrets page, click the “More” button on the right column of the Secrets, and select the drop-down menu “View/Edit” menu item to bring up the View/Update dialog box.
2. Support viewing and editing yaml file information of confidential dictionary.
3. After editing the yaml file, click “OK” button to take effect.

Delete confidential dictionary

This function is used to delete a confidential dictionary.

Delete

1. On the confidential dictionary page, click the “Delete” button in the action column on the right side of the confidential dictionary, and the action confirmation dialog box will pop up.
2. Click the “OK” button to delete the confidential dictionary and related resources.

Batch delete

1. Select one or more confidential dictionaries in the list of confidential dictionaries, and click the “Delete” button at the top of the list to bring up the action confirmation dialog.
2. Click the “OK” button to delete the confidential dictionaries and related resources.

View confidential dictionary details

This function is used to view information about the confidential dictionary.

1. On the Secrets page, click the Secrets Name item to enter the Secrets Details page.
2. View the following information: ID, status, name, status, cluster, namespace, comment, created at, etc.

View Container Group

This function is used to view the container groups associated with the confidential dictionary and supports managing container groups.

View/Edit

This function is used to view the yaml file of a container group.

1. On the Secrets page, click the Secrets name item to enter the Secrets details page.
2. Click the “Container Groups” tab to enter the container groups page.
3. Click the “View/Edit” button on the right column of the container group to bring up the View/Update dialog box.
4. Support viewing and editing the yaml file information of the confidential dictionary.
5. After editing the yaml file, click the “OK” button to take effect.

Delete

This function is used to delete a container group. After the container group is deleted, a new container group will be redeployed according to the yaml file settings.

1. On the Secrets page, click the Secrets name item to enter the Secrets details page.
2. Click the Container Groups tab to enter the Container Groups page.
3. Click the “Delete” button on the right action bar of the container group to bring up the action confirmation dialog.
4. Click the “OK” button to complete the operation.

Delete

This function is used to delete a service.

1. On the Secrets page, click the Secrets name item to enter the Secrets details page.
2. Click the Services tab to enter the Services page.
3. Click the “Delete” button on the right column of the service to bring up the action confirmation dialog box.
4. Click the “OK” button to complete the operation.

View Events

This function is used to record the occurrence of resource object events, including the content, source, cause, and created at, for troubleshooting purposes.

1. On the Secrets page, click the Secrets Name item to enter the Secrets Details page.
2. Click the Events tab to enter the Events page.
3. View the content, source, reason, and created at of the event.

View source information

This function is used to view and edit the yaml information of the confidential dictionary.

1. On the Secrets page, click the Secrets name item to enter the Secrets details page.
2. Click the “Source Information” tab to enter the source information page.
3. Click the “Copy Content” button to copy the yaml file information of the node.
4. After updating the yaml file, click the “Update” button.

View operation log

This function is used to view the operation logs related to the confidential dictionary.

1. On the confidential dictionary page, click the confidential dictionary name item to enter the confidential dictionary details page.
2. Click the Operation Log tab to enter the Operation Log page.
   • If you want to view more operation logs, please click “Load More” button to get more logs.
   • View Log Details: Click the “View” button on the right column of the operation log to view the log details. Copy details are supported.
   • View logs of specified time period: If you want to view the operation logs of a certain time period, set the specific date in the start date and end date at the top right of the list to query the log information of the specified time period.
   • Export logs: Currently, only the logs displayed on this page are supported to be exported. Click the upper-right corner of icon, set the export data column in the pop-up export data dialog, and click the “OK” button to export the logs.