ingress-nginx-helm/examples/static-ip/nginx-ingress-controller.yaml

58 lines
1.8 KiB
YAML
Raw Permalink Normal View History

2019-11-19 04:10:37 +00:00
apiVersion: apps/v1
2018-04-27 00:09:55 +00:00
kind: Deployment
metadata:
2021-11-28 21:12:19 +00:00
name: ingress-nginx-controller
2018-04-27 00:09:55 +00:00
labels:
2018-09-05 12:51:21 +00:00
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/part-of: ingress-nginx
2018-04-27 00:09:55 +00:00
spec:
replicas: 1
selector:
matchLabels:
2018-09-05 12:51:21 +00:00
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/part-of: ingress-nginx
2018-04-27 00:09:55 +00:00
template:
metadata:
labels:
2018-09-05 12:51:21 +00:00
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/part-of: ingress-nginx
2018-04-27 00:09:55 +00:00
spec:
# hostNetwork makes it possible to use ipv6 and to preserve the source IP correctly regardless of docker configuration
2021-11-28 21:12:19 +00:00
# however, it is not a hard dependency of the ingress-nginx-controller itself and it may cause issues if port 10254 already is taken on the host
2018-04-27 00:09:55 +00:00
# that said, since hostPort is broken on CNI (https://github.com/kubernetes/kubernetes/issues/31307) we have to use hostNetwork where CNI is used
# like with kubeadm
# hostNetwork: true
terminationGracePeriodSeconds: 60
containers:
2022-06-10 11:03:34 +00:00
- image: registry.k8s.io/ingress-nginx/controller:v1.0.5
2021-11-28 21:12:19 +00:00
name: controller
2018-04-27 00:09:55 +00:00
readinessProbe:
httpGet:
path: /healthz
port: 10254
scheme: HTTP
livenessProbe:
httpGet:
path: /healthz
port: 10254
scheme: HTTP
initialDelaySeconds: 10
timeoutSeconds: 1
ports:
- containerPort: 80
hostPort: 80
- containerPort: 443
hostPort: 443
env:
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
args:
- /nginx-ingress-controller
2021-11-28 21:12:19 +00:00
- --publish-service=$(POD_NAMESPACE)/ingress-nginx-lb