Don't use hostPort or hostNetwork

There is no need to use a hostPort or the hostNetwork; avoiding hostPort allocation improves compatibility with other cluster monitoring and avoiding hostNetwork ensures public-facing clusters don't have an exploitable ports.
This commit is contained in:
Craig authored and GitHub committed 2019-10-29 18:27:18 +01:00
1 parent 88d2b49ab8
commit 06787ac34c
1 file changed
-2
@@ -25,7 +25,6 @@ spec:
securityContext: securityContext:
runAsNonRoot: true runAsNonRoot: true
runAsUser: 65534 runAsUser: 65534
hostNetwork: true
hostPID: true hostPID: true
containers: containers:
- name: node-exporter - name: node-exporter
@@ -39,7 +38,6 @@ spec:
ports: ports:
- name: metrics - name: metrics
containerPort: 9100 containerPort: 9100
hostPort: 9100
resources: resources:
requests: requests:
cpu: 10m cpu: 10m