This is pretty common knowledge if you have any experience working with kubernetes. Some less common knowledge: Do your pre-startup config with a shell script

This is pretty common knowledge if you have any experience working with kubernetes. Some less common knowledge: Do your pre-startup config with a shell script and then `exec` your process. If you need some sort of process manager, use supervisord and configure stdout/stderr capture and forwarding. Supervisord will do anything you need from init in a container. If you're running a jvm in the container, set the dns cache ttl in the java security config. Sometimes it's very useful to include a preStop hook that will end your process and then sleep for N seconds so that your process unbinds its listening socket and then for a period of time the pod will respond to incoming SYNs with a RST. So your upstream app doesn't sit there waiting on a timeout because for various reasons it still made new connection attempts despite the pod being removed from the service endpoints or w/e. Fix your resolver configs. ndots. timeout. retry. Remove all the hosts search domains by setting `--resolv-conf=/dev/null` in your kubelet options. Then set dnsConfig.options in your pod spec. While you're at it, set `--allowed-unsafe-sysctls 'net.ipv4.tcp.keepalive*'` so you can configure your pods with sane values. Update pod spec with securityContext.sysctls to set the per pod values. Update the kubelet before applying that pod spec because lol if you don't... (your pods do not inherit these values from the host! So if you think you've set them, you're probably wrong.)