starlingx/ptp-notification-armada-app
Code Issues Proposed changes

Fix logic for disabling v1 api container

Browse Source 
The existing logic in the daemonset template was removing several of the
required volume mounts and resulting in a failure to create the pods.
The fix preserves the volume mounts even if the v1 notification is
disabled.

Test-plan:
PASS: Build and deploy ptp-notification
PASS: Enable/disable v1/v2 api containers

Story: 2010538
Task: 47557

Signed-off-by: Cole Walker <cole.walker@windriver.com>
Change-Id: Iee6dacbf36e038c61de9450ca15e5cdc135d97aa
This commit is contained in:
Cole Walker 2023-02-28 13:01:15 -05:00
parent f8984796e3
commit 6ab1d6010f
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
stx-ptp-notification-helm/stx-ptp-notification-helm/helm-charts/ptp-notification/templates/daemonset.yaml
View File

@ -247,6 +247,7 @@ spec:
- name: conf
mountPath: /ptp/
readOnly: true
{{ end }}
volumes:
- name: scripts
configMap:
@ -287,7 +288,6 @@ spec:
hostPath:
path: /sys/
type: Directory
{{ end }}
tolerations:
- key: "node-role.kubernetes.io/master"
operator: "Exists"