Remove pod resource spec for ptp-notification

The daemonset of ptp-notification was configured with explicit resource
requests. The ptp-notification application is configured to run on
dedicated platform cores and was improperly causing them to count
against the overall k8s not resources. Removing the explicit resource
configuration will correct this. It is not required for the normal
operation of this application.

Closes-Bug: 1927971

Signed-off-by: Cole Walker <cole.walker@windriver.com>
Change-Id: If7414052c70b55947d05b5a46d32eaa003ea56eb

stx-ptp-notification-helm/stx-ptp-notification-helm/helm-charts/ptp-notification/templates/daemonset.yaml

@@ -89,10 +89,6 @@ spec:
         volumeMounts:
           - name: scripts
             mountPath: /mnt
-        resources:
-          limits:
-            cpu: {{ .Values.resources.cpu }}
-            memory: {{ .Values.resources.memory }}
       - name: {{ .Chart.Name }}-ptptracking
         image: "{{ .Values.ptptracking.image.repository }}:{{ .Values.ptptracking.image.tag }}"
         imagePullPolicy: {{ .Values.ptptracking.image.pullPolicy }}
@@ -153,10 +149,6 @@ spec:
           - name: conf
             mountPath: /ptp/
             readOnly: true
-        resources:
-          limits:
-            cpu: {{ .Values.resources.cpu }}
-            memory: {{ .Values.resources.memory }}
       volumes:
         - name: scripts
           configMap:

stx-ptp-notification-helm/stx-ptp-notification-helm/helm-charts/ptp-notification/values.yaml

@@ -16,10 +16,6 @@ replicaCount: 1
 nameOverride: ""
 fullnameOverride: ""
 
-resources:
-  cpu: 1
-  memory: 2Gi
-
 global:
   namespace: notification