Cluster Tagging

The tagging feature allows users to assign custom tags to virtual machines, enabling more efficient classification, search, and management of resources.

• Intelligent Classification: Easily organize virtual machines based on any criteria suitable for your environment (production, staging, development), project, department, or management process.

• Quick Search: Based on tags, users can easily filter and search for VMs without needing to remember complex names.

• Efficient Management: Supports cost tracking, resource usage monitoring, and report generation for each tagged VM group.

• Flexible Customization: Tags are customizable and can be applied for various purposes to meet specific enterprise needs.

The tagging feature enables more scientific management of virtualized infrastructure, saving time and improving system operational efficiency.

In the portal, you can operate the tagging feature as follows:

1. Creating Tags

To tag VMs within an MFKE worker group, users must create tags in advance according to their intended use.

2. Assigning Tags for Using Worker Groups Belonging to M-FKE

2.1. When Creating a New Cluster

Step 1: In Unify Portal, select Kubernetes → Managed → Create a Kubernetes Engine to create a new cluster.

Step 2: Under [Nodes Pool], select the tag to use for the worker group.

Enter all required information for the cluster and click the Create a Kubernetes Engine button.

2.2. Editing Worker Group Tags

Step 1: Select "Containers" > "Kubernetes" from the menu to display the Kubernetes Management page. Select the cluster whose tags you want to edit.

Step 2: Select Node Pools > Edit Workers.

Step 3: Add tags to the worker group and click the [Save] button.

Tag editing completes within a few minutes, and the cluster status changes to "Processing." During this processing, users cannot edit the cluster.

2.3. Removing Tags from a Worker Group

Step 1: Select Node Pools > Edit Workers

Step 2: Click the ❎ mark to remove the tag from the worker group, then click Save.

Tag removal will be executed within a few minutes, and the cluster status will change to "Processing." Users cannot perform cluster editing operations until the process is complete.