3586986416
This is the 2nd attempt. The previous was reverted while we figured out the regional mirrors (oops). New plan: k8s.gcr.io is a read-only facade that auto-detects your source region (us, eu, or asia for now) and pulls from the closest. To publish an image, push k8s-staging.gcr.io and it will be synced to the regionals automatically (similar to today). For now the staging is an alias to gcr.io/google_containers (the legacy URL). When we move off of google-owned projects (working on it), then we just do a one-time sync, and change the google-internal config, and nobody outside should notice. We can, in parallel, change the auto-sync into a manual sync - send a PR to "promote" something from staging, and a bot activates it. Nice and visible, easy to keep track of.
111 lines
2.8 KiB
YAML
111 lines
2.8 KiB
YAML
# RBAC authn and authz
|
|
apiVersion: v1
|
|
kind: ServiceAccount
|
|
metadata:
|
|
name: elasticsearch-logging
|
|
namespace: kube-system
|
|
labels:
|
|
k8s-app: elasticsearch-logging
|
|
kubernetes.io/cluster-service: "true"
|
|
addonmanager.kubernetes.io/mode: Reconcile
|
|
---
|
|
kind: ClusterRole
|
|
apiVersion: rbac.authorization.k8s.io/v1
|
|
metadata:
|
|
name: elasticsearch-logging
|
|
labels:
|
|
k8s-app: elasticsearch-logging
|
|
kubernetes.io/cluster-service: "true"
|
|
addonmanager.kubernetes.io/mode: Reconcile
|
|
rules:
|
|
- apiGroups:
|
|
- ""
|
|
resources:
|
|
- "services"
|
|
- "namespaces"
|
|
- "endpoints"
|
|
verbs:
|
|
- "get"
|
|
---
|
|
kind: ClusterRoleBinding
|
|
apiVersion: rbac.authorization.k8s.io/v1
|
|
metadata:
|
|
namespace: kube-system
|
|
name: elasticsearch-logging
|
|
labels:
|
|
k8s-app: elasticsearch-logging
|
|
kubernetes.io/cluster-service: "true"
|
|
addonmanager.kubernetes.io/mode: Reconcile
|
|
subjects:
|
|
- kind: ServiceAccount
|
|
name: elasticsearch-logging
|
|
namespace: kube-system
|
|
apiGroup: ""
|
|
roleRef:
|
|
kind: ClusterRole
|
|
name: elasticsearch-logging
|
|
apiGroup: ""
|
|
---
|
|
# Elasticsearch deployment itself
|
|
apiVersion: apps/v1
|
|
kind: StatefulSet
|
|
metadata:
|
|
name: elasticsearch-logging
|
|
namespace: kube-system
|
|
labels:
|
|
k8s-app: elasticsearch-logging
|
|
version: v5.6.4
|
|
kubernetes.io/cluster-service: "true"
|
|
addonmanager.kubernetes.io/mode: Reconcile
|
|
spec:
|
|
serviceName: elasticsearch-logging
|
|
replicas: 2
|
|
selector:
|
|
matchLabels:
|
|
k8s-app: elasticsearch-logging
|
|
version: v5.6.4
|
|
template:
|
|
metadata:
|
|
labels:
|
|
k8s-app: elasticsearch-logging
|
|
version: v5.6.4
|
|
kubernetes.io/cluster-service: "true"
|
|
spec:
|
|
serviceAccountName: elasticsearch-logging
|
|
containers:
|
|
- image: k8s.gcr.io/elasticsearch:v5.6.4
|
|
name: elasticsearch-logging
|
|
resources:
|
|
# need more cpu upon initialization, therefore burstable class
|
|
limits:
|
|
cpu: 1000m
|
|
requests:
|
|
cpu: 100m
|
|
ports:
|
|
- containerPort: 9200
|
|
name: db
|
|
protocol: TCP
|
|
- containerPort: 9300
|
|
name: transport
|
|
protocol: TCP
|
|
volumeMounts:
|
|
- name: elasticsearch-logging
|
|
mountPath: /data
|
|
env:
|
|
- name: "NAMESPACE"
|
|
valueFrom:
|
|
fieldRef:
|
|
fieldPath: metadata.namespace
|
|
volumes:
|
|
- name: elasticsearch-logging
|
|
emptyDir: {}
|
|
# Elasticsearch requires vm.max_map_count to be at least 262144.
|
|
# If your OS already sets up this number to a higher value, feel free
|
|
# to remove this init container.
|
|
initContainers:
|
|
- image: alpine:3.6
|
|
command: ["/sbin/sysctl", "-w", "vm.max_map_count=262144"]
|
|
name: elasticsearch-logging-init
|
|
securityContext:
|
|
privileged: true
|