fix

config/daemon.json_cpu

 {
-   "insecure-registries":["harbor_host"]
+    "registry-mirrors": ["https://hub-mirror.c.163.com","https://rrkngb5t.mirror.aliyuncs.com"],
+    "insecure-registries":["harbor_host"]
 }
+

config/nvidia-device-plugin.yml

-apiVersion: extensions/v1beta1
+# Copyright (c) 2019, NVIDIA CORPORATION.  All rights reserved.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+apiVersion: apps/v1
 kind: DaemonSet
 metadata:
   name: nvidia-device-plugin-daemonset
   namespace: kube-system
 spec:
+  selector:
+    matchLabels:
+      name: nvidia-device-plugin-ds
+  updateStrategy:
+    type: RollingUpdate
   template:
     metadata:
-      # Mark this pod as a critical add-on; when enabled, the critical add-on scheduler
-      # reserves resources for critical add-on pods so that they can be rescheduled after
-      # a failure.  This annotation works in tandem with the toleration below.
+      # This annotation is deprecated. Kept here for backward compatibility
+      # See https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/
       annotations:
         scheduler.alpha.kubernetes.io/critical-pod: ""
       labels:
         name: nvidia-device-plugin-ds
     spec:
       tolerations:
-      # Allow this pod to be rescheduled while the node is in "critical add-ons only" mode.
-      # This, along with the annotation above marks this pod as a critical add-on.
+      # This toleration is deprecated. Kept here for backward compatibility
+      # See https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/
       - key: CriticalAddonsOnly
         operator: Exists
+      - key: nvidia.com/gpu
+        operator: Exists
+        effect: NoSchedule
+      # Mark this pod as a critical add-on; when enabled, the critical add-on
+      # scheduler reserves resources for critical add-on pods so that they can
+      # be rescheduled after a failure.
+      # See https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/
+      priorityClassName: "system-node-critical"
       containers:
-      - image: harbor_host/k8s/k8s-device-plugin:1.10
+      - image: harbor_host/k8s/k8s-device-plugin:1.0.0-beta4
         name: nvidia-device-plugin-ctr
         securityContext:
           allowPrivilegeEscalation: false

script/seetaas/2-replace-file.sh

@@ -64,3 +64,6 @@ sed -i s#hub.kce.ksyun.com/kpl_k8s/ubuntu-basic:16.04#$harbor_host/k8s/ubuntu-ba
 sed -i s#hub.kce.ksyun.com/kpl_k8s/image-proxy:v0.9.2#$harbor_host/k8s/image-proxy:v0.9.2#g `find $workspace  -maxdepth 5 -name Dockerfile -type f`
 sed -i s#hub.kce.ksyun.com/kpl_k8s/nginx:latest#$harbor_host/k8s/nginx#g `find $workspace  -maxdepth 5 -name Dockerfile -type f`
 sed -i s#hub.kce.ksyun.com/kpl_k8s/cuda:10.0-base-ubuntu16.04#$harbor_host/k8s/cuda:10.0-base-ubuntu16.04#g `find $workspace  -maxdepth 5 -name Dockerfile -type f`
+###################################修改launcher部署的harbor_host模板#######################################
+sed -i s#harbor_host#$harbor_host#g $workspace/src/kpl-launcher/deploy.sh
+