Node Pool Management

    2）Example of Nodepool usage

    • Create a nodepool
    • Get the nodepool information
    1. $ kubectl get np 
    3. NAME       TYPE   READYNODES   NOTREADYNODES   AGE
    4. beijing    Cloud                               35s
    5. hangzhou   Edge                                28s
    • Add node to nodepool
    1. For example:
    2. $ kubectl label node master apps.openyurt.io/desired-nodepool=beijing
    4. master labeled
    • Verify whether a node is added to a nodepool:
    1. $ kubectl get node {Your_Node_Name} -o yaml 
    2. For Example:
    3. $ kubectl get node k8s-node1 -o yaml
    5. apiVersion: v1
    7. metadata:
    8.   annotations:
    9.     apps.openyurt.io/example: test-hangzhou
    10.     kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock
    11.     node.alpha.kubernetes.io/ttl: "0"
    12.     node.beta.alibabacloud.com/autonomy: "true"
    13.     volumes.kubernetes.io/controller-managed-attach-detach: "true"
    14.   creationTimestamp: "2021-04-14T12:17:39Z"
    15.   labels:
    16.     apps.openyurt.io/desired-nodepool: hangzhou
    17.     apps.openyurt.io/example: test-hangzhou
    18.     apps.openyurt.io/nodepool: hangzhou
    19.     beta.kubernetes.io/os: linux
    20.     kubernetes.io/arch: amd64
    22.     kubernetes.io/os: linux
    23.     openyurt.io/is-edge-worker: "true"
    24.   name: k8s-node1
    25.   resourceVersion: "1244431"
    26.   selfLink: /api/v1/nodes/k8s-node1
    27.   uid: 1323f90b-acf3-4443-a7dc-7a54c212506c
    28. spec:
    29.   podCIDR: 192.168.1.0/24
    30.   podCIDRs:
    31.   - 192.168.1.0/24
    32.   taints:
    33.   - effect: NoSchedule
    34.     key: apps.openyurt.io/example
    35.     value: test-hangzhou