chore: adjust versioning on example and test yamls?

Author: jpayne3506

.pipelines/mdnc/azure-cns-cni.yaml

@@ -107,7 +107,7 @@ spec:
               mountPath: /etc/cni/net.d
       containers:
         - name: cns-container
-          image: mcr.microsoft.com/containernetworking/azure-cns:v1.4.32
+          image: mcr.microsoft.com/containernetworking/azure-cns:v1.4.32 # <Does this need to be updated?>
           imagePullPolicy: IfNotPresent
           args: [ "-c", "tcp://$(CNSIpAddress):$(CNSPort)", "-t", "$(CNSLogTarget)"]
           volumeMounts:
@@ -140,7 +140,7 @@ spec:
               valueFrom:
                   fieldRef:
                     apiVersion: v1
-                    fieldPath: spec.nodeName 
+                    fieldPath: spec.nodeName
       hostNetwork: true
       volumes:
         - name: azure-endpoints

cns/azure-cns-windows.yaml

@@ -30,13 +30,13 @@ spec:
           hostProcess: true
           runAsUserName: "NT AUTHORITY\\SYSTEM"
       containers:
-        - name: cns-container
+        - name: cns-container # <does this need to be updated?>
           image: acnpublic.azurecr.io/azure-cns:v1.4.26-9-gc40fb852
           imagePullPolicy: IfNotPresent
           securityContext:
             privileged: true
           command: "azure-cns.exe"
-          args: 
+          args:
             [
               '-c', "tcp://$(CNSIpAddress):$(CNSPort)",
               '-t', "$(CNSLogTarget)",
@@ -71,7 +71,7 @@ spec:
               valueFrom:
                 fieldRef:
                   apiVersion: v1
-                  fieldPath: spec.nodeName 
+                  fieldPath: spec.nodeName
       hostNetwork: true
       volumes:
         - name: log

cns/azure-cns.yaml

@@ -96,7 +96,7 @@ spec:
           effect: NoSchedule
       containers:
         - name: cns-container
-          image: mcr.microsoft.com/containernetworking/azure-cns:v1.4.7
+          image: mcr.microsoft.com/containernetworking/azure-cns:v1.4.7 # <does this need to be updated?>
           imagePullPolicy: IfNotPresent
           args: [ "-c", "tcp://$(CNSIpAddress):$(CNSPort)", "-t", "$(CNSLogTarget)"]
           volumeMounts:
@@ -129,7 +129,7 @@ spec:
               valueFrom:
                   fieldRef:
                     apiVersion: v1
-                    fieldPath: spec.nodeName 
+                    fieldPath: spec.nodeName
       hostNetwork: true
       volumes:
         - name: azure-endpoints

npm/azure-npm.yaml

@@ -79,7 +79,7 @@ spec:
           operator: Exists
       containers:
         - name: azure-npm
-          image: mcr.microsoft.com/containernetworking/azure-npm:v1.4.45.3
+          image: mcr.microsoft.com/containernetworking/azure-npm:v1.4.45.3 # <does this need to be updated?>
           resources:
             limits:
               cpu: 250m

npm/deploy/kustomize/overlays/controller/deployment.yaml

@@ -36,7 +36,7 @@ spec:
             containerPort: 10091
           - name: http
             containerPort: 10092
-          image:  mcr.microsoft.com/containernetworking/azure-npm:v1.4.1
+          image:  mcr.microsoft.com/containernetworking/azure-npm:v1.4.1 # <does this need to be updated?>
           command: ["azure-npm"]
           args: ["controlplane"]
           resources:

npm/deploy/kustomize/overlays/daemon/deployment.yaml

@@ -34,7 +34,7 @@ spec:
           ports:
           - name: metrics
             containerPort: 10091
-          image:  mcr.microsoft.com/containernetworking/azure-npm:v1.4.1
+          image:  mcr.microsoft.com/containernetworking/azure-npm:v1.4.1 # <does this need to be updated?>
           command: ["azure-npm"]
           args: ["daemon"]
           resources:

npm/deploy/manifests/controller/azure-npm.yaml

@@ -84,7 +84,7 @@ metadata:
   namespace: kube-system
 spec:
   ports:
-  - name: http 
+  - name: http
     port: 9001
     targetPort: 10092
   selector:
@@ -133,12 +133,12 @@ spec:
     spec:
       containers:
       - args:
-        - controlplane 
+        - controlplane
         ports:
         - name: metrics
-          containerPort: 10091 
+          containerPort: 10091
         - name: http
-          containerPort: 10092 
+          containerPort: 10092
         command:
         - azure-npm
         env:
@@ -149,7 +149,7 @@ spec:
               fieldPath: spec.nodeName
         - name: NPM_CONFIG
           value: /etc/azure-npm/azure-npm.json
-        image:  mcr.microsoft.com/containernetworking/azure-npm:v1.4.1
+        image:  mcr.microsoft.com/containernetworking/azure-npm:v1.4.1 # <does this need to be updated?>
         name: azure-npm
         resources:
           limits:

npm/deploy/manifests/daemon/azure-npm.yaml

@@ -135,7 +135,7 @@ spec:
               valueFrom:
                 fieldRef:
                   fieldPath: spec.nodeName
-          image:  mcr.microsoft.com/containernetworking/azure-npm:v1.4.1
+          image:  mcr.microsoft.com/containernetworking/azure-npm:v1.4.1 # <does this need to be updated?>
           name: azure-npm
           ports:
             - name: metrics

npm/deploy/npm/azure-npm.yaml

@@ -34,7 +34,7 @@ rules:
       - watch
 ---
 apiVersion: rbac.authorization.k8s.io/v1
-kind: ClusterRoleBinding  
+kind: ClusterRoleBinding
 metadata:
   name: azure-npm-binding
   namespace: kube-system
@@ -79,7 +79,7 @@ spec:
         operator: Exists
       containers:
         - name: azure-npm
-          image: mcr.microsoft.com/containernetworking/azure-npm:v1.4.1
+          image: mcr.microsoft.com/containernetworking/azure-npm:v1.4.1 # <does this need to be updated?>
           resources:
             limits:
               cpu: 250m

npm/examples/azure-npm-lite.yaml

@@ -79,7 +79,7 @@ spec:
           operator: Exists
       containers:
         - name: azure-npm
-          image: mcr.microsoft.com/containernetworking/azure-npm:v1.4.45.3
+          image: mcr.microsoft.com/containernetworking/azure-npm:v1.4.45.3 # <does this need to be updated?>
           resources:
             limits:
               cpu: 250m