-
Bug
-
Resolution: Unresolved
-
Medium
-
None
Actually OOM relies on simple TCP port check for readiness
readinessProbe:
tcpSocket:
port: {{ .Values.service.internalPort }}
initialDelaySeconds: {{ .Values.readiness.initialDelaySeconds }}
periodSeconds: {{ .Values.readiness.periodSeconds }}
This would show SDNC container as ready, but karaf is not really up and running --> see SDNC-1475
We should use existing service /ready which checks status of karaf features.
readinessProbe:
httpGet:
path: /ready
port: {{ .Values.service.internalPort }}
till now ready-service is part of wt-features and is not available if sdnr.enabled=false
Task: provide ready service as default feature.
As soon as this is confirmed and available please raise request for OOM