Qiming
9bf026e951
There are many YAML manifests sneaking into the `zh/docs/` directory. These files should go to the `zh/examples` directory instead. Having these "garbage" files (not referenced anywhere) is creating confusion for the release meister when merging branches. For example, some YAML files found in the 'master' branch are no longer there in the release-1.16 branch. It is tedious, if possible at all, to solve all this kind of conflicts during a rebase. The PR cleanses the zh/docs directory for all dangling YAML files.
101 lines
2.5 KiB
YAML
101 lines
2.5 KiB
YAML
apiVersion: apps/v1
|
|
kind: StatefulSet
|
|
metadata:
|
|
name: cassandra
|
|
labels:
|
|
app: cassandra
|
|
spec:
|
|
serviceName: cassandra
|
|
replicas: 3
|
|
selector:
|
|
matchLabels:
|
|
app: cassandra
|
|
template:
|
|
metadata:
|
|
labels:
|
|
app: cassandra
|
|
spec:
|
|
terminationGracePeriodSeconds: 1800
|
|
containers:
|
|
- name: cassandra
|
|
image: gcr.io/google-samples/cassandra:v13
|
|
imagePullPolicy: Always
|
|
ports:
|
|
- containerPort: 7000
|
|
name: intra-node
|
|
- containerPort: 7001
|
|
name: tls-intra-node
|
|
- containerPort: 7199
|
|
name: jmx
|
|
- containerPort: 9042
|
|
name: cql
|
|
resources:
|
|
limits:
|
|
cpu: "500m"
|
|
memory: 1Gi
|
|
requests:
|
|
cpu: "500m"
|
|
memory: 1Gi
|
|
securityContext:
|
|
capabilities:
|
|
add:
|
|
- IPC_LOCK
|
|
lifecycle:
|
|
preStop:
|
|
exec:
|
|
command:
|
|
- /bin/sh
|
|
- -c
|
|
- nodetool drain
|
|
env:
|
|
- name: MAX_HEAP_SIZE
|
|
value: 512M
|
|
- name: HEAP_NEWSIZE
|
|
value: 100M
|
|
- name: CASSANDRA_SEEDS
|
|
value: "cassandra-0.cassandra.default.svc.cluster.local"
|
|
- name: CASSANDRA_CLUSTER_NAME
|
|
value: "K8Demo"
|
|
- name: CASSANDRA_DC
|
|
value: "DC1-K8Demo"
|
|
- name: CASSANDRA_RACK
|
|
value: "Rack1-K8Demo"
|
|
- name: POD_IP
|
|
valueFrom:
|
|
fieldRef:
|
|
fieldPath: status.podIP
|
|
readinessProbe:
|
|
exec:
|
|
command:
|
|
- /bin/bash
|
|
- -c
|
|
- /ready-probe.sh
|
|
initialDelaySeconds: 15
|
|
timeoutSeconds: 5
|
|
# These volume mounts are persistent. They are like inline claims,
|
|
# but not exactly because the names need to match exactly one of
|
|
# the stateful pod volumes.
|
|
volumeMounts:
|
|
- name: cassandra-data
|
|
mountPath: /cassandra_data
|
|
# These are converted to volume claims by the controller
|
|
# and mounted at the paths mentioned above.
|
|
# do not use these in production until ssd GCEPersistentDisk or other ssd pd
|
|
volumeClaimTemplates:
|
|
- metadata:
|
|
name: cassandra-data
|
|
spec:
|
|
accessModes: [ "ReadWriteOnce" ]
|
|
storageClassName: fast
|
|
resources:
|
|
requests:
|
|
storage: 1Gi
|
|
---
|
|
kind: StorageClass
|
|
apiVersion: storage.k8s.io/v1
|
|
metadata:
|
|
name: fast
|
|
provisioner: k8s.io/minikube-hostpath
|
|
parameters:
|
|
type: pd-ssd
|