28ac1b3395
Use the systemd $NOTIFY_SOCKET convention for kube-apiserver startup. This allows it to be part of dependency trees and for consumers to wait until it is listening on its ports. The $NOTIFY_SOCKET protocol is described here: http://www.freedesktop.org/software/systemd/man/sd_notify.html Currently this is limited to the kube-apiserver process. Other kube processes are internal kubernetes moving points. The API server is the entry point relied on by callers. 100% stolen from Stef Walter from: https://github.com/GoogleCloudPlatform/kubernetes/pull/8316
26 lines
580 B
Desktop File
26 lines
580 B
Desktop File
[Unit]
|
|
Description=Kubernetes API Server
|
|
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
|
|
|
|
[Service]
|
|
EnvironmentFile=-/etc/kubernetes/config
|
|
EnvironmentFile=-/etc/kubernetes/apiserver
|
|
User=kube
|
|
ExecStart=/usr/bin/kube-apiserver \
|
|
$KUBE_LOGTOSTDERR \
|
|
$KUBE_LOG_LEVEL \
|
|
$KUBE_ETCD_SERVERS \
|
|
$KUBE_API_ADDRESS \
|
|
$KUBE_API_PORT \
|
|
$KUBELET_PORT \
|
|
$KUBE_ALLOW_PRIV \
|
|
$KUBE_SERVICE_ADDRESSES \
|
|
$KUBE_ADMISSION_CONTROL \
|
|
$KUBE_API_ARGS
|
|
Restart=on-failure
|
|
Type=notify
|
|
LimitNOFILE=65536
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|