Platform Center
Home / Platform management / Safety management / Node isolation strategy (Alpha) / Create a node isolation policy

Create a node isolation policy

Create node isolation policies for the current cluster to grant exclusive access to the nodes in the subgroup to the specified projects, thereby restricting the nodes on which Pods can run and achieving physical resource isolation between projects.

Create a node isolation policy

  1. In the left navigation pane, click Safety and security > Node isolation strategy.

  2. Click on Create a node isolation policy.

  3. Refer to the following instructions to configure the relevant parameters.

    Parameter Description
    Exclusive Project Whether to enable or disable the switch for making the project exclusive in the strategy configuration. Click to enable or disable. It is enabled by default.
    When the switch is enabled, only Pods under the configured project in the strategy can run on the nodes included in the strategy. When the switch is disabled, Pods under other projects in the current cluster can also run on the nodes included in the strategy, except for the projects in the strategy.
    The project The projects that can use the nodes configured in the strategy.
    Click the drop-down selection box under The project, and click the checkbox before the project name to select multiple projects.
    Note:
    Only one node isolation strategy can be set for a project. If a project has already set a node isolation strategy, it cannot be selected.
    Supports keyword filtering and project filtering in the drop-down selection box.
    Node The IP address of the computing node allocated to the project in the strategy.
    Click the drop-down selection box under Node, and click the checkbox before the node name to select multiple nodes.
    Note:
    One node can only belong to one isolation strategy. If a node already belongs to another node isolation strategy, it cannot be selected.
    Supports keyword filtering and node filtering in the drop-down selection box.

  4. Click Create.

    Note:

  5. This document provides an overview of the Kubernetes infrastructure and the cloud-native industry.

  6. Kubernetes is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications.

  7. The cloud-native industry refers to the use of cloud computing technologies and principles to build and run scalable applications in a distributed environment.

  8. Cloud-native applications are designed to be resilient, scalable, and portable across different cloud providers.

  9. Kubernetes provides a set of APIs and tools for managing containerized applications, including features for automatic scaling, load balancing, and service discovery.

  10. The Kubernetes architecture consists of a master node and multiple worker nodes. The master node is responsible for managing the cluster and scheduling tasks, while the worker nodes run the containerized applications.

  11. Kubernetes uses a declarative approach to application management, where users define the desired state of their applications and Kubernetes ensures that the actual state matches the desired state.

  12. Kubernetes supports various deployment strategies, including rolling updates, blue-green deployments, and canary deployments, to minimize downtime and ensure smooth application updates.

  13. The cloud-native industry is rapidly evolving, with new technologies and best practices emerging regularly. Staying up-to-date with the latest trends and advancements is crucial for organizations looking to leverage the benefits of cloud-native architectures.

  14. In conclusion, Kubernetes and the cloud-native industry provide a powerful foundation for building and running scalable, resilient, and portable applications in a distributed environment.

    • After the policy is created, existing Pods within the project that do not comply with the current policy will be rescheduled to the nodes included in the current policy after reconstruction.

    • Exclusive Project When enabled, existing Pods on the current node will not be automatically evicted. If eviction is required, it needs to be manually scheduled.

Remove the node isolation policy

Note: After removing the node isolation strategy, the project will no longer be restricted to running on specific nodes, and the nodes will no longer be dedicated to the project.

  1. In the left navigation pane, click Safety and security > Node isolation strategy.

  2. Find the node isolation strategy and click on > Delete.