Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitAuto: [网络]SpiderPool当子网不对等,创建应用时,需要给workload手动添加节点亲和性,并且匹配子网的节点亲和的信息 #5948

Closed
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/en/docs/network/config/use-ippool/usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,7 @@ This page describes how to configure multiple NICs for workload Pods in combinat
![Manual Selection](https://docs.daocloud.io/daocloud-docs-images/docs/en/docs/network/images/useippool03.png)

Note: If the chosen [IP Pool Creation Time](../ippool/createpool.md) has added node affinity like: `zone:beijing`, please add the corresponding label `zone:beijing` when creating the workload. For use cases, please refer to: [Instructions f../../config/ippool/ippoolusage.mdool](ippoolusage.md)![zone-beijing](https://docs.daocloud.io/daocloud-docs-images/docs/en/docs/network/images/zone-beijing.png)
In case of subnet mismatches, SpiderPool will automatically add the necessary node affinity rules to ensure correct workload scheduling.

**Automatically create fixed IP pool**

Expand Down
1 change: 1 addition & 0 deletions docs/en/docs/network/modules/spiderpool/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ The features provided by SpiderPool are as follows.
| Feature | Description
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Multiple ways to use IP Pool | 1. IP Pools can be associated with namespaces, nodes, and applications via Node Selector. <br />2. You can specify the IP Pool in the Annotation when the application is deployed and get the IP resources in the IP Pool in order of priority. |
| Automatic Node Affinity | Automatically detects subnet configuration mismatches and adds node affinity rules to workloads to ensure correct scheduling. |
| IP Pool's node affinity | Nodes within the same cluster may belong to different data centers or different subnets. Therefore different copies of the same application need to be assigned IP addresses under different subnets for scheduling. The node affinity of IP Pool supports this scenario. |
| IP Pool's namespace affinity | Based on the namespace affinity of IP Pool, the same IP Pool can be shared to multiple Namespaces at the same time. |
| Alternate IP Pool | When the IP address in the IP Pool has been assigned and the corresponding subnet is no longer available, you can create a new subnet and IP Pool and assign it to the application to prevent the application from failing to expand its capacity. |
Expand Down
Loading