summary |
shortlog |
log |
commit | commitdiff |
review |
tree
raw |
patch |
inline | side by side (from parent 1:
e5f9156)
The timeouts for Stargate are too small for a proper
startup
Issue-ID: OOM-3226
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: I3235a1022d9c5380d3110c62e42a6f62cc13f001
tag: {{ .Values.k8ssandraOperator.stargate.tag }}
size: {{ .Values.k8ssandraOperator.stargate.size }}
heapSize: {{ .Values.k8ssandraOperator.stargate.jvmOptions.heapSize }}
tag: {{ .Values.k8ssandraOperator.stargate.tag }}
size: {{ .Values.k8ssandraOperator.stargate.size }}
heapSize: {{ .Values.k8ssandraOperator.stargate.jvmOptions.heapSize }}
+ livenessProbe:
+ initialDelaySeconds: 200
+ periodSeconds: 10
+ failureThreshold: 20
+ successThreshold: 1
+ timeoutSeconds: 20
+ readinessProbe:
+ initialDelaySeconds: 200
+ periodSeconds: 10
+ failureThreshold: 20
+ successThreshold: 1
+ timeoutSeconds: 20
cassandra:
serverVersion: {{ .Values.k8ssandraOperator.cassandraVersion }}
storageConfig:
cassandra:
serverVersion: {{ .Values.k8ssandraOperator.cassandraVersion }}
storageConfig: