starlingx/vault-armada-app
Code Issues Proposed changes

adjust livenessProbe intervals

Browse Source 
A proposed set of solutions to high platform CPU usage requests
livenessProbe intervals to be greater than 10 and not a multiple of 5.
It is also requested that timeout values be more forgiving at greater
than 5 seconds.

livenessProbe is enabled by default for vault injector and vault
manager.  Vault-manager is not a high performance component, so use
rather large intervals.  Keep vault injector closer to the requested
threshold.

Test plan:
PASS  selected values are presented in pod spec during runtime

Story: 2011073
Task: 50887

Change-Id: I72a335957ec88fcc7f2a0c417da6815b363934ba
Signed-off-by: Michel Thebeau <Michel.Thebeau@windriver.com>
This commit is contained in:
Michel Thebeau 2024-08-21 13:22:30 +00:00
parent adc792cd48
commit 4e0c5bfaf2
2 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
stx-vault-helm/stx-vault-helm/fluxcd-manifests/vault-manager/vault-manager-static-overrides.yaml
View File

@ -18,3 +18,7 @@ manager:
unsealWaitIntervals: 0 unsealWaitIntervals: 0
imagePullSecrets: imagePullSecrets:
- name: default-registry-key - name: default-registry-key
livenessProbe:
initialDelaySeconds: 31
periodSeconds: 23
timeoutSeconds: 13

4
stx-vault-helm/stx-vault-helm/fluxcd-manifests/vault/vault-static-overrides.yaml
View File

@ -38,6 +38,10 @@ injector:
- key: "node-role.kubernetes.io/control-plane" - key: "node-role.kubernetes.io/control-plane"
operator: "Exists" operator: "Exists"
effect: "NoSchedule" effect: "NoSchedule"
livenessProbe:
initialDelaySeconds: 11
periodSeconds: 11
timeoutSeconds: 7
server: server:
affinity: | affinity: |
podAntiAffinity: podAntiAffinity: