base
contains the base image with some scripts, qemu and dnsmasqcentos7
adds a vagrant centos7 box to the imagecli
contains a tool for provisioning, running and managing the containerized clustersk8s-1.9.3
k8s-1.9.3 cluster based on the centos7 image, provisioned with kubeadmk8s-1.10.3
k8s-1.10.3 cluster based on the centos7 image, provisioned with kubeadmk8s-1.10.4
k8s-1.10.4 cluster based on the centos7 image, provisioned with kubeadmk8s-1.11.0
k8s-1.11.0 cluster based on the centos7 image, provisioned with kubeadmk8s-multus-1.10.4:
: k8s-1.10.4 cluster based on the centos7 image and uses multus CNI, provisioned with kubeadmk8s-multus-1.11.1:
: k8s-1.11.1 cluster based on the centos7 image and uses multus CNI, provisioned with kubeadmk8s-multus-1.12.2:
: k8s-1.12.2 cluster based on the centos7 image and uses multus CNI, provisioned with kubeadmk8s-genie-1.11.1:
: k8s-1.11.1 cluster based on the centos7 image and uses genie CNI, provisioned with kubeadmos-3.9
os-3.9 cluster based on the centos7 image, provisioned with openshift-ansibleos-3.9-crio
os-3.9 cluster with CRI-O support based on the centos7 image, provisioned with openshift-ansibleos-3.10.0
os-3.10.0 cluster based on the centos7 image, provisioned with openshift-ansibleos-3.10-crio
os-3.10 cluster with CRI-O support based on the centos7 image, provisioned with openshift-ansibleos-3.10-multus
os-3.10 cluster with multus cni support based on the centos7 image, provisioned with openshift-ansibleos-3.11.0
os-3.11.0 cluster based on the centos7 image, provisioned with openshift-ansibleos-3.11-crio
os-3.11 cluster with CRI-O support based on the centos7 image, provisionedos-3.11-multus
os-3.11 cluster with multus cni support based on the centos7 image, provisioned with openshift-ansible
kubevirtci/cli
:sha256:1dd015dea4f12e6dcb8e31be3eeb677fed96f290ef4a4892a33c43d666053536
kubevirtci/gocli
:sha256:2ff1e9cddfa2cfdf268301a52d1a5ec252ace6908196609e001844e5458b746a
kubevirtci/base
:sha256:034de1a154409d87498050ccc281d398ce1a0fed32efdbd66d2041a99a46b322
kubevirtci/centos:1804_02
:sha256:70653d952edfb8002ab8efe9581d01960ccf21bb965a9b4de4775c8fbceaab39
- Deprecated:
kubevirtci/os-3.9.0:
:sha256:234b3ae5c335c9fa32fa3bc01d5833f8f4d45420d82a8f8b12adc02687eb88b1
- Deprecated:
kubevirtci/os-3.9.0-crio:
:sha256:107d03dad4da6957e28774b121a45e177f31d7b4ad43c6eab7b24d467e59e213
- Deprecated:
kubevirtci/os-3.10.0:
:sha256:cc418c0c837d8e6c9a31a063762d9e4c8bfc70a1fcca10823b11c6d8a7ae2394
- Deprecated:
kubevirtci/os-3.10.0-crio:
:sha256:56debd7bc2ce87dd616ebc30f06971e388b6983c0cda8646a7563e1dafadb69b
- Deprecated:
kubevirtci/os-3.10.0-multus
:sha256:875c973099141ab2013aaf51ec2b35b5326be943ef1437e4a87e041405e724ca
kubevirtci/os-3.11.0-multus
:sha256:46155f973cb4637be5f73cf0307bb09e4caf5c66bd921cf5d1988db2598a8995
kubevirtci/os-3.11.0:
:sha256:2d0a8f59dfebe181f550c4fbcd90d491a56a7d642d761c32a3c7732644325c0b
kubevirtci/os-3.11.0-crio:
:sha256:3f11a6f437fcdf2d70de4fcc31e0383656f994d0d05f9a83face114ea7254bc0
- Deprecated:
kubevirtci/k8s-1.9.3:
:sha256:f6ffb23261fb8aa15ed45b8d17e1299e284ea75e1d2814ee6b4ec24ecea6f24b
- Deprecated:
kubevirtci/k8s-1.10.3:
:sha256:d6290260e7e6b84419984f12719cf592ccbe327373b8df76aa0481f8ec01d357
kubevirtci/k8s-1.10.4:
:sha256:2ed70abfa8f6c30d990b76b816577040c0709258cbbd7c70f71a70d547f5544f
kubevirtci/k8s-1.11.0:
:sha256:e02ec414c7673a3644b5ba742b550a124c9195eaacb280151406bf9e8201a95f
- Deprecated:
kubevirtci/k8s-multus-1.10.4:
:sha256:1d16d436347fcb9eba28cad08f6e074d4628e9a097a7325eb1ab87351e7f6d5c
- Deprecated:
kubevirtci/k8s-multus-1.11.1:
:sha256:3d35b19105344e270be168920e98287fbefcd5366fdf78681712d05725204559
kubevirtci/k8s-multus-1.12.2:
:sha256:4974496beb19a30156c125d7721912b54a705926dcbf66c41f570dca286996ba
kubevirtci/k8s-genie-1.11.1:
:sha256:bd62afe346d81f5d3bc0dd3255aaaaa3ae4d91787de2db3ecd94cc22f809b587
gocli
is a tiny go binary which helps managing the containerized clusters. It
ca be used from a docker images, so no need to install it. You can for instance
use a bash alias:
alias gocli="docker run --net=host --privileged --rm -it -v /var/run/docker.sock:/var/run/docker.sock kubevirtci/gocli:latest"
gocli help
Start a k8s cluster which contains of one master and two nodes:
gocli run --random-ports --nodes 3 --background kubevirtci/k8s-1.10.3
Find out the connection details of the cluster:
$ gocli ports k8s
33396
$ gocli scp /etc/kubernetes/admin.conf - > ./kubeconfig
$ kubectl --kubeconfig ./kubeconfig --insecure-skip-tls-verify --server https://localhost:33396 get pods -n kube-system
NAME READY STATUS RESTARTS AGE
etcd-node01 1/1 Running 0 14m
kube-apiserver-node01 1/1 Running 0 13m
kube-controller-manager-node01 1/1 Running 0 14m
kube-dns-6f4fd4bdf-mh6nb 3/3 Running 0 14m
kube-flannel-ds-4bk76 1/1 Running 0 14m
kube-flannel-ds-5zgmt 1/1 Running 1 14m
kube-flannel-ds-qbm2r 1/1 Running 1 14m
kube-proxy-gtvpb 1/1 Running 0 14m
kube-proxy-knc6p 1/1 Running 0 14m
kube-proxy-vx9t6 1/1 Running 0 14m
kube-scheduler-node01 1/1 Running 0 13m
or to permamently edit kubeconfig:
$ gocli ports k8s
33396
$ gocli scp /etc/kubernetes/admin.conf - > ./kubeconfig
$ kubectl --kubeconfig=./kubeconfig config set-cluster kubernetes --server=https://127.0.0.1:33396
$ kubectl --kubeconfig=./kubeconfig config set-cluster kubernetes --insecure-skip-tls-verify=true
$ kubectl --kubeconfig ./kubeconfig get pods -n kube-system
NAME READY STATUS RESTARTS AGE
etcd-node01 1/1 Running 0 14m
kube-apiserver-node01 1/1 Running 0 13m
kube-controller-manager-node01 1/1 Running 0 14m
kube-dns-6f4fd4bdf-mh6nb 3/3 Running 0 14m
kube-flannel-ds-4bk76 1/1 Running 0 14m
kube-flannel-ds-5zgmt 1/1 Running 1 14m
kube-flannel-ds-qbm2r 1/1 Running 1 14m
kube-proxy-gtvpb 1/1 Running 0 14m
kube-proxy-knc6p 1/1 Running 0 14m
kube-proxy-vx9t6 1/1 Running 0 14m
kube-scheduler-node01 1/1 Running 0 13m
$ gocli rm
Start a k8s cluster which contains of one master and two nodes:
gocli run --random-ports --nodes 2 --memory 5120M --reverse --ocp-port 8443 --background kubevirtci/os-3.11.0
Note the extra --reverse
flag. Normally we start the master first and nodes
register. In the case of openshift it is different. We first need to start the
nodes, so that openshift-ansible can reach out to the nodes from master.
Furter we added --ocp-port 8443
. That is only required if you want to access
the openshift-web-console. More about that further below.
Find out the connection details of the cluster:
$ gocli ports k8s
8443
$ gocli scp /etc/origin/master/admin.kubeconfig - > ./kubeconfig
$ oc --kubeconfig=./kubeconfig config set-cluster node01:8443 --server=127.0.0.1:8443
$ oc --kubeconfig=./kubeconfig config set-cluster node01:8443 --insecure-skip-tls-verify=true
$ oc --kubeconfig ./kubeconfig get nodes
Make sure that node01
resolves to 127.0.0.1
and that you added --ocp-port 8443
when creatin the cluster. If you did that, you can simply access the
webconsole at https://127.0.0.1:8443
. The login credentials are
admin:admin
.
The two preconditions are necessary to make the authentication redirects work.
$ gocli rm