主机节点的信息为：
[root@master-node ~]# kubectl get node -o wide --show-labels
NAME          STATUS   ROLES                      AGE      VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                                        KERNEL-VERSION                               CONTAINER-RUNTIME   LABELS
10.20.1.130   Ready    controlplane,etcd,worker   2y272d   v1.20.4   10.20.1.130   <none>        openEuler 20.03 (LTS-SP3)                       4.19.90-2209.1.0.0166.oe1.x86_64             docker://20.10.15   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,ingress-deploy=true,kubernetes.io/arch=amd64,kubernetes.io/hostname=10.20.1.130,kubernetes.io/os=linux,node-role.kubernetes.io/controlplane=true,node-role.kubernetes.io/etcd=true,node-role.kubernetes.io/worker=true,uavcloud.env=demo
10.20.1.133   Ready    worker                     2y272d   v1.20.4   10.20.1.133   <none>        openEuler 20.03 (LTS-SP3)                       4.19.90-2209.1.0.0166.oe1.x86_64             docker://20.10.15   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=10.20.1.133,kubernetes.io/os=linux,node-role.kubernetes.io/worker=true,uavcloud.env=demo
10.20.1.134   Ready    worker                     2y272d   v1.20.4   10.20.1.134   <none>        openEuler 20.03 (LTS-SP3)                       4.19.90-2209.1.0.0166.oe1.x86_64             docker://20.10.15   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=10.20.1.134,kubernetes.io/os=linux,mysql-deploy=true,node-role.kubernetes.io/worker=true
10.20.1.141   Ready    worker                     510d     v1.20.4   10.20.1.141   <none>        BigCloud Enterprise Linux For Euler 21.10 LTS   4.19.90-2107.6.0.0192.8.oe1.bclinux.x86_64   docker://20.10.15   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,ingress-deploy=true,kubernetes.io/arch=amd64,kubernetes.io/hostname=10.20.1.141,kubernetes.io/os=linux,node-role.kubernetes.io/worker=true,uavcloud.env=demo
10.20.1.142   Ready    worker                     510d     v1.20.4   10.20.1.142   <none>        BigCloud Enterprise Linux For Euler 21.10 LTS   4.19.90-2107.6.0.0192.8.oe1.bclinux.x86_64   docker://20.10.15   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,ingress-deploy=true,kubernetes.io/arch=amd64,kubernetes.io/hostname=10.20.1.142,kubernetes.io/os=linux,node-role.kubernetes.io/worker=true,uavcloud.env=demo
10.20.1.144   Ready    worker                     510d     v1.20.4   10.20.1.144   <none>        BigCloud Enterprise Linux For Euler 21.10 LTS   4.19.90-2107.6.0.0192.8.oe1.bclinux.x86_64   docker://20.10.15   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,ingress-deploy=true,kubernetes.io/arch=amd64,kubernetes.io/hostname=10.20.1.144,kubernetes.io/os=linux,node-role.kubernetes.io/worker=true,uavcloud.env=demo
10.20.1.145   Ready    worker                     510d     v1.20.4   10.20.1.145   <none>        BigCloud Enterprise Linux For Euler 21.10 LTS   4.19.90-2107.6.0.0192.8.oe1.bclinux.x86_64   docker://20.10.15   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,ingress-deploy=true,kubernetes.io/arch=amd64,kubernetes.io/hostname=10.20.1.145,kubernetes.io/os=linux,node-role.kubernetes.io/worker=true,uavcloud.env=demo

我现在的需求是
1. 需要清退10.20.1.142，10.20.1.144 10.20.1.145这几台机器，但是要在一个月之后，
2. jxyd内部的deployment的生命周期与这几台机器的周期相同
3. jxyd内部的中间件可以保留，后续其他的平台需要使用，因此需要调度到 10.20.1.133 10.20.1.134 10.20.1.141之上
4. 需要检查每个deployment的资源信息
   1. 如果现在的资源比这个大，需要统一调整为 resources:
      limits:
      cpu: '2'
      memory: 2Gi
      requests:
      cpu: '1'
      memory: 500Mi
   2. 调整中需要同步修改 container的 -env:
       - name: CUST_JAVA_OPTS
         value: '-Xms500m -Xmx2000m -Dlog4j2.formatMsgNoLookups=true'

请你结合上面的需求，给我完整解决方案, 可以使用python3 shell kubectl结合的方式