[Container-tools] Cross-repo Coordination: Move Kube setup to adb-utils

[Praveen Kumar]

On Tue, Apr 5, 2016 at 2:28 AM, Lalatendu Mohanty <lmohanty at redhat.com> wrote:
> On 04/04/2016 06:02 PM, Brian (bex) Exelbierd wrote:
>
> L#73-103 was a workaround for an upstream issue and the the fix was sent to
> upstream and was merged. However I am not sure which version of K8s has the
> fix. We need to check if the stock  K8s has the fix.

I went ahead and checked with available version for ADB/CDK and seems
like we already have that fix in repo rpm and we don't really need now
this to be part of our kickstart file. Created issue[0] for same to
track it.

#  rpm -qa | grep kube
kubernetes-master-1.2.0-0.6.alpha1.git8632732.el7.x86_64
kubernetes-client-1.2.0-0.6.alpha1.git8632732.el7.x86_64
kubernetes-node-1.2.0-0.6.alpha1.git8632732.el7.x86_64
kubernetes-1.2.0-0.6.alpha1.git8632732.el7.x86_64


# rpm -lq kubernetes-master | grep service
/usr/lib/systemd/system/kube-apiserver.service
/usr/lib/systemd/system/kube-controller-manager.service
/usr/lib/systemd/system/kube-scheduler.service


Service file which is part of stock rpm now

$ cat /usr/lib/systemd/system/kube-apiserver.service
[Unit]
Description=Kubernetes API Server
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
After=network.target
After=etcd.service

[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


Service  file which we include in kickstart

$ cat /etc/systemd/system/kube-apiserver.service
[Unit]
Description=Kubernetes API Server
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
After=network.target

[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
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target


We have to brew a vagrant box after removing those lines from
kickstart and check if that doesn't break anything (which I hope not).

[0] https://github.com/projectatomic/adb-atomic-developer-bundle/issues/318

-- 
Praveen Kumar
http://fedoraproject.org/wiki/User:Kumarpraveen
http://fedoraproject.org/
http://kumar-pravin.blogspot.com