How-to guides
Users can enter the required information for the Kubernetes Engine and select detailed options through the Samsung Cloud Platform Console to create a service.
Create Kubernetes Engine
You can create and use the Kubernetes Engine service from the Samsung Cloud Platform Console.
You can create and manage clusters to use the Kubernetes Engine service. After creating the cluster, you can add services needed for operation, such as nodes, namespaces, and workloads.
Create a cluster
You can create and use a Kubernetes Engine cluster service in the Samsung Cloud Platform Console.
To create a Kubernetes Engine cluster, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Create Cluster button. 2. Go to the Create Cluster page.
- On the Create Cluster page, enter the information required to create a service and select detailed options.
- Enter or select the required information in the Service Information Input area.
| Category | Required status | Detailed description |
|---|
| Cluster name | Essential | Cluster name- must start with an English letter and be entered using English letters, numbers, and special characters (
-) within 3 - 30 characters
|
| Control Plane Settings > Kubernetes Version | Essential | Select Kubernetes version |
| Control Plane Settings > Private Endpoint Access Allowed Resources | Selection | After selecting a resource, click Add to select the resource that will be allowed to access the private endpoint- Only resources in the same account and the same region can be registered
- Regardless of whether it is enabled, the nodes of the cluster can access the private endpoint
|
| Control Plane Settings > Public Endpoint | Selection | After selecting Use, enter the public endpoint Allowed IP range as 192.168.99.0/24- Set the access control IP range to allow external access to the Kubernetes API server endpoint
- If external access is not required, you can disable it to reduce security threats
|
| ServiceWatch log collection | Selection | Set whether to enable log collection so that cluster logs can be viewed in ServiceWatch- If you select Enable, log storage up to 5 GB for all services within the Account is provided free of charge, and charges apply based on storage volume if it exceeds 5 GB
- If you need to view cluster logs, it is recommended to enable the ServiceWatch log collection feature
|
| Cloud Monitoring log collection | Selection | Set whether to enable log collection so that logs for the cluster can be viewed in Cloud Monitoring- If you select Enable, 1 GB of log storage is provided for free across all services in the Account, and any data exceeding 1 GB is deleted sequentially
|
| Network Settings | Required | Network connection settings for the node pool- VPC name: Select a pre-created VPC
- Subnet name: Select a standard Subnet to use from the subnets of the selected VPC
|
| Network Settings > Security Group | Selection | Security Group: After clicking the Select button, select a Security Group in the Select Security Group popup- Up to 4 Security Group can be selected
|
| StorageClass configuration | Required | Select the storage volume to use in the cluster- NFS Volume: Click the Search button and then select File Storage in the File Storage Selection popup. The default File Storage supports only the NFS format. A StorageClass and Provisioner appropriate for the selected File Storage are provided
- Block Storage provides a StorageClass and CSI by default, so no additional configuration is required
|
Table. Kubernetes Engine service information input fields
- Additional Information Input area, enter or select the required information.
| Category | Required | Detailed description |
|---|
| tag | Selection | Add Tag- Up to 50 per resource can be added
- After clicking the Add Tag button, enter or select Key, Value values
|
Table. Kubernetes Engine additional information input items
- Summary Review the detailed information and estimated charges generated in the panel, then click the Create button.
- When creation is complete, check the created resources on the Cluster List page.
Check cluster detailed information
The Kubernetes Engine service allows you to view and edit the full list of resources and detailed information. Cluster Details page includes Details, Node Pools, Tags, Job History tabs.
To view detailed cluster information, follow these steps.
- All Services > Container > Kubernetes Engine Click the menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- Cluster List page, click the resource (cluster) to view its detailed information. 3. Go to the Cluster Details page.
- Cluster Details page displays the cluster’s status information and detailed information, and consists of Details, Node Pool, Tags, Job History tabs.
| Category | Detailed description |
|---|
| Cluster status | Kubernetes Engine cluster status- Running: Creation complete/running
- Updating: Upgrading version
|
| Service cancellation | Button to delete a Kubernetes Engine cluster- To delete a Kubernetes Engine service, you must delete all node pools added to the cluster
- If the service is deleted, the running service may be stopped immediately, so deletion is required after considering the impact of service interruption
|
Table. Cluster status information and additional features
On the Cluster List page, you can view detailed information of the selected resource and, if necessary, edit the information.
| Category | Detailed description |
|---|
| service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform |
| Resource Name | Resource name- In the Kubernetes Engine service, it refers to the cluster name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation Date/Time | Service creation date and time |
| Modifier | User who edited the service information |
| Modification date and time | Date and time the service information was modified |
| Cluster name | Cluster name |
| LLM Endpoint | LLM Endpoint information |
| Control Area Settings | Check the assigned Kubernetes control plane (Control Plane) version and allowed access range- If a Kubernetes version of the control plane that can be upgraded is available, click the Edit icon to perform a Cluster version upgrade. See Cluster version upgrade for details
- Click the Download Admin Kubeconfig/Download User Kubeconfig button for the private endpoint address to download the kubeconfig settings for each role as a yaml document
- Click the Edit icon of the private endpoint access‑allowed resource to modify the allowed resource
- Click the Download Admin Kubeconfig/Download User Kubeconfig button for the public endpoint address to download the kubeconfig settings for each role as a yaml document
- Click the Edit icon of the public endpoint to modify its enabled status and allowed IP range
- Click the Edit icon of ServiceWatch log collection to toggle its enabled status. When log collection is enabled, view the control plane’s Audit/Event logs in ServiceWatch > Log Group
- Click the Edit icon of Cloud Monitoring log collection to toggle its enabled status. When log collection is enabled, view the control plane’s Audit/Event logs in Cloud Monitoring > Log Analysis
|
| Network Settings | View the VPC, Subnet, and Security Group information configured when creating a Kubernetes Engine cluster- Click each setting to view detailed information on the details page
- If you need to change the Security Group, click the Edit icon to configure
- Managed Security Groups are system-provided items that are created automatically
|
| StorageClass configuration | If you click the NFS volume name, you can view detailed information on the storage details page |
Table. Cluster Details Tab Items
Reference
- The version of Kubernetes Engine is expressed as
[major].[minor].[patch], and you can upgrade only one minor version at a time.- Example: version
1.11.x > 1.13.x (Not allowed) / version 1.11.x > 1.12.x (Allowed)
- If you are using a Kubernetes version that has reached end of support or a version that is scheduled to reach end of support, a red exclamation mark will appear to the right of the version. * If this icon appears, we recommend upgrading the Kubernetes version.
Node pool
You can view, add, modify, or delete cluster node pool information. For detailed information on using node pools, refer to Managing Nodes.
| Category | Detailed description |
|---|
| Add node pool | Add a node pool to the current cluster |
| Node pool list | View the list of node pools created in the current cluster- Click a node pool name to navigate to its detail page and view detailed information
More menu- Node List: displays node name, version, and status information
- Upgrade: upgrade the node pool version
- Node Count Adjustment: adjust node count
- Delete Node Pool: delete the node pool
|
| Node pool details | Provides node pool management features- Node List: Displays node name, version, and status information
- Upgrade: Upgrade node pool version
- Adjust Node Count: Adjust node count
- Delete Node Pool: Delete node pool
- Server Information: Displays server information of the node pool
- Network Information: Displays network information of the node pool
- Node Information: Displays version, labels, taints, and advanced settings
- Connected Resources: Displays connected resources of the node pool
|
Table. Node pool tab items
Reference
If a red exclamation mark icon appears on the node pool version, the server OS of that node pool is not supported in newer Kubernetes versions. The node pool server OS must be upgraded to ensure stable service.
- To upgrade the node pool version, delete the existing node pool and then create a new node pool with a higher server OS version.
Tag
On the Cluster List page, you can view the tag information of the selected resource and add, modify, or delete it.
| Category | Detailed description |
|---|
| Tag list | Tag list- You can view the Key and Value information of the tag
- Up to 50 tags can be added per resource
- When entering a tag, you can search and select from the list of previously created Keys and Values
|
Table. Cluster Tag Tab Items
Job History
You can view the operation history of the selected resource on the Cluster List page.
| Category | Detailed description |
|---|
| Task History List | Resource Change History- You can view the work details, work date and time, resource type, resource name, work result, and operator information
- Work History List When you click the corresponding resource in the list, Work History Details a popup window opens
|
Table. Cluster job history tab items
Managing Cluster Resources
To manage cluster resources, we provide cluster version upgrade, kubeconfig download, and control plane logging modification features.
Caution
To use Kubernetes Engine, you need minimum view permissions for VPC, VPC Subnet, Security Group, FileStorage, and Virtual Server.
Security Group and Virtual Server are created/deleted by Kubernetes Engine for lifecycle management purposes even without create/delete permissions, and the creator/modifier is recorded as System.
Cluster version upgrade
If there is a version that can be upgraded from the cluster’s Kubernetes version, you can perform the upgrade on the Cluster Details page.
Reference
- Check the following items before upgrading the cluster.
- Check if the cluster status is Running
- Check whether the status of all node pools in the cluster is Running or Deleting.
- Check that all node pool versions in the cluster match the cluster’s version.
- Check whether automatic scaling up/down of all node pools in the cluster and the node auto-recovery feature are disabled.
- After upgrading the cluster, proceed with the node pool upgrade. * The control plane and node pool upgrades of a Kubernetes cluster are performed separately.
- You can upgrade only one minor version at a time.
- Example: version 1.12.x > 1.13.x (possible) / version 1.11.x > 1.13.x (not possible)
- After an upgrade, you cannot perform a downgrade or rollback, so to use a previous version again, you must create a new cluster.
Caution
- Since user systems using an end‑of‑life Kubernetes version may become vulnerable, upgrade the control plane and node pool versions directly from the Samsung Cloud Platform Console.
- There is no additional cost for the upgrade.
- Please conduct compatibility testing of the upgrade version in advance to ensure stable system operation for users.
Pre-upgrade preparation for cluster version
When upgrading the cluster version, there is no need to delete and recreate API objects. For the migrated API, all existing API objects can be read and updated using the new API version. However, due to the deprecated API in older versions of Kubernetes, you may be unable to read or modify existing objects, or create new ones. Therefore, to ensure system stability, it is recommended to migrate the client and manifest before upgrading.
Migrate the client and manifest using the following method.
- Download the latest version of the client (e.g., kubectl), install it on the cluster, and modify the YAML to reference the new API.
- Or use a separate plugin (kubectl convert) to convert automatically. * For detailed instructions, refer to the 쿠버네티스 공식 문서 > 리눅스에 kubectl 설치 및 설정.
Reference
Since the deprecated API differs for each cluster version, the scope of application and system impact may vary. For detailed information, refer to the
쿠버네티스 공식 문서 > Deprecation Guide.
Upgrade cluster and node pool versions
To update the cluster and node pool, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engines.
- Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- On the Cluster List page, click the resource (cluster) to upgrade the version. 3. Navigate to the Cluster Details page.
- Cluster Details page, click the Edit icon for the Kubernetes Version. 4. Cluster version upgrade A popup window opens.
- Select the Kubernetes version to upgrade, and click the Confirm button.
- It may take a few minutes for the cluster upgrade to complete.
- While the upgrade is in progress, the cluster status is shown as Updating, and when the upgrade completes, it is shown as Running.
- When the upgrade is complete, select the Node Pool tab. 6. Go to the Node Pool page.
- Click the More button of the node pool item and click Upgrade. 7. Node pool version upgrade A popup window opens.
- Node Pool Version Upgrade After checking the message in the popup window, click the Confirm button.
- It may take a few minutes for the node pool upgrade to complete.
- While the upgrade is in progress, the node pool status is shown as Updating, and when the upgrade is complete, it is shown as Running.
kubeconfig download
You can download the admin/user kubeconfig settings for the cluster’s public and private endpoints as a yaml document.
To download the cluster’s kubeconfig settings, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engines.
Service Home 페이지에서 클러스터 메뉴를 클릭하세요. 2. Navigate to the Cluster List page.
- On the Cluster List page, click the resource (cluster) to download the kubeconfig. 3. Navigate to the Cluster Details page.
- Cluster Details page, click the Download admin kubeconfig/Download user kubeconfig button for the desired endpoint.
- You can download the kubeconfig file in YAML format for each permission.
Modify resources that allow private endpoint access
You can modify the resource settings that allow private endpoint access to the cluster.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engines.
- On the Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- On the Cluster List page, click the resource (cluster) for which you want to modify the private endpoint access control. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, click the Edit icon of Private Endpoint Access Allowed Resources. 4. Edit Private Endpoint Access Allowed Resources The popup window opens.
- Edit Private Endpoint Access Allowed Resources In the popup window, set the Use status of Private Endpoint Access Allowed Resources, add the allowed access resource, and then click the Confirm button.
Modify public endpoint
You can change the public endpoint settings of the cluster.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engines.
- Click the Cluster menu on the Service Home page. 2. Navigate to the Cluster List page.
- On the Cluster List page, click the resource (cluster) for which you want to modify the public endpoint access control. 3. Navigate to the Cluster Details page.
- Click the Edit icon of the Public Endpoint on the Cluster Details page. 4. Edit Public Endpoint The popup window opens.
- Public Endpoint Edit In the popup, set the Public Endpoint’s Usage status and add the allowed IP range, then click the Confirm button.
Modify control plane log collection settings
You can change the log collection settings of the cluster’s control plane (Control Plane). Detailed logs of the cluster can be viewed in the ServiceWatch service or the Cloud Monitoring service.
Reference
Even if you configure Cloud Monitoring log collection, you can view the cluster logs.
- However, since the Cloud Moniotring log collection feature is scheduled for discontinuation, we recommend using ServiceWatch log collection.
To change the control plane log collection settings of the cluster, follow the steps below.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engines.
Service Home 페이지에서 클러스터 메뉴를 클릭하세요. 2. Navigate to the Cluster List page.
- Cluster List page, click the resource (cluster) you want to modify control plane logging for. 3. Go to the Cluster Details page.
- On the Cluster Details page, click the Edit icon for ServiceWatch log collection. 4. ServiceWatch log collection The popup window opens.
- The Cloud Monitoring log collection feature can also be configured in the same way.
- ServiceWatch Log Collection in the popup window, set the use option for ServiceWatch Log Modification, then click the Confirm button.
Reference
When log collection is enabled, you can view the Audit/Event logs of the cluster control plane in each service. Detailed logs can be viewed on the next page.
Security Group Modify
You can modify the cluster’s Security Group.
Caution
In the network settings of Kubernetes Engine, you can select up to four Security Groups.
- If you manually add a Security Group to a node created by Kubernetes Engine on the Virtual Server service page, it may be automatically removed because it is not managed by Kubernetes Engine.
- For nodes, be sure to add and manage the Security Group in the network settings of the Kubernetes Engine service.
Managed Security Group is automatically managed in Kubernetes Engine.
- Do not use it for any user-defined purpose because if you delete a Managed Security Group or add/delete rules, it will automatically be restored.
To modify the cluster’s Security Group, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engines.
- Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- Cluster List page, click the resource (cluster) whose Security Group you want to modify. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, click the Edit icon of the Security Group. 4. Security Group Edit The popup window opens.
- After selecting or deselecting the Security Group to modify, click the Confirm button.
Terminate Cluster
Caution
If you terminate the cluster, all associated node pools will be deleted, and all data in every pod within the cluster will be permanently removed.
To terminate the cluster, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engines.
- On the Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- Cluster List page, click the resource (cluster) to view its detailed information. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, click Cancel Service.
- Service Termination After reviewing the content in the popup window, click the Confirm button.
1 - Managing Nodes
A node is a set of machines that run containerized applications. A cluster must have at least one node to deploy the application. A node can be defined and used in a node pool. Nodes belonging to a node pool must have the same server type, size, and OS image, and you can establish a flexible deployment strategy by creating multiple node pools.
After creating a Kubernetes Engine cluster, add a node pool and modify or delete it as needed.
Caution
- It is recommended not to use the OS firewall on Kubernetes Engine nodes that use Calico.
- The firewall settings of the Samsung Cloud Platform are set to Inactive by default.
- As recommended in the reference link below, in environments using Calico, it is advisable to configure the firewall as disabled.
Add node pool
A node refers to a machine that runs containerized applications, and at least one node is required to deploy applications in a Kubernetes cluster. After the creation of the Kubernetes Engine cluster is complete, add a node pool on the details page.
- In Kubernetes Engine, you can define and use a node pool, which is a set of nodes. * Since the nodes in a node pool use the same server type, size, and OS image, users can devise flexible deployment strategies by using multiple node pools.
Reference
In the Virtual Server menu, you can create a node pool using the user’s Custom Image. To create a node pool using a Custom Image, follow the steps below.
- Create a Virtual Server that includes a Kubernetes Engine image of Samsung Cloud Platform.
- Use the Image creation feature of the Virtual Server to create the image.
- Select the registered Custom Image to create a node pool.
To add a node pool, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- On the Cluster List page, select the cluster you want to add a node pool to. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, select the Node Pool tab, then click the Add Node Pool button. 4. Add Cluster Node Pool Navigate to the page.
- Add Cluster Node Pool page, enter the information required to create a node pool, and select detailed options.
- Enter or select the required information in the Service Information Input area.
| Category | required status | Detailed description |
|---|
| Node pool name | Required | Node pool name- must start with a lowercase English letter and use lowercase letters, numbers, and special characters (
-) within 3-20 characters- cannot end with a special character (
-)
|
| Server Information > Server Type | Required | Node’s Virtual Server server types- Standard: Standard specifications commonly used
- High Capacity: Large server specifications exceeding Standard
- GPU: GPU specifications available when securing resources for special requirements such as AI/ML
- For detailed information about the server types provided by Virtual Server, refer to Virtual Server 서버 타입
|
| Server Information > Server OS | Required | Node’s Virtual Sever OS image- Standard: RHEL 8.10, Ubuntu 22.04
- Custom: Custom image for Kubernetes created from the Virtual Server product (RHEL, Ubuntu)
|
| Server Information > Block Storage | Required | Block Storage settings used by the node’s Virtual Server- SSD: high-performance general volume
- SSD/HDD_KMS: additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption keys
- Encryption can only be applied at initial creation and cannot be changed after the service is created
- Performance degradation occurs when using the SSD_KMS disk type
- SSD_Provisioned: enter detailed settings for the selected storage type
- Enter a value in the Max IOPS field within the range 5000-20000, and in the Max Throughput field within the range 250-1000
- For a Custom Image with SSD_Provisioned, the predetermined values are auto-filled and the fields are disabled
- Capacity is entered in Units, with a value between 13 and 1536
- Since 1 Unit equals 8 GB, this creates 104–12,288 GB
|
| Server Information > Server Group | Selection | Apply a pre‑created Server Group in the Virtual Server service on the node- Click Use to configure Server Group usage
- When usage is enabled, select a Server Group
- Supports Affinity or Anti‑Affinity policies
- Partition policy is not supported
- Cannot modify after node pool creation
- GPU server type cannot be selected
|
| Server Information > Keypair | Required | User authentication method used to connect to a node’s Virtual Server- New: Create a new one if a new Keypair is required
- For instructions on creating a new Keypair, see Keypair 생성하기
- Default login account list by OS
|
| Network Information > Subnet Name | Required | Select the Subnet of the chosen VPC- Only Subnets with a registered DNS IP can be used
|
| Network Information > Availability Zone | Required | Select Availability Zone |
| Network Information > Prioritize IP Assignment | Selection | Use click and enter an IP address or IP range- Multiple IP addresses or ranges can be entered separated by commas
- Refer to 노드 풀 우선 IP 지정 설정하기 for configuration instructions
|
| Node Information > Node Pool Auto Scaling/Downscaling | Required | Automatically adjust the number of nodes in a node pool |
| Node Information > Node Count | Required | Number of nodes to create within a node pool- Enter a value within the range of 1-100
|
| Node Information > Node Auto Recovery | Required | When an abnormal node is detected in the node pool, automatically delete and create a new one |
| Node Information > Label | Selection | Optionally schedule the workload on a node- Add click the button to enter the label key and value
|
| Node Info > Taint | Selection | Prevent workloads from being scheduled onto nodes- Add button to click for taint effect, enter key and value
|
| Node Information > Advanced Settings | Selection | Settings for detailed areas such as pods and logs for the node- Click Use to select whether to apply advanced configuration items for the node pool to be created
|
| connection resource | Selection | Configure File Storage and Object Storage resources for nodes at the node pool level- Click the Add button to select the File Storage and Object Storage resources to attach to the node pool you will create
|
Table. Kubernetes Engine node pool service information input items
- Summary Check the detailed information and estimated charges generated in the panel, and click the Create button.
- When creation is complete, check the created resources on the Cluster Details > Node Pool Tab > Node Pool List page.
- When the notification popup opens, click the Confirm button.
Adjusting the number of nodes
If needed, modify the number of nodes in the node pool on the Kubernetes Engine detail page.
Reference
Modifying the node count will automatically add or remove nodes, causing the container operation to terminate. At this time, the container moves to another node, which may cause the running service to be interrupted.
To modify the number of nodes, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- On the Cluster List page, select the cluster whose node count you want to modify. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, select the Node Pool tab, then click the Node Pool Name you want to edit. 4. Go to the Node Pool Details page.
- On the Node Pool Details page, click the Adjust Node Count icon to the right of Node Pool Information. 5. Or click More > Adjust Node Count at the far right of the node pool entry in the Node Pool tab. 5. Adjust Node Count The popup window opens.
- Node Count Adjustment In the popup window, modify the node count information, then click the Confirm button.
Upgrade Node Pool
If the control plane’s Kubernetes version and the node pool’s version differ, you can upgrade the node pool to synchronize the versions.
Caution
- After upgrading the cluster, proceed with a node pool upgrade. The control plane and node pool upgrades of a Kubernetes cluster are performed separately.
- When a node pool upgrade is performed, a rolling update is carried out on the nodes belonging to the node pool. At this point, a brief service interruption may occur, but this is a normal effect of the rolling update and will automatically normalize after a short period.
- The server OS version may vary depending on the Kubernetes version of the node pool.
To upgrade the node pool, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- Select the cluster on the Cluster List page for which you want to perform a node pool version upgrade. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, after selecting the Node Pool tab, click More > Upgrade at the far right of the node pool entry. 4. Or click the Upgrade button at the top right of the node pool detail page. 4. Node Pool Version Upgrade A popup window opens.
- You can upgrade the node pool only when the node’s status is Running.
- Node Pool Version Upgrade After reviewing the information in the popup window, click the Confirm button.
Auto-scaling node pool
Node pool auto-scaling is a feature that automatically adjusts the number of nodes in a specified node pool by adding new nodes or removing existing nodes according to workload demands. This feature operates based on the node pool.
- When a node pool auto‑scales, it is adjusted based on the resource requests of the pods running on the node pool’s nodes, rather than the actual resource utilization, and it periodically checks the status of pods and nodes and executes the auto‑scaling operation.
To set up the node pool’s automatic scaling feature, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- On the Cluster List page, select the cluster you want to use the node auto‑scaling feature for. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, select the Node Pool tab, then click the Node Pool Name you want to edit. 4. Go to the Node Pool Details page.
- On the Node Pool Details page, click the Adjust Node Count icon to the right of Node Pool Information. 5. Or click More > Adjust Node Count at the far right of the node pool entry in the Node Pool tab. 5. Adjust Node Count The popup window opens.
- In the Node Count Adjustment popup, select Node Pool Auto-Scaling as Enabled.
- After entering the minimum and maximum node counts, click the Confirm button.
Reference
Node pool auto‑scaling settings can also be configured on the cluster node pool creation page.
- Node pool scaling conditions
- When a pod fails to start in the cluster due to insufficient resources (Pending pod occurs)
- Node pool reduction condition (when all are met)
- If the sum of resource requests (CPU/Memory) of all pods running on a node is less than 50% of the node’s allocatable resources.
- If all pods running on a node can be run on another node (there must be no pods subject to PDB restrictions, etc.)
- When using automatic node pool scaling, add the following annotation to the node to prevent deletion caused by node reduction.
cluster-autoscaler.kubernetes.io/scale-down-disabled: “true”
Caution
- Node pool auto-scaling works only when the NotReady nodes among all nodes in the cluster are 45% or less of the total and no more than three.
- If there are nodes directly connected instead of node pools created by the Kubernetes Engine service, the feature may malfunction when used.
Automatically restore node pool
Node auto-recovery is a feature that automatically deletes an abnormal node detected in the cluster, creates a new node, and restores the node count in the node pool to a normal state. This feature operates based on the node pool.
Caution
Node auto-recovery deletes the existing node and creates a new one when communication between K8S control planes is disrupted due to node (Virtual Server) problems, a stopped state, network issues, etc., according to the auto-recovery criteria, so it should be used with caution.
- When creating a node pool, it is restored according to the initially set conditions, and custom settings made after node creation are not restored.
If there are nodes directly connected instead of node pools created by the Kubernetes Engine service, the feature may malfunction when used.
To enable the node auto-recovery feature, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- On the Cluster List page, select the cluster for which you want to use the node auto-recovery feature. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, select the Node Pool tab, then click the Node Pool Name you want to edit. 4. Go to the Node Pool Details page.
- On the Node Pool Details page, click the Adjust Node Count icon to the right of Node Pool Information. 5. Or click More > Adjust Node Count at the far right of the node pool entry in the Node Pool tab. 5. Adjust Node Count The popup window opens.
- In the Node Count Adjustment popup, select Node Auto Recovery as Enabled, then click the Confirm button.
Reference
Node auto-recovery can also be configured on the cluster node pool creation page.
- If the node is a target for automatic recovery
- When a node reports a NotReady status in successive checks for a certain time threshold (about 10 minutes).
- When a node does not report its status at all for a certain time threshold (approximately 10 minutes)
- If the node is not a target for automatic recovery
- When the initial node is created, it remains in the Creating state and does not become Running.
- When more than five abnormal nodes occur simultaneously in the same node pool.
Node pool labels are a feature for optionally scheduling workloads onto nodes.
Caution
- When applying a node pool label, it does not affect existing nodes; the label is applied only to nodes created thereafter.
- If you need to apply a label to an existing node, the user must set it directly with kubectl.
To set the node pool label, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- Select the cluster for which you want to set the node pool label on the Cluster List page. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, select the Node Pool tab, then click the Node Pool Name you want to edit. 4. Go to the Node Pool Details page.
- On the Node Pool Details page, clicking the Edit icon of a label opens the Edit Label popup.
- Edit Label In the popup window, click the Add button to add as many labels as needed.
- Enter the label information and click the Confirm button.
Node pool taint is a feature that prevents workloads from being scheduled onto nodes.
Caution
- If you set taints on all node pools, pods required for normal cluster operation may not be scheduled.
- When applying a node pool taint, it does not affect existing nodes; the taint is applied only to newly created nodes.
- If you need to apply a taint to an existing node, the user must configure it directly with kubectl.
To set the node pool taint, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Cluster menu. 2. Go to the Cluster List page.
- On the Cluster List page, select the cluster for which you want to set a node pool taint. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, select the Node Pool tab, then click the Node Pool Name you want to edit. 4. Go to the Node Pool Details page.
- On the Node Pool Details page, when you click the Edit icon of the taint, the Edit Taint popup opens.
- Tint Edit In the popup window, click the Add button to add as many tints as needed.
- Enter the tint information and click the Confirm button.
Node pool advanced settings are a feature for applying detailed configurations such as the number of pods per node, PID, logs, and image garbage collection.
Caution
Node pools cannot be modified after creation. If an invalid value is entered, the node may not operate correctly.
Reference
Each setting corresponds to the kubelet configuration as follows.
- Maximum pods per node: maxPods
- Image GC upper limit percent: imageGCHighThresholdPercent
- Image GC lower bound percent: imageGCLowThresholdPercent
- Container log maximum size MB: containerLogMaxSize
- Maximum number of container log files: containerLogMaxFiles
- Pod PID limit: podPidsLimit
- Unsafe Sysctl allowed: allowedUnsafeSysctls
To configure advanced settings for the node pool, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- Cluster List page, select the cluster you want to configure advanced node pool settings for. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, after selecting the Node Pool tab, click Create Node Pool. 4. Navigate to the Create Node Pool page.
- On the Node Pool Creation page, select Advanced Settings as Enabled.
- Use After selecting, enter the required information for the items that appear.
- In the Summary tab, verify that the required information has been entered correctly, then click the Create button.
Node pool connection resources are a feature for connecting or disconnecting File Storage and Object Storage on a per‑node‑pool basis.
Caution
- There is a limit on the number of node pool connection resources.
- You can add up to three File Storage and three Object Storage, for a total of six connection resources.
- StorageClass and Provisioner for the connected resource are not provided.
- Do not arbitrarily modify the automatically added connection resources in the node pool for File Storage and Object Storage services. * Changes may be reverted or cause unexpected behavior.
To configure node pool connection resources, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- Select the cluster you want to configure node pool connection resources for on the Cluster List page. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, select the Node Pool tab, then click the Node Pool Name you want to edit. 4. Go to the Node Pool Details page.
- Node Pool Details page, when you click the Edit icon of a connected resource, the Edit Connected Resource popup opens.
- Edit Connection Resource popup, when you click the Add button, the Add Connection Resource popup opens.
- Add Connected Resource In the popup window, select File Storage and Object Storage.
- After verifying the resources to connect to the node pool, click the Confirm button.
It is a feature that prioritizes assigning IPs to new nodes on a per‑node‑pool basis. If you enable Priority IP assignment, IPs within the specified range are allocated sequentially when a new node is created. If an IP cannot be assigned within the specified range, the IP within the cluster Subnet will be automatically allocated, just as when Priority IP assignment is not set.
To configure priority IP assignment for the node pool, follow the steps below.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Cluster menu. 2. Navigate to the Cluster List page.
- Select the cluster on the Cluster List page for which you want to set the node pool preferred IP assignment. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, select the Node Pool tab, then click the Node Pool Name you want to edit. 4. Go to the Node Pool Details page.
- Node Pool Details page, when you click the Edit icon of the priority IP assignment, the Edit Priority IP Assignment popup opens.
- Edit Priority IP Assignment In the popup window, enter the priority IP range and click the Confirm button.
Reference
First, the input format for the IP range is as follows.
- Single IP: a single IPv4 address (e.g., 192.168.99.0)
- IP range: specify a continuous address in the startIP‑endIP format (e.g., 192.168.0.0-192.168.0.255)
- Combination: Enter as a single string separating the two above with commas (,) (e.g., 192.168.99.0,192.168.0.0-192.168.0.255,10.0.0.5)
Delete Node Pool
Delete the node pool from the Kubernetes Engine detail page if needed.
To delete a node pool, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Cluster menu. 2. Go to the Cluster List page.
- On the Cluster List page, select the cluster whose node count you want to modify. 3. Navigate to the Cluster Details page.
- On the Cluster Details page, select the Node Pool tab, then click the More button at the far right of the node pool entry. 4. Or click the Delete Node Pool button at the top right of the node pool detail page. 4. Node Pool Deletion A popup window opens.
- Node Pool Deletion In the popup window, select the checkbox, enter the name of the node pool to delete, and click the Confirm button.
- You must select the checkbox in the node deletion confirmation message for the confirm button to become active.
View node detailed information
After creating the cluster, you can view metadata, object information, and other details of the added nodes, and edit resource files using a YAML editor.
To view detailed information about the node pool, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Node menu. 2. Navigate to the Node List page.
- On the Node List page, select the cluster you want to view detailed information for from the gear button at the top left, then click the Confirm button.
- Select the node you want to view detailed information for and click. 4. Node Details page is accessed.
| Category | Detailed description |
|---|
| Status Indicator | Display the current status of the node |
| Detailed Information | Check the node’s account information, metadata, and object information. |
| YAML | Node resources can be edited in the YAML editor- Edit button click, modify the resource, then click the Save button to apply the changes
- When editing content, you can click the Diff button to view the changed content
|
| event | Check events that occurred on the node |
| Pod | Check node pod information- Pod (pod) is the smallest compute unit that can be created, managed, and deployed in Kubernetes Engine
|
| Account information | Check basic information about the Account, such as name, location, and creation date/time. |
| Metadata Information | Check the node’s label, annotation, taint, and other metadata information. |
| Object Information | The internal IP, machine ID, capacity, resources, etc., of the created node are displayed- If GPU resources are present, check the number of GPUs in the Capacity > Nvidia.com/GPU column
|
Table. Node detailed information items
2 - Managing Namespaces
A namespace is a logical separation unit within a Kubernetes cluster and is used to specify access permissions or resource usage limits per namespace.
Create a namespace
To create a namespace, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- Click the Namespace menu on the Service Home page. 2. Go to the Namespace List page.
- On the Namespace List page, select the cluster for which you want to create a namespace from the list in the upper left, then click Create Object.
- In the Object Creation Popup, enter the object information and click the Create button.
Reference
For detailed information on object creation, refer to the
쿠버네티스 공식 문서 > 쿠버네티스 오브젝트.
Check detailed namespace information
You can view the namespace status and detailed information on the namespace detail page.
To view detailed namespace information, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- Click the Namespace menu on the Service Home page. 2. Go to the Namespace List page.
- Namespace List page, after selecting the cluster that the namespace requiring detailed information belongs to from the list at the top left, click View.
- On the Namespace List page, select the item you want to view details for and click it. 4. Navigate to the Namespace Details page.
| Category | Detailed description |
|---|
| Status display | Display the current state of the namespace |
| Delete Namespace | Delete the namespace- A namespace containing workloads cannot be deleted. To delete the namespace, you must delete all associated workloads
|
| Detailed Information | Check the Account information and metadata of the namespace |
| YAML | Namespaces can be edited in the YAML editor- Click the Edit button, modify the namespace, then click the Done button to apply the changes
- When editing content, click the Diff button to view the changed content
|
| event | Check events that occurred within the namespace |
| Pod | Check the pod information of the namespace |
| Account information | Check basic information about the Account, such as its name, location, and creation date/time. |
| Metadata Information | Check the namespace’s metadata information |
Table. Namespace detailed information items
Delete namespace
To delete a namespace, follow these steps.
- All Services > Container > Kubernetes Engine menu, click it. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click the Namespace menu. 2. Go to the Namespace List page.
- On the Namespace List page, select the cluster that the namespace you want to delete belongs to from the list at the top left, then click Search.
- On the Namespace List page, select the item you want to view details for and click it. 4. Navigate to the Namespace Details page.
- On the Namespace Details page, click Delete Namespace.
- Notification dialog appears, click the Confirm button.
Caution
On the namespace list page, after selecting the item you want to delete, click Delete to remove the selected namespace.
- Namespaces containing workloads cannot be deleted. To delete a namespace, delete all associated workloads.
3 - Managing Workloads
The workload is an application that runs on Kubernetes Engine. After creating a namespace, you can add or delete workloads. Workloads are created and then managed for each item such as Deployment, Pod, StatefulSet, DaemonSet, Job, and CronJob.
Reference
Deployments, Pods, StatefulSets, DaemonSets, Jobs, and CronJobs are set to the cluster (namespace) selected when creating the service by default. Even if you select a different item in the list, the default cluster (namespace) setting is retained.
- To select a different cluster (namespace), click the list at the top left of the list page. * Select the cluster and namespace to modify from the list, and click the View button. * You can view the services created in the selected cluster/namespace.
Managing Deployments
A Deployment is a resource that provides updates for Pods and ReplicaSets (ReplicaSet). You can create a deployment in the workload, view its details, or delete it.
Create Deployment
To create a deployment, follow the steps below.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Deployment under the Workload menu. 2. Go to the Deployment List page.
- Deployment List page, after selecting the cluster and namespace from the list in the upper left, click Create Object.
- In the Object Creation Popup, enter the object information and click the Create button.
- The following is an example
.yaml file showing the required fields and object Spec for creating a Deployment. * (application/deployment.yaml) apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx-deployment
spec:
selector:
matchLabels:
app: nginx
replicas: 2 # tells deployment to run 2 pods matching the template
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.14.2
ports:
- containerPort: 80
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx-deployment
spec:
selector:
matchLabels:
app: nginx
replicas: 2 # tells deployment to run 2 pods matching the template
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.14.2
ports:
- containerPort: 80
Code block. Required fields and object Spec for deployment creation
Reference
For detailed information on the concept of Deployments and object creation, please refer to the
쿠버네티스 공식 문서 > 디플로이먼트.
Check deployment detailed information
To view deployment details, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Deployment under the Workload menu. 2. Navigate to the Deployment List page.
- Deployment List page, select the cluster and namespace from the list at the top left, then click Search.
- Deployment List page, select the item you want to view detailed information for. 4. Navigate to the Deployment Details page.
- If you select System Object Display at the top of the list, all items except the Kubernetes object entries will be shown.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete Deployment | Delete the deployment |
| Detailed Information | Detailed deployment information can be viewed |
| YAML | The deployment’s resource file can be edited in the YAML editor- Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, click the Diff button to view the changes
|
| event | Check events that occurred within the deployment |
| Pod | Check the pod information of the deployment- Pod(파드) is the smallest compute unit that can be created, managed, and deployed in Kubernetes Engine
|
| Account information | Check basic information about the Account, such as its name, location, and creation date/time. |
| Metadata Information | Check the deployment’s metadata information |
| Object Information | Check the deployment’s object information |
Table. Deployment detailed information items
Delete Deployment
To delete the deployment, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Deployment under the Workload menu. 2. Go to the Deployment List page.
- Deployment List page, select the cluster and namespace from the list at the top left, then click View.
- Select the item you want to delete on the Deployment List page. 4. Go to the Deployment Details page.
- Click Delete Deployment on the Deployment Details page.
- When the notification dialog appears, click the OK button.
Caution
On the deployment list page, after selecting the item you want to delete, click Delete to remove the selected deployment.
Managing Pods
A Pod is the smallest compute unit in Kubernetes that can be created, managed, and deployed, representing a group of one or more containers. You can create pods in a workload, view detailed information, or delete them.
Create Pod
To create a pod, follow these steps.
- All Services > Container > Kubernetes Engine Click the menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Pod under the Workload menu. 2. Go to the Pod List page.
- On the Pod List page, select the cluster and namespace from the list at the top left, then click Create Object.
- In the Object Creation Popup, enter the object information and click the Create button.
Reference
For detailed information on the concept of pods and object creation, refer to the
쿠버네티스 공식 문서 > 파드.
Check pod details
To view detailed pod information, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Pod under the Workload menu. 2. Navigate to the Pod List page.
- On the Pod List page, select the cluster and namespace from the list at the top left, then click Search.
- Select the item whose detailed information you want to view on the Pod List page. 4. Navigate to the Pod Details page.
- If you select System Object Display at the top of the list, all items except the Kubernetes object entries will be shown.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Status display | Display the current status of the pod |
| Delete pod | Delete the pod |
| Detailed Information | Can view detailed pod information |
| YAML | The pod’s resource file can be edited in the YAML editor- Click the Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, click the Diff button to view the changed content
|
| event | Check events that occurred within the pod |
| log | Select a container to view the pod’s container information. |
| Account information | Check basic information about the Account, such as its name, location, and creation date/time. |
| Metadata Information | Check the pod’s metadata information |
| Object Information | Check the pod’s object information |
| Initialization Container Information | Check the pod’s init container information |
| Container Information | Check the pod’s container information |
Table. Pod detailed information items
Delete Pod
To delete a pod, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Pod under the Workload menu. 2. Go to the Pod List page.
- On the Pod List page, select the cluster and namespace from the list in the upper left, then click Search.
- On the Pod List page, select the item you want to delete. 4. Go to the Pod Details page.
- On the Pod Details page, click Delete Pod.
- Notification dialog appears, click the Confirm button.
On the pod list page, after selecting the item you want to delete, click Delete to delete the selected pod.
Managing StatefulSets
A StatefulSet is a workload API object used to manage an application’s stateful components. You can create a StatefulSet in the workload, view its details, or delete it.
Create a StatefulSet
To create a StatefulSet, follow the steps below.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click StatefulSet under the Workload menu. 2. Navigate to the StatefulSet list page.
- On the StatefulSet List page, select the cluster and namespace from the top‑left list, then click Create Object.
- Enter the object information in the Object Creation Popup and click the Create button.
Reference
For detailed information on the StatefulSet concept and object creation, see the
쿠버네티스 공식 문서 > 스테이트풀셋.
Check detailed information of StatefulSet
To view detailed information about a StatefulSet, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click StatefulSet under the Workload menu. 2. StatefulSet List page is accessed.
- StatefulSet List page, select the cluster and namespace from the list at the top left, then click Search.
- StatefulSet List page, select the item you want to view detailed information for. 4. Navigate to the StatefulSet Details page.
- If you select System Object Display at the top of the list, all items except the Kubernetes object entries will be shown.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete StatefulSet | Delete the StatefulSet |
| Detailed Information | Detailed information of the StatefulSet can be viewed |
| YAML | The resource file of a StatefulSet can be edited in the YAML editor- Edit button click and after modifying the resource, click the Done button to apply the changes
- When editing content, click the Diff button to view the changes
|
| event | Check events that occurred within the StatefulSet |
| Pod | Check the pod information of the StatefulSet |
| Account information | Check basic information about the Account, such as its name, location, and creation date/time. |
| Metadata Information | Check the metadata information of the StatefulSet |
| Object Information | Check the object information of the StatefulSet |
Table. StatefulSet detailed information items
Delete StatefulSet
To delete a StatefulSet, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click StatefulSet under the Workload menu. 2. Go to the StatefulSet List page.
- StatefulSet list page, select the cluster and namespace from the list at the top left, then click Search.
- Select the items you want to delete on the StatefulSet list page. 4. StatefulSet Details navigate to the page.
- On the StatefulSet details page, click Delete StatefulSet.
- Notification dialog appears, click the Confirm button.
Caution
On the StatefulSet list page, after selecting the item you want to delete, click Delete to remove the selected StatefulSet.
Managing DaemonSets
A DaemonSet is a resource that ensures a copy of a pod runs on every node or on a subset of nodes. You can create a DaemonSet in the workload, view its details, or delete it.
Create DaemonSet
To create a DaemonSet, follow the steps below.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click DaemonSet under the Workloads menu. 2. Navigate to the DaemonSet List page.
- DaemonSet List page, after selecting the cluster and namespace from the list at the top left, click Create Object.
- In the Object Creation Popup, enter the object information and click the Create button.
Reference
For detailed information on the concept of DaemonSets and object creation, refer to the
쿠버네티스 공식 문서 > 데몬셋.
Check DaemonSet detailed information
Follow these steps to view the detailed information of a DaemonSet.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click DaemonSet under the Workloads menu. 2. Go to the DaemonSet List page.
- On the DaemonSet List page, select the cluster and namespace from the list in the upper left, then click Search.
- On the DaemonSet list page, select the item you want to view detailed information for. 4. Navigate to the DaemonSet Details page.
- If you select System Object Display at the top of the list, all items except the Kubernetes object entries will be shown.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete DaemonSet | Delete the DaemonSet |
| Detailed Information | Can view detailed DaemonSet information |
| YAML | The DaemonSet resource file can be edited in the YAML editor- Click the Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, click the Diff button to view the changes
|
| event | Check events that occurred within the DaemonSet |
| Pod | Check the DaemonSet pod information |
| Account information | Check basic information about the Account, such as its name, location, and creation date/time. |
| Metadata Information | Check the DaemonSet’s metadata information. |
| Object Information | Check the DaemonSet object information |
Table. DaemonSet detailed information items
Delete DaemonSet
To delete a DaemonSet, follow the steps below.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click DaemonSet under the Workloads menu. 2. Navigate to the DaemonSet List page.
- On the DaemonSet List page, select the cluster and namespace from the list at the top left, then click View.
- Select the items you want to delete on the DaemonSet list page. 4. Go to the DaemonSet Details page.
- Click Delete DaemonSet on the DaemonSet Details page.
- Notification dialog appears, click the Confirm button.
---
After selecting the item to delete on the DaemonSet list page, click Delete to delete the selected DaemonSet.
Job Management
It refers to a resource that creates one or more pods and continues to run pods until the specified number of pods have successfully terminated. You can create a job in the workload, view its details, or delete it.
Create Job
Follow these steps to create a job.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Job under the Workload menu. 2. Go to the Job List page.
- On the Job List page, after selecting the cluster and namespace from the top‑left list, click Create Object.
- In the Object Creation Popup, enter the object information and click the Create button.
Reference
For detailed information on the concept of jobs and object creation, refer to the
쿠버네티스 공식 문서 > 잡.
Check job details
To view job details, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Job under the Workload menu. 2. Go to the Job List page.
- On the Job List page, select the cluster and namespace from the list at the top left, then click Search.
- Select the item you want to view detailed information for on the Job List page. 4. Job Details page is opened.
- If you select Show system objects at the top of the list, the remaining items, excluding the Kubernetes object entries, will be displayed.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete job | Delete job |
| Detailed Information | Job detailed information can be viewed |
| YAML | You can edit the job’s resource file in the YAML editor- Click the Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, you can click the Diff button to view the changed content
|
| event | Check events that occurred within the job |
| Pod | Check the job’s pod information |
| Account information | Check basic information about the Account, such as its name, location, and creation date/time. |
| Metadata Information | Check the job’s metadata information |
| Object Information | Check job object information |
Table. Job detailed information items
Delete job
To delete a job, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Job under the Workload menu. 2. Go to the Job List page.
- On the Job List page, select the cluster and namespace from the list in the upper left, then click Search.
- Job List Select the items you want to delete on the page. 4. Go to the Job Details page.
- On the Job Details page, click Delete Job.
- Notification dialog appears, click the Confirm button.
On the job list page, after selecting the item you want to delete, click Delete to delete the selected job.
Managing Cron Jobs
A cron job is a resource that periodically runs a job (Job) according to a schedule written in cron format. It can be used when executing repetitive tasks at regular intervals, such as backups and report generation. You can create a cron job in the workload, view its details, or delete it.
Creating a Cron Job
To create a cron job, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click CronJob under the Workload menu. 2. Cron Job List Navigate to the page.
- On the CronJob List page, select the cluster and namespace from the list in the upper‑left corner, then click Create Object.
- In the Object Creation Popup, enter the object information and click the Confirm button.
Reference
For detailed information on the concept of CronJobs and object creation, refer to
쿠버네티스 공식 문서 > 크론잡.
Check detailed information of cron job
To view detailed information about the cron job, follow these steps.
- All Services > Container > Kubernetes Engine menu, click it. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click CronJob under the Workload menu. 2. Go to the Cron Job List page.
- On the CronJob List page, select the cluster and namespace from the list at the top left, then click View.
- Select the item you want to view detailed information for on the Cron Job List page. 4. Navigate to the Cron Job Details page.
- If you select System Object Display at the top of the list, all items except the Kubernetes object entries will be shown.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete cron job | Delete the cron job |
| Detailed Information | View detailed information of cron jobs |
| YAML | The cron job’s resource file can be edited in the YAML editor- Click the Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, you can click the Diff button to view the changes
|
| event | Check events that occurred within the cron job |
| Job | Check the cron job’s job information. Selecting a job item moves to the job detail page. |
| Account information | Check basic information about the Account, such as its name, location, and creation date/time. |
| Metadata Information | Check the metadata information of the cron job |
| Object Information | Check the object information of the cron job |
Table. Cron job detailed information items
Delete cron job
To delete a cron job, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click CronJob under the Workload menu. 2. Go to the Cron Job List page.
- On the CronJob List page, select the cluster and namespace from the list at the top left, then click View.
- Select the items you want to delete on the Cron Job List page. 4. Go to the Cron Job Details page.
- On the Cron Job Details page, click Delete Cron Job.
- Notification dialog appears, click the Confirm button.
Caution
On the cron job list page, after selecting the item you want to delete, click Delete to remove the selected cron job.
4 - Manage services and ingresses
A Service is an abstraction that exposes applications running in a set of Pods as a network service, and an Ingress is used to expose HTTP and HTTPS routes from outside the cluster to inside the cluster. After creating a namespace, you can create or delete services, endpoints, ingresses, and ingress classes.
Reference
Services, endpoints, ingresses, and ingress classes are set by default to the cluster (namespace) selected when creating the service. Even if you select a different item in the list, the default cluster (namespace) setting is retained.
- To select a different cluster (namespace), click the list in the top-left corner of the list page. * From the list, select the cluster and namespace to modify, then click the Query button. * You can view the services created in the selected cluster/namespace.
Manage Services
You can create a service and view or delete its detailed information.
Create Service
To create a service, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Service under the Service and Ingress menu. 2. Go to the Service List page.
- On the Service List page, select the cluster and namespace from the list in the upper left, then click Create Object.
- In the Object Creation Popup, enter the object information and click the Create button.
Reference
For detailed information on the concept of services and object creation, refer to the
쿠버네티스 공식 문서 > 서비스.
Check service detailed information
To view the detailed service information, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Service under the Service and Ingress menu. 2. Go to the Service List page.
- On the Service List page, select the cluster and namespace from the list in the upper left, then click View.
- On the Service List page, select the item for which you want to view detailed information. 4. Navigate to the Service Details page.
- If you select System Object Display at the top of the list, all items except the Kubernetes object entries will be shown.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete Service | Delete the service |
| Detailed Information | View detailed service information. |
| YAML | The service’s resource file can be edited in the YAML editor- Click the Edit button and modify the resource, then click the Done button to apply the changes
- When editing content, click the Diff button to view the changed content
|
| event | Check events that occurred within the service |
| Account information | Check basic information about the Account, such as name, location, and creation timestamp. |
| Metadata Information | Check the service’s metadata information |
| Object Information | Check the service’s object information |
Table. Service detailed information items
Delete Service
To delete the service, follow these steps.
- All Services > Container > Kubernetes Engine Click the menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Service under the Service and Ingress menu. 2. Navigate to the Service List page.
- On the Service List page, select the cluster and namespace from the list in the upper left, then click View.
- On the Service List page, select the item you want to delete. 4. Navigate to the Service Details page.
- On the Service Details page, click Delete Service.
- Notification dialog appears, click the Confirm button.
Caution
On the service list page, after selecting the item you want to delete, click Delete to remove the selected service.
Managing Endpoints
You can create an endpoint and view or delete its details.
Create Endpoint
To create an endpoint, follow these steps.
- All Services > Container > Kubernetes Engine Click the menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Endpoint under the Service and Ingress menu. 2. Navigate to the Endpoint List page.
- Endpoint List page, after selecting the cluster and namespace from the list at the top left, click Create Object.
- In the Object Creation Popup, enter the object information and click the Create button.
View endpoint detailed information
To view the endpoint details, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Endpoint under the Service and Ingress menu. 2. Go to the Endpoint List page.
- On the Endpoint List page, select the cluster and namespace from the list in the upper left, then click Query.
- On the Endpoint List page, select the item for which you want to view detailed information. 4. Navigate to the Endpoint Details page.
- If you select System Object Display at the top of the list, all items except the Kubernetes object entries will be shown.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Endpoint Deletion | Delete the endpoint |
| Detailed Information | Can view detailed information of the endpoint |
| YAML | The endpoint’s resource file can be edited in the YAML editor- Click the Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, click the Diff button to view the changes
|
| event | Check events that occurred within the endpoint |
| Account information | Check basic information about the Account, such as name, location, and creation date/time. |
| metadata information | Check the endpoint’s metadata information |
| Object Information | Check the endpoint’s object information |
Table. Endpoint detailed information items
Delete endpoint
To delete an endpoint, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Endpoint under the Service and Ingress menu. 2. Navigate to the Endpoint List page.
- On the Endpoint List page, select the cluster and namespace from the list in the upper left, then click Search.
- Select the item you want to delete on the Endpoint List page. 4. Navigate to the Endpoint Details page.
- On the Endpoint Details page, click Delete Endpoint.
- Notification dialog appears, click the Confirm button.
Reference
On the endpoint list page, after selecting the item you want to delete, click Delete to delete the selected endpoint.
Manage Ingress
Ingress is an API object that manages external access (HTTP, HTTPS) to services within the Kubernetes Engine, used to expose workloads externally, and provides L7 load balancing functionality.
Create Ingress
To create an ingress, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- Service Home page, click Ingress under the Service and Ingress menu. 2. Navigate to the Ingress List page.
- On the Ingress List page, after selecting the cluster and namespace from the list at the top left, click Create Object.
- In the Object Creation Popup, enter the object information and click the Create button.
Reference
For detailed information on the concept of Ingress and object creation, refer to the
쿠버네티스 공식 문서 > Ingress.
Check Ingress Detailed Information
To view the detailed ingress information, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- Click Ingress under the Service and Ingress menu on the Service Home page. 2. Go to the Ingress List page.
- On the Ingress List page, select the cluster and namespace from the list at the top left, then click 조회.
- Select the item whose detailed information you want to view on the Ingress List page. 4. Navigate to the Ingress Details page.
- If you select System Object Display at the top of the list, all items except the Kubernetes object entries will be shown.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete Ingress | Delete ingress |
| Detailed Information | Detailed information of the Ingress can be viewed |
| YAML | The Ingress resource file can be edited in the YAML editor- Click the Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, click the Diff button to view the changes
|
| event | Check events that occurred within the ingress |
| Account information | Check basic information about the Account, such as name, location, and creation date/time. |
| Metadata Information | Check the metadata information of the Ingress |
| Object Information | Check the object information of the Ingress |
Table. Ingress detailed information items
Delete Ingress
To delete the ingress, follow these steps.
- All Services > Container > Kubernetes Engine menu, click it. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Ingress under the Service and Ingress menu. 2. Go to the Ingress List page.
- On the Ingress List page, select the cluster and namespace from the list at the top left, then click 조회.
- On the Ingress List page, select the item you want to delete. 4. Go to the Ingress Details page.
- On the Ingress Details page, click Delete Ingress.
- When the notification confirmation window appears, click the Confirm button.
Caution
On the Ingress list page, after selecting the item you want to delete, click Delete to delete the selected Ingress.
Managing Ingress Class
IngressClass refers to an API resource that enables the use of multiple ingress controllers within a single cluster. In each Ingress, you must specify a reference class for the IngressClass resource that includes the configuration, including the controller that must implement the class.
Create Ingress Class
To create an Ingress class, follow the steps below.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Ingress Class under the Service and Ingress menu. 2. Navigate to the Ingress Class List page.
- On the IngressClass List page, select the cluster and namespace from the list at the top left, then click Create Object.
- In the Object Creation Popup, enter the object information and click the Confirm button.
Reference
For detailed information on the concept of IngressClass and object creation, please refer to the
쿠버네티스 공식 문서 > Ingress.
View detailed information of the Ingress class
To view detailed information about the Ingress class, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Ingress Class under the Service and Ingress menu. 2. Navigate to the Ingress Class List page.
- On the IngressClass List page, select the cluster and namespace from the list in the upper left, then click Search.
- On the Ingress Class List page, select the item you want to view detailed information for. 4. Go to the Ingress Class Details page.
- If you select System Object Display at the top of the list, all items except the Kubernetes object entries will be shown.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete IngressClass | Delete the Ingress class |
| Detailed Information | Detailed information of the Ingress class can be viewed |
| YAML | The resource file of the Ingress class can be edited in the YAML editor- Click the Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, you can click the Diff button to view the changed content
|
| event | Check the events that occurred within the Ingress class |
| Account information | Check basic information about the Account, such as name, location, and creation date/time. |
| Metadata Information | Check the metadata information of the Ingress class |
| Object Information | Check the object information of the Ingress class |
Table. Ingress class detailed information items
Delete Ingress Class
To delete the Ingress class, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Ingress Class under the Service and Ingress menu. 2. Navigate to the Ingress Class List page.
- On the IngressClass List page, select the cluster and namespace from the list in the upper left, then click Search.
- Select the item you want to delete on the Ingress Class List page. 4. Navigate to the Ingress Class Details page.
- On the Ingress Class Details page, click Delete Ingress Class.
- Notification dialog appears, click the Confirm button.
Caution
On the IngressClass list page, after selecting the item you want to delete, click Delete to delete the selected IngressClass.
5 - Manage Storage
You can create and manage storage for use with Kubernetes Engine. Storage is created and managed for each PVC, PV, and StorageClass.
Reference
PVC, PV, and storage class services are set by default to the cluster (namespace) selected when creating the service. Even if you select a different item in the list, the default cluster (namespace) setting is retained.
- To select a different cluster (namespace), click the list in the top-left corner of the list page. * Select the cluster and namespace to modify from the list and click the View button. * You can view the services created in the selected cluster/namespace.
Information
The items associated with each storage type are as follows.
| Type | Detailed description |
|---|
| Block storage | Supports a storage class that utilizes the volume of the Block storage product integrated with Virtual Server. |
| Object Storage | Can be integrated with Samsung Cloud Platform products or external Object Storage- No additional configuration is required for the Kubernetes Engine, and it can be directly configured and integrated with workloads (applications) according to the Object Storage guide
|
| File storage | Supports storage classes for NFS and CIFS protocol volumes in conjunction with the File Storage product- For NFS protocol volumes, selection is required when creating a Kubernetes Engine (supports HDD and SSD disk types)
- For CIFS protocol volumes, selection can be made during or after Kubernetes Engine creation
|
Table. Storage linkage items by type
Managing PVC
A Persistent Volume Claim(PVC) is an object defined to allocate the required storage capacity. PVC provides high usability through abstraction and can prevent the issue of data being deleted together when the container lifecycle expires (maintaining Data Persistence).
Create PVC
To create a PVC, follow these steps.
- All Services > Container > Kubernetes Engine Click the menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click PVC under the Storage menu. 2. PVC List Navigate to the page.
- PVC List page, after selecting the cluster and namespace from the top‑left list, click Create Object.
- In the Object Creation Popup, enter the object information and click the Create button.
Reference
For detailed information on the concept of PVCs and object creation, refer to
쿠버네티스 공식 문서 > 퍼시스턴트 볼륨.
Check PVC detailed information
To view detailed PVC information, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click PVC under the Storage menu. 2. Go to the PVC list page.
- On the PVC List page, select the cluster and namespace from the list in the upper left, then click Search.
- PVC List page, select the item for which you want to view detailed information. 4. PVC Details Navigate to the page.
- If you select Show system objects at the top of the list, all items except the Kubernetes object entries are displayed.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Status indicator | Displays the current status of the PVC. |
| Delete PVC | Delete PVC |
| Detailed Information | You can view detailed information of the PVC. |
| YAML | The PVC resource file can be edited in the YAML editor- Click the Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, you can click the Diff button to view the changed content
|
| event | Check events that occurred within the PVC |
| Account information | Check basic information about the Account, such as name, location, and creation time. |
| metadata information | Check the metadata information of the PVC |
| Object Information | Check PVC object information |
Table. PVC detailed information items
Delete PVC
To delete a PVC, follow these steps.
- All Services > Container > Kubernetes Engine click the menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click PVC under the Storage menu. 2. Navigate to the PVC List page.
- On the PVC list page, select the cluster and namespace from the list at the top left, then click Query.
- On the PVC List page, select the items you want to delete. 4. PVC Details Navigate to the page.
- On the PVC Details page, click Delete PVC.
- When the notification confirmation window appears, click the Confirm button.
Caution
After selecting the item you want to delete on the PVC list page, click Delete to delete the selected PVC.
- Before deleting the PVC, verify the backup status of the PV and volume to be removed.
Managing PV
Persistent Volume (PV) refers to the physical disk that a system administrator creates in the Kubernetes Engine.
Create PV
To create a PV, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click PV under the Storage menu. 2. Go to the PV list page.
- On the PV List page, after selecting the cluster and namespace from the list at the top left, click Create Object.
- In the Object Creation Popup, enter the object information and click the Create button.
Reference
For detailed information on the concept of PVs and object creation, refer to
쿠버네티스 공식 문서 > 퍼시스턴트 볼륨.
Check PV detailed information
To view detailed PV information, follow these steps.
- All Services > Container > Kubernetes Engine Click the menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- Service Home page, click PV under the Storage menu. 2. Navigate to the PV list page.
- On the PV List page, after selecting the cluster and namespace from the list at the top left, click Search.
- Select the item you want to view detailed information for on the PV List page. 4. PV Details Navigate to the page.
- If you select Show system objects at the top of the list, all items except the Kubernetes object entries are displayed.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Status indicator | Displays the current status of the PV. |
| Delete PV | Delete PV |
| Detailed Information | Detailed PV information can be viewed. |
| YAML | The PV’s resource file can be edited in the YAML editor- Click the Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, click the Diff button to view the changes
|
| event | Check events that occurred within the PV |
| Account information | Check basic information about the Account, such as name, location, and creation time. |
| metadata information | Check the PV metadata information |
| Object Information | Check the PV’s object information |
Table. PV detailed information items
Delete PV
To delete a PV, follow these steps.
- All Services > Container > Kubernetes Engine menu, click it. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click PV under the Storage menu. 2. Navigate to the PV list page.
- PV List page, after selecting the cluster and namespace from the list at the top left, click Search.
- Select the item you want to delete on the PV List page. 4. PV Details navigate to the page.
- On the PV Details page, click Delete PV.
- When the notification confirmation window appears, click the Confirm button.
Caution
On the PV list page, after selecting the item you want to delete, click Delete to delete the selected PV.
Managing Storage Classes
Storage Class (Storage Class) is a Kubernetes resource that defines the type, performance, and other levels of storage.
Reference
Kubernetes Engine provides the nfs-subdir-external-sc and bs-ssd storage classes by default, and has the following characteristics.
- The nfs-subdir-external-sc storage class shares and uses file storage attached to the cluster.
- Access mode: RWX - ReadWriteMany
Reclaim policy: Delete (when PVC is deleted, PV and stored data are deleted together), Retain (when PVC is deleted, PV and stored data are retained)
- Volume binding mode: Immediate (creates a PV as soon as the PVC is created or binds to an existing PV)
Capacity expansion: individual PVC expansion not allowed / entire file storage expansion allowed
- The bs-ssd storage class supports using SSD-type volumes in conjunction with the Block Storage product.
- Access mode: RWO - ReadWriteOnce
- Reclaim policy: Delete (when PVC is deleted, PV and stored data are deleted together), Retain (when PVC is deleted, PV and stored data are retained)
- Volume binding mode: WaitForFirstConsumer (wait for PV creation until a Pod using the PVC is created)
Capacity expansion support: individual PVC expansion support (automatic volume expansion in 8 Gi increments)
predefined storage class
| Storage Class | Volume Binding Mode* | Default volume type** | Reclaim Policy*** | Allow volume expansion | Mount options | Remarks |
|---|
| nfs-subdir-external-sc (default) | Immediate | - | Delete | Unsupported | nfsvers=3, noresvport | Associate with the NFS volume selected in “StorageClass setting”. |
| nfs-subdir-external-sc-retain | Immediate | - | Retain | Unsupported | nfsvers=3, noresvport | Associate with the NFS volume selected in “StorageClass setting”. |
| bs-ssd | WaitForFirstConsumer | SSD | Delete | Support | - | VirtualServer > Block Storage integration |
| bs-ssd-retain | WaitForFirstConsumer | SSD | Retain | Support | - | VirtualServer > Block Storage integration |
- To use a storage class other than the default, you need to specify the storage class name in PVC’s spec.storageClassName.
- Users can directly change the default storage class (adjust the storageclass.kubernetes.io/is-default-class: “true” annotation)
Table. Predefined storage class list
Reference
(*) The characteristics of the volume binding mode are as follows.
- Immediate: Create PV at the time the PVC is created (regardless of POD creation)
- WaitForFirstConsumer: Create PV after the POD to be bound is created
(**) For the bs-ssd storage class, you can change the volume type to be used by modifying parameter.type.
- SSD (default): standard SSD Block Storage type
- SSD_Provisioned: max_iops, max_throughput configurable type (see “Block Storage Storage Class Usage” for detailed usage)
(***) The characteristics of the reclamation policy are as follows.
- Delete: If you delete the PVC, the associated PV and physical data will also be deleted.
- Retain: Even if the PVC is deleted, the associated PV and physical data are not deleted and are retained. * Physical data not used by the workload may remain in storage, so careful capacity management is required.
Caution
When using volume expansion, consider the following.
- nfs-subdir-external-sc storage class
- Cannot adjust the PVC’s capacity. * (Volume expansion not supported)
- All PVs share the total capacity of the File Storage volume, so expanding the volume for each PVC is not required.
- bs-ssd storage class
- You can expand the PVC capacity. * (Zoom function not supported)
- A PVC’s requested capacity does not guarantee that the corresponding PV will have that amount of capacity. * (Support expansion in 8 Gi units)
Caution
Consider the following when using Multi-AvailabilityZone.
- nfs-subdir-external-sc storage class
- Cannot specify the AZ where the volume will be created
- PV can be mounted on nodes in any AZ, regardless of the AZ assigned to the File Storage.
- bs-ssd storage class
- You can specify the AZ where the volume and Pod are created by setting allowedTopologies in the StorageClass.
- Pod scheduling nodes and volume creation AZ must match. * (Cross-AZ not supported)
Create StorageClass
To create a storage class, follow these steps.
- All Services > Container > Kubernetes Engine Click the menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click StorageClass under the Storage menu. 2. Navigate to the StorageClass List page.
- On the StorageClass List page, select the cluster and namespace from the list in the upper left, then click Create Object.
- In the Object Creation Popup, enter the object information and click the Create button.
Reference
For detailed information on the concept of storage classes and object creation, please refer to
쿠버네티스 공식 문서 > 스토리지 클래스.
Check detailed storage class information
To view detailed information about the StorageClass, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- Service Home page, click StorageClass under the Storage menu. 2. Navigate to the StorageClass List page.
- StorageClass List page, select the cluster and namespace from the list at the top left, then click Search.
- Select the item you want to view detailed information for on the StorageClass List page. 4. Go to the StorageClass Details page.
- If you select Show system objects at the top of the list, all items except the Kubernetes object entries are displayed.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete StorageClass | Delete the storage class |
| Detailed Information | Detailed information of the storage class can be viewed |
| YAML | The resource file of the StorageClass can be edited in the YAML editor- Click the Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, you can click the Diff button to view the changes
|
| event | Check events that occurred within the storage class |
| Account information | Check basic information about the Account, such as name, location, and creation time. |
| metadata information | Check the metadata information of the StorageClass |
| Object Information | Check the object information of the storage class |
Table. StorageClass detailed information items
Delete StorageClass
To delete a StorageClass, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click StorageClass under the Storage menu. 2. Navigate to the StorageClass List page.
- On the StorageClass List page, select the cluster and namespace from the list in the upper left, then click Search.
- Select the items you want to delete on the StorageClass List page. 4. Go to the StorageClass Details page.
- Click Delete StorageClass on the StorageClass Details page.
- Notification dialog appears, click the Confirm button.
Caution
If you delete the storage class referenced by a PVC in use, the following issue may occur.
- PVC deletion, recreation failed
- PVC volume size expansion failure (Block Storage)
- When expanding statefulset replicas and creating an additional PVC, it fails
6 - Configuration Management
When you need to manage values that change inside a container across various environments such as development and production, creating separate images to handle them via environment variables is inconvenient and incurs significant cost waste.
In Kubernetes, you can manage environment variables or configuration values as variables so they can be changed externally and injected when a Pod is created; at this point, you can use ConfigMap and Secret.
Reference
ConfigMaps and Secret services default to the cluster (namespace) selected when the service is created. Even if you select a different item in the list, the default cluster (namespace) setting is retained.
- To select a different cluster (namespace), click the list in the top-left corner of the list page. * Select the cluster and namespace to modify from the list and click the View button. * You can view the services created in the selected cluster/namespace.
Managing ConfigMaps
You can create and manage the Config information used in a namespace as a ConfigMap.
Create ConfigMap
To create a ConfigMap, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click ConfigMap under the Configuration menu. 2. Go to the ConfigMap List page.
- On the ConfigMap list page, select the cluster and namespace from the list in the upper left, then click Create Object.
- In the Object Creation Popup, enter the object information and click the Create button.
Reference
For detailed information on the concept of ConfigMaps and object creation, refer to the
쿠버네티스 공식 문서 > 컨피그맵.
Check ConfigMap detailed information
To view detailed ConfigMap information, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click ConfigMap under the Configuration menu. 2. Navigate to the ConfigMap List page.
- On the ConfigMap List page, select the cluster and namespace from the list in the upper left, then click View.
- Select the item you want to view detailed information for on the ConfigMap List page. 4. Navigate to the ConfigMap Details page.
- If you select System Object Display at the top of the list, all items except the Kubernetes object entries will be shown.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete ConfigMap | Delete ConfigMap |
| Detailed Information | Detailed ConfigMap information can be viewed |
| YAML | The ConfigMap’s resource file can be edited in the YAML editor- Click the Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, you can click the Diff button to view the changed content
|
| event | Check events that occurred in the ConfigMap |
| Account information | Check basic information about the Account, such as name, location, and creation date/time. |
| Metadata Information | Check the ConfigMap’s metadata information |
| Object Information | Check the object information of the ConfigMap- In Data,
- - -separates rows, and value is displayed in a textarea format - The binary data value outputs its length
|
Table. ConfigMap detailed information items
Delete ConfigMap
To delete a ConfigMap, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click ConfigMap under the Configuration menu. 2. Navigate to the ConfigMap list page.
- ConfigMap List page, after selecting the cluster and namespace from the list in the top‑left corner, click View.
- Select the item you want to delete on the ConfigMap List page. 4. Navigate to the ConfigMap Details page.
- On the ConfigMap Details page, click Delete ConfigMap.
- Notification dialog appears, click the Confirm button.
Caution
On the ConfigMap list page, after selecting the item you want to delete, click Delete to delete the selected ConfigMap.
Manage Secrets
Using secrets allows you to securely store and manage sensitive information such as passwords, OAuth tokens, and SSH keys.
Create Secret
To create a secret, follow these steps.
- All Services > Container > Kubernetes Engine menu, click it. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Secret under the Configuration menu. 2. Go to the Secret List page.
- Secret List page, after selecting the cluster and namespace from the list at the top left, click Create Object.
- Enter the object information in the Object Creation Popup and click the Create button.
Reference
For detailed information on the concept of Secrets and object creation, refer to the
쿠버네티스 공식 문서 > 시크릿.
Check secret detailed information
To view the secret details, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Secret under the Configuration menu. 2. Navigate to the Secret List page.
- On the Secret List page, select the cluster and namespace from the list at the top left, then click View.
- Select the item you want to view details for on the Secret List page. 4. Navigate to the Secret Detail page.
- If you select System Object Display at the top of the list, all items except the Kubernetes object entries will be shown.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete Secret | Delete the secret |
| Detailed Information | You can view detailed information of the secret |
| YAML | The secret’s resource file can be edited in the YAML editor- Click the Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, you can click the Diff button to view the changed content
|
| event | Check events that occurred within the secret |
| Account Information | Check basic information about the Account, such as its name, location, and creation date/time. |
| metadata information | Check the metadata information of the secret |
| Object Information | Check the secret object’s information |
Table. Secret detailed information items
Delete Secret
To delete the secret, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Secret under the Configuration menu. 2. Go to the Secret List page.
- Secret List page, select the cluster and namespace from the list at the top left, then click View.
- Select the item you want to delete on the Secret List page. 4. Go to the Secret Detail page.
- On the Secret Details page, click Delete Secret.
- Notification dialog appears, click the Confirm button.
Caution
On the secret list page, after selecting the item you want to delete, click Delete to remove the selected secret.
7 - Manage Permissions
When multiple users access a Kubernetes cluster, you can assign permissions for specific APIs or namespaces to define access scopes. You can apply Kubernetes’ role-based access control (RBAC, Role-based access control) feature to set permissions for each cluster or namespace.
You can create and manage ClusterRoles, ClusterRoleBindings, Roles, and RoleBindings.
Reference
ClusterRole, ClusterRoleBinding, Role, and RoleBinding services are set by default to the cluster (namespace) selected when creating the service. Even if you select a different item in the list, the default cluster (namespace) setting is retained.
- To select a different cluster (namespace), click the list in the top‑left corner of the list page. * Select the cluster and namespace to modify from the list and click the View button. * You can view the services created in the selected cluster/namespace.
Managing Cluster Roles
You can set and manage access permissions on a per-cluster basis. You can also set permissions for APIs or resources that are not limited to a namespace.
Create ClusterRole
To create a cluster role, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Cluster Role under the Permissions menu. 2. Go to the Cluster role list page.
- Cluster Role List page, after selecting the cluster and namespace from the list at the top left, click Create Object.
- Enter the object information in the Object Creation Popup and click the Create button.
Reference
For detailed information about ClusterRoles, refer to the
쿠버네티스 공식 문서 > Using RBAC Authorization.
Check detailed information of the cluster role
To view detailed information about the cluster role, follow these steps.
- All Services > Container > Kubernetes Engine menu, click it. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Cluster Role under the Permissions menu. 2. Go to the Cluster role list page.
- Cluster Role List page, select the cluster and namespace from the list at the top left, then click Search.
- Select the item you want to view detailed information for on the Cluster Role List page. 4. Navigate to the Cluster role details page.
- If you select System Object Display at the top of the list, all items except the Kubernetes object entries will be shown.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete ClusterRole | Delete the cluster role |
| Detailed Information | Detailed information of the cluster role can be viewed |
| YAML | The resource file of the ClusterRole can be edited in the YAML editor- Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, click the Diff button to view the changed content
|
| event | Check events that occurred within the cluster role |
| Account information | Check basic information about the Account, such as name, location, and creation timestamp. |
| Metadata Information | Check the metadata information of the ClusterRole |
| Policy Rule Information | View the policy rule information of a ClusterRole- Resources: List of resources to which the rule applies
- Non-Resource URLs: Non-Resource URLs are the set of partial URLs that a user needs to access
* is allowed but only as the final segment of the path
- Since non-resource URLs are not namespaced, this field can only be applied to a ClusterRole referenced by a ClusterRoleBinding
- A rule can apply to an API resource (e.g., “pods” or “secrets”) or a non-resource URL path (e.g., “/api”), but not to both
- Resource Names: Resource names are an optional whitelist of names to which the rule applies. An empty set means everything is allowed
- Verbs: Verbs refer to the API verbs used in resource requests such as get, list, create, update, patch, watch, delete, deletecollection
|
Table. Cluster role detailed information items
Delete cluster role
To delete the cluster role, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Cluster Role under the Permissions menu. 2. Go to the Cluster role list page.
- Cluster Role List page, after selecting the cluster and namespace from the list at the top left, click Search.
- On the Cluster role list page, select the items you want to delete. 4. Navigate to the Cluster role details page.
- On the Cluster Role Details page, click Delete Cluster Role.
- Notification dialog appears, click the Confirm button.
Caution
On the cluster role list page, after selecting the item you want to delete, click Delete to delete the selected cluster role.
Managing ClusterRoleBinding
You can create and manage a cluster role binding by linking a cluster role with a specific target.
Create ClusterRoleBinding
To create a ClusterRoleBinding, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click ClusterRoleBinding under the Permissions menu. 2. Go to the Cluster Role Binding List page.
- Cluster Role Binding List On the page, after selecting the cluster and namespace from the list at the top left, click Create Object.
- Enter the object information in the Object Creation Popup and click the Create button.
Reference
For detailed information about ClusterRoleBinding, refer to the
쿠버네티스 공식 문서 > Using RBAC Authorization.
View detailed information of ClusterRoleBinding
To view detailed information about the ClusterRoleBinding, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click ClusterRoleBinding under the Permissions menu. 2. Navigate to the Cluster Role Binding List page.
- On the Cluster Role Binding List page, select the cluster and namespace from the list at the top left, then click Search.
- Cluster Role Binding List page, select the item for which you want to view detailed information. 4. Navigate to the Cluster Role Binding Details page.
- If you select System Object Display at the top of the list, all items except the Kubernetes object entries will be shown.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete ClusterRoleBinding | Delete the cluster role binding |
| Detailed Information | View detailed information of the ClusterRoleBinding |
| YAML | The resource file of the cluster role binding can be edited in the YAML editor- Edit button, modify the resource, and then click the Done button to apply the changes
- When editing content, click the Diff button to view the changes
|
| event | Check the events that occurred within the ClusterRoleBinding |
| Account information | Check basic information about the Account, such as name, location, and creation timestamp. |
| Metadata Information | Check the metadata information of the ClusterRoleBinding |
| Role/Target Information | Check the role and target information of the ClusterRole |
Table. ClusterRoleBinding detailed information items
Delete ClusterRoleBinding
To delete a ClusterRoleBinding, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click ClusterRoleBinding under the Permissions menu. 2. Navigate to the Cluster Role Binding List page.
- Cluster Role Binding List page, select the cluster and namespace from the list at the top left, then click View.
- Select the item you want to delete on the Cluster Role Binding List page. 4. Go to the Cluster Role Binding Details page.
- On the Cluster Role Binding Details page, click Delete Cluster Role Binding.
- Notification dialog appears, click the Confirm button.
Caution
On the ClusterRoleBinding list page, after selecting the item you want to delete, click Delete to remove the selected ClusterRoleBinding.
Manage roles
A role refers to a rule that specifies permissions for a particular API or resource. You can create and manage permissions that allow access only to the namespace to which the role belongs.
Create role
To create a role, follow the steps below.
- All Services > Container > Kubernetes Engine menu, click it. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Role under the Permission menu. 2. Go to the Roll List page.
- On the Role List page, after selecting the cluster and namespace from the list in the upper left, click Create Object.
- Enter the object information in the Object Creation Popup and click the Create button.
Reference
For detailed information about roles, see the
쿠버네티스 공식 문서 > Using RBAC Authorization.
Check detailed roll information
To view detailed roll information, follow the steps below.
- Click the All Services > Container > Kubernetes Engine menu. 1. Navigate to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Role under the Permission menu. 2. Go to the Role List page.
- Roll List page, after selecting the cluster and namespace from the list at the top left, click View.
- Roll List page, select the item you want to view detailed information for. 4. Roll Details page is accessed.
- Selecting Show system objects at the top of the list displays all items except the Kubernetes object entries.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete role | Delete the role |
| Detailed Information | View detailed information of the roll |
| YAML | Roll’s resource file can be edited in the YAML editor- Click the Edit button, modify the resource, then click the Done button to apply the changes
- When editing content, click the Diff button to view the changed content
|
| event | Check events that occurred within LoL |
| Account information | Check basic information about the Account, such as name, location, creation date and time, etc. |
| Metadata Information | Check the metadata information of LoL |
| Policy Rule Information | Check the policy rule information for a Role- Resources: List of resources to which the rule applies
- Non-Resource URLs: Non-Resource URLs are the set of partial URLs that a user must access
* is allowed, but only as the final segment of the entire path
- Since non-resource URLs are not namespaced, this field can only be applied to a ClusterRole referenced by a ClusterRoleBinding
- A rule can apply to an API resource (e.g., “pods” or “secrets”) or a non-resource URL path (e.g., “/api”), but not to both
- Resource Names: Resource names are an optional whitelist of names to which the rule applies; an empty set means everything is allowed
- Verbs: Verbs are the API actions used in resource requests such as get, list, create, update, path, watch, delete, deletecollection
|
Table. Role detailed information items
Delete role
To delete the role, follow the steps below.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Role under the Permissions menu. 2. Go to the Role List page.
- On the Roll List page, select the cluster and namespace from the list at the top left, then click View.
- On the Role List page, select the item you want to delete. 4. Navigate to the Roll Details page.
- On the Roll Details page, click Delete Roll.
- When the Notification dialog appears, click the Confirm button.
Caution
On the role list page, after selecting the item you want to delete, click Delete to delete the selected role.
Managing Role Bindings
You can create and manage role bindings by linking a role to a specific subject.
Create Role Binding
To create a roll binding, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Role Binding under the Permissions menu. 2. Go to the Roll Binding List page.
- On the Roll Binding List page, select the cluster and namespace from the list at the top left, then click Create Object.
- In the Object Creation Popup, enter the object information and click the Create button.
Reference
For detailed information about role binding, see the
쿠버네티스 공식 문서 > Using RBAC Authorization.
Check detailed information of role binding
To view detailed Roll Binding information, follow these steps.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Role Binding under the Permissions menu. 2. Go to the Roll Binding List page.
- On the Roll Binding List page, select the cluster and namespace from the list in the upper left, then click Search.
- Roll Binding List page, select the item you want to view detailed information for. 4. Go to the Roll Binding Details page.
- If you select Show System Objects at the top of the list, all items except the Kubernetes object entries will be displayed.
- Click each tab to view the service information.
| Category | Detailed description |
|---|
| Delete roll binding | Delete roll binding |
| Detailed Information | View detailed information of roll binding |
| YAML | The resource file of RollBinding can be edited in a YAML editor- Click the Edit button, edit the resource, and then click the Done button to apply the changes
- When editing content, click the Diff button to view the changes
|
| event | Check events that occurred within the role binding |
| Account information | Check basic information about the Account, such as its name, location, and creation date/time. |
| Metadata Information | Check the metadata information of the roll binding |
| Role/Target Information | Check the role’s responsibilities and target information. |
Table. RoleBinding detailed information items
Delete Role Binding
To delete the roll binding, follow the steps below.
- Click the All Services > Container > Kubernetes Engine menu. 1. Go to the Service Home page of Kubernetes Engine.
- On the Service Home page, click Role Binding under the Permissions menu. 2. Go to the Roll Binding List page.
- On the Roll Binding List page, select the cluster and namespace from the list in the upper left, then click View.
- Select the item you want to delete on the Roll Binding List page. 4. Go to the Roll Binding Details page.
- On the Roll Binding Details page, click Delete Roll Binding.
- Notification dialog appears, click the Confirm button.
Caution
After selecting the item you want to delete on the role binding list page, click Delete to delete the selected role binding.