ducoterra
ef9104c796
All checks were successful
Reese's Arch Toolbox / build-and-push-arch-toolbox (push) Successful in 14s
52 lines
1.5 KiB
YAML
52 lines
1.5 KiB
YAML
service:
|
|
# Don't use an external IP address
|
|
type: ClusterIP
|
|
|
|
ingress:
|
|
enabled: true
|
|
pathType: Prefix
|
|
# Change this
|
|
hostname: wordpress.reeseapps.com
|
|
annotations:
|
|
# Get a cert from letsencrypt
|
|
cert-manager.io/cluster-issuer: letsencrypt
|
|
# Use the nginx ingress class
|
|
kubernetes.io/ingress.class: nginx
|
|
# Allow infinitely large uploads (change this)
|
|
nginx.ingress.kubernetes.io/proxy-body-size: "0"
|
|
nginx.org/client-max-body-size: "0"
|
|
tls: true
|
|
|
|
resources:
|
|
# namespaces have strict "request" requirements
|
|
requests:
|
|
cpu: 100m
|
|
memory: 128Mi
|
|
# limits are unbounded - allow some breathing room
|
|
limits:
|
|
cpu: 2
|
|
memory: 1Gi
|
|
|
|
updateStrategy:
|
|
# Since the default storage is single-node mount we can't
|
|
# use the typical rolling update strategy because the new
|
|
# pod might try to start on a node without the storage
|
|
# mounted. We can get around this by tearing down the old
|
|
# pod before spinning up the new one. This will result in
|
|
# down time, we can also change the default storage to
|
|
# fix this.
|
|
type: Recreate
|
|
|
|
# These tolerations ensure that if one of my nodes goes down
|
|
# for some reason your pods will jump to the next available
|
|
# node within 1 second of it being unreachable.
|
|
tolerations:
|
|
- key: "node.kubernetes.io/unreachable"
|
|
operator: "Exists"
|
|
effect: "NoExecute"
|
|
tolerationSeconds: 1
|
|
- key: "node.kubernetes.io/not-ready"
|
|
operator: "Exists"
|
|
effect: "NoExecute"
|
|
tolerationSeconds: 1
|