Importing and Removing Resources for Native Applications
Native applications greatly facilitate the unified management of computing components, networks, storage, and configurations, but not all resources related to business belong to the application.
-
Resources added during the application creation process, or added through application updates, are by default associated with the application and do not require additional importing.
-
Resources created outside the application do not belong to the application and cannot be found in the application's details. However, as long as the resource definitions meet business requirements, the business can operate normally. In this case, it is recommended that you import the resources into the application for unified management.
Resources imported into the application can benefit from the following features:
| Feature | Description |
|---|---|
| Version Snapshot | When creating a version snapshot for the application, a snapshot will also be generated for the resources within the application.
|
| Deleted with Application | If an application is no longer needed, deleting the application will automatically remove all resources associated with the application, including computing components, internal routes, and inbound rules. |
| Easier to Find | In the application detail information, you can quickly view the resources associated with the application. For example: External traffic can access Deployment D through Service S, which belongs to Application A, but the corresponding access address can only be quickly found in the application details if Service S also belongs to Application A. |
Importing Resources
Batch import related resources under the namespace where the application resides; a resource can belong to only one application.
Steps to Operate
-
Enter Container Platform.
-
In the left navigation bar, click Application Management > Native Applications.
-
Click on Application Name.
-
Click Actions > Manage Resources.
-
In the Resource Type at the bottom, select the type of resources to be imported.
Note: Common resource types include Deployment, DaemonSet, StatefulSet, Job, CronJob, Service, Ingress, PVC, ConfigMap, Secret, and HorizontalPodAutoscaler, which are displayed at the top; other resources are arranged in alphabetical order, and you can quickly query specific resource types by searching keywords.
-
In the Resources section, select the resources to be imported.
Attention: For Job type resources, only tasks created through YAML are supported for import.
-
Click Import Resources.
Removing / Batch Removing Resources
Removing / batch removing resources from an application only disassociates the application from the resources and does not delete the resources.
If there are interconnections between resources under an application, removing any resource from the application will not change the associations between the resources. For example, even if Service S is removed from Application A, external traffic can still access Deployment D through Service S.
Steps to Operate
-
Enter Container Platform.
-
In the left navigation bar, click Application Management > Native Applications.
-
Click on Application Name.
-
Click Actions > Manage Resources.
-
Click Remove on the right side of a resource to remove it; or select multiple resources at once, and click Remove at the top of the table to batch remove resources.