Skip to content

Instantly share code, notes, and snippets.

@hareeshpc
Last active December 14, 2018 18:16
Show Gist options
  • Select an option

  • Save hareeshpc/2b57ee9a15293fe468bf214a8604f96d to your computer and use it in GitHub Desktop.

Select an option

Save hareeshpc/2b57ee9a15293fe468bf214a8604f96d to your computer and use it in GitHub Desktop.
[hareesh@localhost kubernetes-cluster]$ vagrant up
Bringing machine 'k8s-head' up with 'virtualbox' provider...
Bringing machine 'k8s-node-1' up with 'virtualbox' provider...
Bringing machine 'k8s-node-2' up with 'virtualbox' provider...
==> k8s-head: Box 'ubuntu/xenial64' could not be found. Attempting to find and install...
k8s-head: Box Provider: virtualbox
k8s-head: Box Version: 20180831.0.0
==> k8s-head: Loading metadata for box 'ubuntu/xenial64'
k8s-head: URL: https://vagrantcloud.com/ubuntu/xenial64
==> k8s-head: Adding box 'ubuntu/xenial64' (v20180831.0.0) for provider: virtualbox
k8s-head: Downloading: https://vagrantcloud.com/ubuntu/boxes/xenial64/versions/20180831.0.0/providers/virtualbox.box
k8s-head: Download redirected to host: cloud-images.ubuntu.com
==> k8s-head: Successfully added box 'ubuntu/xenial64' (v20180831.0.0) for 'virtualbox'!
==> k8s-head: Importing base box 'ubuntu/xenial64'...
==> k8s-head: Matching MAC address for NAT networking...
==> k8s-head: Checking if box 'ubuntu/xenial64' is up to date...
==> k8s-head: Setting the name of the VM: k8s-head
Vagrant is currently configured to create VirtualBox synced folders with
the `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrant
guest is not trusted, you may want to disable this option. For more
information on this option, please refer to the VirtualBox manual:
https://www.virtualbox.org/manual/ch04.html#sharedfolders
This option can be disabled globally with an environment variable:
VAGRANT_DISABLE_VBOXSYMLINKCREATE=1
or on a per folder basis within the Vagrantfile:
config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false
==> k8s-head: Vagrant has detected a configuration issue which exposes a
==> k8s-head: vulnerability with the installed version of VirtualBox. The
==> k8s-head: current guest is configured to use an E1000 NIC type for a
==> k8s-head: network adapter which is vulnerable in this version of VirtualBox.
==> k8s-head: Ensure the guest is trusted to use this configuration or update
==> k8s-head: the NIC type using one of the methods below:
==> k8s-head:
==> k8s-head: https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type
==> k8s-head: https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type
==> k8s-head: Clearing any previously set network interfaces...
==> k8s-head: Preparing network interfaces based on configuration...
k8s-head: Adapter 1: nat
k8s-head: Adapter 2: hostonly
==> k8s-head: Forwarding ports...
k8s-head: 22 (guest) => 2222 (host) (adapter 1)
==> k8s-head: Running 'pre-boot' VM customizations...
==> k8s-head: Booting VM...
==> k8s-head: Waiting for machine to boot. This may take a few minutes...
k8s-head: SSH address: 127.0.0.1:2222
k8s-head: SSH username: vagrant
k8s-head: SSH auth method: private key
k8s-head: Warning: Remote connection disconnect. Retrying...
k8s-head:
k8s-head: Vagrant insecure key detected. Vagrant will automatically replace
k8s-head: this with a newly generated keypair for better security.
k8s-head:
k8s-head: Inserting generated public key within guest...
k8s-head: Removing insecure key from the guest if it's present...
k8s-head: Key inserted! Disconnecting and reconnecting using new SSH key...
==> k8s-head: Machine booted and ready!
==> k8s-head: Checking for guest additions in VM...
k8s-head: The guest additions on this VM do not match the installed version of
k8s-head: VirtualBox! In most cases this is fine, but in rare cases it can
k8s-head: prevent things such as shared folders from working properly. If you see
k8s-head: shared folder errors, please make sure the guest additions within the
k8s-head: virtual machine match the version of VirtualBox you have installed on
k8s-head: your host and reload your VM.
k8s-head:
k8s-head: Guest Additions Version: 5.1.38
k8s-head: VirtualBox Version: 5.2
==> k8s-head: Setting hostname...
==> k8s-head: Configuring and enabling network interfaces...
==> k8s-head: Mounting shared folders...
k8s-head: /vagrant => /home/hareesh/Projects_WS/kubernetes-cluster
==> k8s-head: Running provisioner: shell...
k8s-head: Running: inline script
k8s-head: Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
k8s-head: Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
k8s-head: Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
k8s-head: Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
k8s-head: Get:5 http://security.ubuntu.com/ubuntu xenial-security/main Sources [139 kB]
k8s-head: Get:6 http://archive.ubuntu.com/ubuntu xenial/main Sources [868 kB]
k8s-head: Get:7 http://security.ubuntu.com/ubuntu xenial-security/restricted Sources [2,116 B]
k8s-head: Get:8 http://security.ubuntu.com/ubuntu xenial-security/universe Sources [89.7 kB]
k8s-head: Get:9 http://security.ubuntu.com/ubuntu xenial-security/multiverse Sources [2,472 B]
k8s-head: Get:10 http://archive.ubuntu.com/ubuntu xenial/restricted Sources [4,808 B]
k8s-head: Get:11 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [589 kB]
k8s-head: Get:12 http://archive.ubuntu.com/ubuntu xenial/universe Sources [7,728 kB]
k8s-head: Get:13 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [408 kB]
k8s-head: Get:14 http://security.ubuntu.com/ubuntu xenial-security/universe Translation-en [159 kB]
k8s-head: Get:15 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [3,724 B]
k8s-head: Get:16 http://security.ubuntu.com/ubuntu xenial-security/multiverse Translation-en [1,844 B]
k8s-head: Get:17 http://archive.ubuntu.com/ubuntu xenial/multiverse Sources [179 kB]
k8s-head: Get:18 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7,532 kB]
k8s-head: Get:19 http://archive.ubuntu.com/ubuntu xenial/universe Translation-en [4,354 kB]
k8s-head: Get:20 http://archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [144 kB]
k8s-head: Get:21 http://archive.ubuntu.com/ubuntu xenial/multiverse Translation-en [106 kB]
k8s-head: Get:22 http://archive.ubuntu.com/ubuntu xenial-updates/main Sources [327 kB]
k8s-head: Get:23 http://archive.ubuntu.com/ubuntu xenial-updates/restricted Sources [2,528 B]
k8s-head: Get:24 http://archive.ubuntu.com/ubuntu xenial-updates/universe Sources [237 kB]
k8s-head: Get:25 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse Sources [8,744 B]
k8s-head: Get:26 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [892 kB]
k8s-head: Get:27 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [715 kB]
k8s-head: Get:28 http://archive.ubuntu.com/ubuntu xenial-updates/universe Translation-en [292 kB]
k8s-head: Get:29 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages [16.6 kB]
k8s-head: Get:30 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse Translation-en [8,440 B]
k8s-head: Get:31 http://archive.ubuntu.com/ubuntu xenial-backports/main Sources [4,856 B]
k8s-head: Get:32 http://archive.ubuntu.com/ubuntu xenial-backports/universe Sources [6,740 B]
k8s-head: Get:33 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages [7,288 B]
k8s-head: Get:34 http://archive.ubuntu.com/ubuntu xenial-backports/main Translation-en [4,456 B]
k8s-head: Get:35 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages [7,804 B]
k8s-head: Get:36 http://archive.ubuntu.com/ubuntu xenial-backports/universe Translation-en [4,184 B]
k8s-head: Fetched 25.2 MB in 6s (4,178 kB/s)
k8s-head: Reading package lists...
k8s-head: Reading package lists...
k8s-head: Building dependency tree...
k8s-head:
k8s-head: Reading state information...
k8s-head: apt-transport-https is already the newest version (1.2.29).
k8s-head: ca-certificates is already the newest version (20170717~16.04.1).
k8s-head: curl is already the newest version (7.47.0-1ubuntu2.11).
k8s-head: software-properties-common is already the newest version (0.96.20.7).
k8s-head: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
k8s-head: OK
k8s-head: Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
k8s-head: Get:2 https://download.docker.com/linux/ubuntu xenial InRelease [66.2 kB]
k8s-head: Hit:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
k8s-head: Hit:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
k8s-head: Hit:5 http://security.ubuntu.com/ubuntu xenial-security InRelease
k8s-head: Get:6 https://download.docker.com/linux/ubuntu xenial/stable amd64 Packages [5,491 B]
k8s-head: Fetched 71.7 kB in 0s (164 kB/s)
k8s-head: Reading package lists...
k8s-head: Reading package lists...
k8s-head: Building dependency tree...
k8s-head: Reading state information...
k8s-head: The following additional packages will be installed:
k8s-head: aufs-tools cgroupfs-mount libltdl7
k8s-head: Suggested packages:
k8s-head: mountall
k8s-head: The following NEW packages will be installed:
k8s-head: aufs-tools cgroupfs-mount docker-ce libltdl7
k8s-head: 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
k8s-head: Need to get 19.5 MB of archives.
k8s-head: After this operation, 89.4 MB of additional disk space will be used.
k8s-head: Get:1 http://archive.ubuntu.com/ubuntu xenial/universe amd64 aufs-tools amd64 1:3.2+20130722-1.1ubuntu1 [92.9 kB]
k8s-head: Get:2 http://archive.ubuntu.com/ubuntu xenial/universe amd64 cgroupfs-mount all 1.2 [4,970 B]
k8s-head: Get:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 libltdl7 amd64 2.4.6-0.1 [38.3 kB]
k8s-head: Get:4 https://download.docker.com/linux/ubuntu xenial/stable amd64 docker-ce amd64 17.03.3~ce-0~ubuntu-xenial [19.4 MB]
k8s-head: dpkg-preconfigure: unable to re-open stdin: No such file or directory
k8s-head: Fetched 19.5 MB in 3s (5,188 kB/s)
k8s-head: Selecting previously unselected package aufs-tools.
k8s-head: (Reading database ...
(Reading database ... 60%tabase ... 5%
k8s-head: (Reading database ... 65%
k8s-head: (Reading database ... 70%
k8s-head: (Reading database ... 75%
k8s-head: (Reading database ... 80%
k8s-head: (Reading database ... 85%
k8s-head: (Reading database ... 90%
k8s-head: (Reading database ... 95%
(Reading database ... 54192 files and directories currently installed.)
k8s-head: Preparing to unpack .../aufs-tools_1%3a3.2+20130722-1.1ubuntu1_amd64.deb ...
k8s-head: Unpacking aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
k8s-head: Selecting previously unselected package cgroupfs-mount.
k8s-head: Preparing to unpack .../cgroupfs-mount_1.2_all.deb ...
k8s-head: Unpacking cgroupfs-mount (1.2) ...
k8s-head: Selecting previously unselected package libltdl7:amd64.
k8s-head: Preparing to unpack .../libltdl7_2.4.6-0.1_amd64.deb ...
k8s-head: Unpacking libltdl7:amd64 (2.4.6-0.1) ...
k8s-head: Selecting previously unselected package docker-ce.
k8s-head: Preparing to unpack .../docker-ce_17.03.3~ce-0~ubuntu-xenial_amd64.deb ...
k8s-head: Unpacking docker-ce (17.03.3~ce-0~ubuntu-xenial) ...
k8s-head: Processing triggers for libc-bin (2.23-0ubuntu10) ...
k8s-head: Processing triggers for man-db (2.7.5-1) ...
k8s-head: Processing triggers for ureadahead (0.100.0-19) ...
k8s-head: Processing triggers for systemd (229-4ubuntu21.10) ...
k8s-head: Setting up aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
k8s-head: Setting up cgroupfs-mount (1.2) ...
k8s-head: Setting up libltdl7:amd64 (2.4.6-0.1) ...
k8s-head: Setting up docker-ce (17.03.3~ce-0~ubuntu-xenial) ...
k8s-head: Processing triggers for libc-bin (2.23-0ubuntu10) ...
k8s-head: Processing triggers for systemd (229-4ubuntu21.10) ...
k8s-head: Processing triggers for ureadahead (0.100.0-19) ...
k8s-head: Reading package lists...
k8s-head: Building dependency tree...
k8s-head: Reading state information...
k8s-head: apt-transport-https is already the newest version (1.2.29).
k8s-head: curl is already the newest version (7.47.0-1ubuntu2.11).
k8s-head: 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
k8s-head: OK
k8s-head: Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
k8s-head: Hit:2 https://download.docker.com/linux/ubuntu xenial InRelease
k8s-head: Hit:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
k8s-head: Hit:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
k8s-head: Hit:5 http://security.ubuntu.com/ubuntu xenial-security InRelease
k8s-head: Get:6 https://packages.cloud.google.com/apt kubernetes-xenial InRelease [8,993 B]
k8s-head: Get:7 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 Packages [22.0 kB]
k8s-head: Fetched 31.0 kB in 1s (26.3 kB/s)
k8s-head: Reading package lists...
k8s-head: Reading package lists...
k8s-head: Building dependency tree...
k8s-head: Reading state information...
k8s-head: The following additional packages will be installed:
k8s-head: cri-tools ebtables kubernetes-cni socat
k8s-head: The following NEW packages will be installed:
k8s-head: cri-tools ebtables kubeadm kubectl kubelet kubernetes-cni socat
k8s-head: 0 upgraded, 7 newly installed, 0 to remove and 1 not upgraded.
k8s-head: Need to get 45.9 MB of archives.
k8s-head: After this operation, 264 MB of additional disk space will be used.
k8s-head: Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 ebtables amd64 2.0.10.4-3.4ubuntu2.16.04.2 [79.9 kB]
k8s-head: Get:2 http://archive.ubuntu.com/ubuntu xenial/universe amd64 socat amd64 1.7.3.1-1 [321 kB]
k8s-head: Get:3 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 cri-tools amd64 1.12.0-00 [5,343 kB]
k8s-head: Get:4 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubernetes-cni amd64 0.6.0-00 [5,910 kB]
k8s-head: Get:5 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubelet amd64 1.13.1-00 [19.0 MB]
k8s-head: Get:6 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubectl amd64 1.13.1-00 [7,843 kB]
k8s-head: Get:7 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubeadm amd64 1.13.1-00 [7,359 kB]
k8s-head: dpkg-preconfigure: unable to re-open stdin: No such file or directory
k8s-head: Fetched 45.9 MB in 12s (3,800 kB/s)
k8s-head: Selecting previously unselected package cri-tools.
k8s-head: (Reading database ...
k8s-head: (Reading database ... 5%
k8s-head: (Reading database ... 10%
k8s-head: (Reading database ... 15%
k8s-head: (Reading database ... 20%
k8s-head: (Reading database ... 25%
k8s-head: (Reading database ... 30%
k8s-head: (Reading database ... 35%
k8s-head: (Reading database ... 40%
k8s-head: (Reading database ... 45%
k8s-head: (Reading database ... 50%
k8s-head: (Reading database ... 55%
k8s-head: (Reading database ... 60%
k8s-head: (Reading database ... 65%
k8s-head: (Reading database ... 70%
k8s-head: (Reading database ... 75%
k8s-head: (Reading database ... 80%
k8s-head: (Reading database ... 85%
k8s-head: (Reading database ... 90%
k8s-head: (Reading database ... 95%
k8s-head: (Reading database ... 100%
k8s-head: (Reading database ...
k8s-head: 54467 files and directories currently installed.)
k8s-head: Preparing to unpack .../cri-tools_1.12.0-00_amd64.deb ...
k8s-head: Unpacking cri-tools (1.12.0-00) ...
k8s-head: Selecting previously unselected package ebtables.
k8s-head: Preparing to unpack .../ebtables_2.0.10.4-3.4ubuntu2.16.04.2_amd64.deb ...
k8s-head: Unpacking ebtables (2.0.10.4-3.4ubuntu2.16.04.2) ...
k8s-head: Selecting previously unselected package kubernetes-cni.
k8s-head: Preparing to unpack .../kubernetes-cni_0.6.0-00_amd64.deb ...
k8s-head: Unpacking kubernetes-cni (0.6.0-00) ...
k8s-head: Selecting previously unselected package socat.
k8s-head: Preparing to unpack .../socat_1.7.3.1-1_amd64.deb ...
k8s-head: Unpacking socat (1.7.3.1-1) ...
k8s-head: Selecting previously unselected package kubelet.
k8s-head: Preparing to unpack .../kubelet_1.13.1-00_amd64.deb ...
k8s-head: Unpacking kubelet (1.13.1-00) ...
k8s-head: Selecting previously unselected package kubectl.
k8s-head: Preparing to unpack .../kubectl_1.13.1-00_amd64.deb ...
k8s-head: Unpacking kubectl (1.13.1-00) ...
k8s-head: Selecting previously unselected package kubeadm.
k8s-head: Preparing to unpack .../kubeadm_1.13.1-00_amd64.deb ...
k8s-head: Unpacking kubeadm (1.13.1-00) ...
k8s-head: Processing triggers for man-db (2.7.5-1) ...
k8s-head: Processing triggers for systemd (229-4ubuntu21.10) ...
k8s-head: Processing triggers for ureadahead (0.100.0-19) ...
k8s-head: Setting up cri-tools (1.12.0-00) ...
k8s-head: Setting up ebtables (2.0.10.4-3.4ubuntu2.16.04.2) ...
k8s-head: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
k8s-head: Setting up kubernetes-cni (0.6.0-00) ...
k8s-head: Setting up socat (1.7.3.1-1) ...
k8s-head: Setting up kubelet (1.13.1-00) ...
k8s-head: Setting up kubectl (1.13.1-00) ...
k8s-head: Setting up kubeadm (1.13.1-00) ...
k8s-head: Processing triggers for systemd (229-4ubuntu21.10) ...
k8s-head: Processing triggers for ureadahead (0.100.0-19) ...
k8s-head: kubelet set on hold.
k8s-head: kubeadm set on hold.
k8s-head: kubectl set on hold.
==> k8s-head: Running provisioner: shell...
k8s-head: Running: inline script
k8s-head: This is master
k8s-head: [init] Using Kubernetes version: v1.13.1
k8s-head: [preflight] Running pre-flight checks
k8s-head: [preflight] Pulling images required for setting up a Kubernetes cluster
k8s-head: [preflight] This might take a minute or two, depending on the speed of your internet connection
k8s-head: [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
k8s-head: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
k8s-head: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
k8s-head: [kubelet-start] Activating the kubelet service
k8s-head: [certs] Using certificateDir folder "/etc/kubernetes/pki"
k8s-head: [certs] Generating "etcd/ca" certificate and key
k8s-head: [certs] Generating "apiserver-etcd-client" certificate and key
k8s-head: [certs] Generating "etcd/server" certificate and key
k8s-head: [certs] etcd/server serving cert is signed for DNS names [k8s-head localhost] and IPs [192.168.205.10 127.0.0.1 ::1]
k8s-head: [certs] Generating "etcd/peer" certificate and key
k8s-head: [certs] etcd/peer serving cert is signed for DNS names [k8s-head localhost] and IPs [192.168.205.10 127.0.0.1 ::1]
k8s-head: [certs] Generating "etcd/healthcheck-client" certificate and key
k8s-head: [certs] Generating "ca" certificate and key
k8s-head: [certs] Generating "apiserver" certificate and key
k8s-head: [certs] apiserver serving cert is signed for DNS names [k8s-head kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 192.168.205.10 192.168.205.10]
k8s-head: [certs] Generating "apiserver-kubelet-client" certificate and key
k8s-head: [certs] Generating "front-proxy-ca" certificate and key
k8s-head: [certs] Generating "front-proxy-client" certificate and key
k8s-head: [certs] Generating "sa" key and public key
k8s-head: [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
k8s-head: [kubeconfig] Writing "admin.conf" kubeconfig file
k8s-head: [kubeconfig] Writing "kubelet.conf" kubeconfig file
k8s-head: [kubeconfig] Writing "controller-manager.conf" kubeconfig file
k8s-head: [kubeconfig] Writing "scheduler.conf" kubeconfig file
k8s-head: [control-plane] Using manifest folder "/etc/kubernetes/manifests"
k8s-head: [control-plane] Creating static Pod manifest for "kube-apiserver"
k8s-head: [control-plane] Creating static Pod manifest for "kube-controller-manager"
k8s-head: [control-plane] Creating static Pod manifest for "kube-scheduler"
k8s-head: [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
k8s-head: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
k8s-head: [apiclient] All control plane components are healthy after 18.502811 seconds
k8s-head: [uploadconfig] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
k8s-head: [kubelet] Creating a ConfigMap "kubelet-config-1.13" in namespace kube-system with the configuration for the kubelets in the cluster
k8s-head: [patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "k8s-head" as an annotation
k8s-head: [mark-control-plane] Marking the node k8s-head as control-plane by adding the label "node-role.kubernetes.io/master=''"
k8s-head: [mark-control-plane] Marking the node k8s-head as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
k8s-head: [bootstrap-token] Using token: evho0h.odeg35eex9oq9yos
k8s-head: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
k8s-head: [bootstraptoken] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
k8s-head: [bootstraptoken] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
k8s-head: [bootstraptoken] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
k8s-head: [bootstraptoken] creating the "cluster-info" ConfigMap in the "kube-public" namespace
k8s-head: [addons] Applied essential addon: CoreDNS
k8s-head: [addons] Applied essential addon: kube-proxy
k8s-head:
k8s-head: Your Kubernetes master has initialized successfully!
k8s-head:
k8s-head: To start using your cluster, you need to run the following as a regular user:
k8s-head:
k8s-head: mkdir -p $HOME/.kube
k8s-head: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
k8s-head: sudo chown $(id -u):$(id -g) $HOME/.kube/config
k8s-head:
k8s-head: You should now deploy a pod network to the cluster.
k8s-head: Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
k8s-head: https://kubernetes.io/docs/concepts/cluster-administration/addons/
k8s-head:
k8s-head: You can now join any number of machines by running the following on each node
k8s-head: as root:
k8s-head:
k8s-head: kubeadm join 192.168.205.10:6443 --token evho0h.odeg35eex9oq9yos --discovery-token-ca-cert-hash sha256:3c01c63b6bff3adb9da0e37a0bad3bdacf7fc3e856d5d6371c7bc6650aee2b83
k8s-head: clusterrole.rbac.authorization.k8s.io/calico-node created
k8s-head: clusterrolebinding.rbac.authorization.k8s.io/calico-node created
k8s-head: configmap/calico-config created
k8s-head: service/calico-typha created
k8s-head: deployment.apps/calico-typha created
k8s-head: daemonset.extensions/calico-node created
k8s-head: customresourcedefinition.apiextensions.k8s.io/felixconfigurations.crd.projectcalico.org created
k8s-head: customresourcedefinition.apiextensions.k8s.io/bgppeers.crd.projectcalico.org created
k8s-head: customresourcedefinition.apiextensions.k8s.io/bgpconfigurations.crd.projectcalico.org created
k8s-head: customresourcedefinition.apiextensions.k8s.io/ippools.crd.projectcalico.org created
k8s-head: customresourcedefinition.apiextensions.k8s.io/hostendpoints.crd.projectcalico.org created
k8s-head: customresourcedefinition.apiextensions.k8s.io/clusterinformations.crd.projectcalico.org created
k8s-head: customresourcedefinition.apiextensions.k8s.io/globalnetworkpolicies.crd.projectcalico.org created
k8s-head: customresourcedefinition.apiextensions.k8s.io/globalnetworksets.crd.projectcalico.org created
k8s-head: customresourcedefinition.apiextensions.k8s.io/networkpolicies.crd.projectcalico.org created
k8s-head: serviceaccount/calico-node created
==> k8s-node-1: Box 'ubuntu/xenial64' could not be found. Attempting to find and install...
k8s-node-1: Box Provider: virtualbox
k8s-node-1: Box Version: 20180831.0.0
==> k8s-node-1: Loading metadata for box 'ubuntu/xenial64'
k8s-node-1: URL: https://vagrantcloud.com/ubuntu/xenial64
==> k8s-node-1: Adding box 'ubuntu/xenial64' (v20180831.0.0) for provider: virtualbox
==> k8s-node-1: Importing base box 'ubuntu/xenial64'...
==> k8s-node-1: Matching MAC address for NAT networking...
==> k8s-node-1: Checking if box 'ubuntu/xenial64' is up to date...
==> k8s-node-1: Setting the name of the VM: k8s-node-1
==> k8s-node-1: Fixed port collision for 22 => 2222. Now on port 2200.
==> k8s-node-1: Vagrant has detected a configuration issue which exposes a
==> k8s-node-1: vulnerability with the installed version of VirtualBox. The
==> k8s-node-1: current guest is configured to use an E1000 NIC type for a
==> k8s-node-1: network adapter which is vulnerable in this version of VirtualBox.
==> k8s-node-1: Ensure the guest is trusted to use this configuration or update
==> k8s-node-1: the NIC type using one of the methods below:
==> k8s-node-1:
==> k8s-node-1: https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type
==> k8s-node-1: https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type
==> k8s-node-1: Clearing any previously set network interfaces...
==> k8s-node-1: Preparing network interfaces based on configuration...
k8s-node-1: Adapter 1: nat
k8s-node-1: Adapter 2: hostonly
==> k8s-node-1: Forwarding ports...
k8s-node-1: 22 (guest) => 2200 (host) (adapter 1)
==> k8s-node-1: Running 'pre-boot' VM customizations...
==> k8s-node-1: Booting VM...
==> k8s-node-1: Waiting for machine to boot. This may take a few minutes...
k8s-node-1: SSH address: 127.0.0.1:2200
k8s-node-1: SSH username: vagrant
k8s-node-1: SSH auth method: private key
k8s-node-1:
k8s-node-1: Vagrant insecure key detected. Vagrant will automatically replace
k8s-node-1: this with a newly generated keypair for better security.
k8s-node-1:
k8s-node-1: Inserting generated public key within guest...
k8s-node-1: Removing insecure key from the guest if it's present...
k8s-node-1: Key inserted! Disconnecting and reconnecting using new SSH key...
==> k8s-node-1: Machine booted and ready!
==> k8s-node-1: Checking for guest additions in VM...
k8s-node-1: The guest additions on this VM do not match the installed version of
k8s-node-1: VirtualBox! In most cases this is fine, but in rare cases it can
k8s-node-1: prevent things such as shared folders from working properly. If you see
k8s-node-1: shared folder errors, please make sure the guest additions within the
k8s-node-1: virtual machine match the version of VirtualBox you have installed on
k8s-node-1: your host and reload your VM.
k8s-node-1:
k8s-node-1: Guest Additions Version: 5.1.38
k8s-node-1: VirtualBox Version: 5.2
==> k8s-node-1: Setting hostname...
==> k8s-node-1: Configuring and enabling network interfaces...
==> k8s-node-1: Mounting shared folders...
k8s-node-1: /vagrant => /home/hareesh/Projects_WS/kubernetes-cluster
==> k8s-node-1: Running provisioner: shell...
k8s-node-1: Running: inline script
k8s-node-1: Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
k8s-node-1: Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
k8s-node-1: Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
k8s-node-1: Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
k8s-node-1: Get:5 http://security.ubuntu.com/ubuntu xenial-security/main Sources [139 kB]
k8s-node-1: Get:6 http://archive.ubuntu.com/ubuntu xenial/main Sources [868 kB]
k8s-node-1: Get:7 http://security.ubuntu.com/ubuntu xenial-security/restricted Sources [2,116 B]
k8s-node-1: Get:8 http://security.ubuntu.com/ubuntu xenial-security/universe Sources [89.7 kB]
k8s-node-1: Get:9 http://archive.ubuntu.com/ubuntu xenial/restricted Sources [4,808 B]
k8s-node-1: Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse Sources [2,472 B]
k8s-node-1: Get:11 http://archive.ubuntu.com/ubuntu xenial/universe Sources [7,728 kB]
k8s-node-1: Get:12 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [589 kB]
k8s-node-1: Get:13 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [408 kB]
k8s-node-1: Get:14 http://security.ubuntu.com/ubuntu xenial-security/universe Translation-en [159 kB]
k8s-node-1: Get:15 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [3,724 B]
k8s-node-1: Get:16 http://security.ubuntu.com/ubuntu xenial-security/multiverse Translation-en [1,844 B]
k8s-node-1: Get:17 http://archive.ubuntu.com/ubuntu xenial/multiverse Sources [179 kB]
k8s-node-1: Get:18 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7,532 kB]
k8s-node-1: Get:19 http://archive.ubuntu.com/ubuntu xenial/universe Translation-en [4,354 kB]
k8s-node-1: Get:20 http://archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [144 kB]
k8s-node-1: Get:21 http://archive.ubuntu.com/ubuntu xenial/multiverse Translation-en [106 kB]
k8s-node-1: Get:22 http://archive.ubuntu.com/ubuntu xenial-updates/main Sources [327 kB]
k8s-node-1: Get:23 http://archive.ubuntu.com/ubuntu xenial-updates/restricted Sources [2,528 B]
k8s-node-1: Get:24 http://archive.ubuntu.com/ubuntu xenial-updates/universe Sources [237 kB]
k8s-node-1: Get:25 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse Sources [8,744 B]
k8s-node-1: Get:26 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [892 kB]
k8s-node-1: Get:27 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [715 kB]
k8s-node-1: Get:28 http://archive.ubuntu.com/ubuntu xenial-updates/universe Translation-en [292 kB]
k8s-node-1: Get:29 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages [16.6 kB]
k8s-node-1: Get:30 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse Translation-en [8,440 B]
k8s-node-1: Get:31 http://archive.ubuntu.com/ubuntu xenial-backports/main Sources [4,856 B]
k8s-node-1: Get:32 http://archive.ubuntu.com/ubuntu xenial-backports/universe Sources [6,740 B]
k8s-node-1: Get:33 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages [7,288 B]
k8s-node-1: Get:34 http://archive.ubuntu.com/ubuntu xenial-backports/main Translation-en [4,456 B]
k8s-node-1: Get:35 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages [7,804 B]
k8s-node-1: Get:36 http://archive.ubuntu.com/ubuntu xenial-backports/universe Translation-en [4,184 B]
k8s-node-1: Fetched 25.2 MB in 12s (1,947 kB/s)
k8s-node-1: Reading package lists...
k8s-node-1: Reading package lists...
k8s-node-1: Building dependency tree...
k8s-node-1:
k8s-node-1: Reading state information...
k8s-node-1: apt-transport-https is already the newest version (1.2.29).
k8s-node-1: ca-certificates is already the newest version (20170717~16.04.1).
k8s-node-1: curl is already the newest version (7.47.0-1ubuntu2.11).
k8s-node-1: software-properties-common is already the newest version (0.96.20.7).
k8s-node-1: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
k8s-node-1: OK
k8s-node-1: Get:1 https://download.docker.com/linux/ubuntu xenial InRelease [66.2 kB]
k8s-node-1: Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
k8s-node-1: Hit:3 http://security.ubuntu.com/ubuntu xenial-security InRelease
k8s-node-1: Hit:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
k8s-node-1: Hit:5 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
k8s-node-1: Get:6 https://download.docker.com/linux/ubuntu xenial/stable amd64 Packages [5,491 B]
k8s-node-1: Fetched 71.7 kB in 0s (164 kB/s)
k8s-node-1: Reading package lists...
k8s-node-1: Reading package lists...
k8s-node-1: Building dependency tree...
k8s-node-1: Reading state information...
k8s-node-1: The following additional packages will be installed:
k8s-node-1: aufs-tools cgroupfs-mount libltdl7
k8s-node-1: Suggested packages:
k8s-node-1: mountall
k8s-node-1: The following NEW packages will be installed:
k8s-node-1: aufs-tools cgroupfs-mount docker-ce libltdl7
k8s-node-1: 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
k8s-node-1: Need to get 19.5 MB of archives.
k8s-node-1: After this operation, 89.4 MB of additional disk space will be used.
k8s-node-1: Get:1 http://archive.ubuntu.com/ubuntu xenial/universe amd64 aufs-tools amd64 1:3.2+20130722-1.1ubuntu1 [92.9 kB]
k8s-node-1: Get:2 https://download.docker.com/linux/ubuntu xenial/stable amd64 docker-ce amd64 17.03.3~ce-0~ubuntu-xenial [19.4 MB]
k8s-node-1: Get:3 http://archive.ubuntu.com/ubuntu xenial/universe amd64 cgroupfs-mount all 1.2 [4,970 B]
k8s-node-1: Get:4 http://archive.ubuntu.com/ubuntu xenial/main amd64 libltdl7 amd64 2.4.6-0.1 [38.3 kB]
k8s-node-1: dpkg-preconfigure: unable to re-open stdin: No such file or directory
k8s-node-1: Fetched 19.5 MB in 3s (5,564 kB/s)
k8s-node-1: Selecting previously unselected package aufs-tools.
k8s-node-1: (Reading database ...
k8s-node-1: (Reading database ... 5%
k8s-node-1: (Reading database ... 10%
k8s-node-1: (Reading database ... 15%
k8s-node-1: (Reading database ... 20%
k8s-node-1: (Reading database ... 25%
k8s-node-1: (Reading database ... 30%
k8s-node-1: (Reading database ... 35%
k8s-node-1: (Reading database ... 40%
k8s-node-1: (Reading database ... 45%
k8s-node-1: (Reading database ... 50%
k8s-node-1: (Reading database ... 55%
k8s-node-1: (Reading database ... 60%
k8s-node-1: (Reading database ... 65%
k8s-node-1: (Reading database ... 70%
k8s-node-1: (Reading database ... 75%
k8s-node-1: (Reading database ... 80%
k8s-node-1: (Reading database ... 85%
k8s-node-1: (Reading database ... 90%
k8s-node-1: (Reading database ... 95%
(Reading database ... 54192 files and directories currently installed.)
k8s-node-1: Preparing to unpack .../aufs-tools_1%3a3.2+20130722-1.1ubuntu1_amd64.deb ...
k8s-node-1: Unpacking aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
k8s-node-1: Selecting previously unselected package cgroupfs-mount.
k8s-node-1: Preparing to unpack .../cgroupfs-mount_1.2_all.deb ...
k8s-node-1: Unpacking cgroupfs-mount (1.2) ...
k8s-node-1: Selecting previously unselected package libltdl7:amd64.
k8s-node-1: Preparing to unpack .../libltdl7_2.4.6-0.1_amd64.deb ...
k8s-node-1: Unpacking libltdl7:amd64 (2.4.6-0.1) ...
k8s-node-1: Selecting previously unselected package docker-ce.
k8s-node-1: Preparing to unpack .../docker-ce_17.03.3~ce-0~ubuntu-xenial_amd64.deb ...
k8s-node-1: Unpacking docker-ce (17.03.3~ce-0~ubuntu-xenial) ...
k8s-node-1: Processing triggers for libc-bin (2.23-0ubuntu10) ...
k8s-node-1: Processing triggers for man-db (2.7.5-1) ...
k8s-node-1: Processing triggers for ureadahead (0.100.0-19) ...
k8s-node-1: Processing triggers for systemd (229-4ubuntu21.10) ...
k8s-node-1: Setting up aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
k8s-node-1: Setting up cgroupfs-mount (1.2) ...
k8s-node-1: Setting up libltdl7:amd64 (2.4.6-0.1) ...
k8s-node-1: Setting up docker-ce (17.03.3~ce-0~ubuntu-xenial) ...
k8s-node-1: Processing triggers for libc-bin (2.23-0ubuntu10) ...
k8s-node-1: Processing triggers for systemd (229-4ubuntu21.10) ...
k8s-node-1: Processing triggers for ureadahead (0.100.0-19) ...
k8s-node-1: Reading package lists...
k8s-node-1: Building dependency tree...
k8s-node-1: Reading state information...
k8s-node-1: apt-transport-https is already the newest version (1.2.29).
k8s-node-1: curl is already the newest version (7.47.0-1ubuntu2.11).
k8s-node-1: 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
k8s-node-1: OK
k8s-node-1: Hit:1 https://download.docker.com/linux/ubuntu xenial InRelease
k8s-node-1: Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
k8s-node-1: Hit:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
k8s-node-1: Hit:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
k8s-node-1: Hit:5 http://security.ubuntu.com/ubuntu xenial-security InRelease
k8s-node-1: Get:6 https://packages.cloud.google.com/apt kubernetes-xenial InRelease [8,993 B]
k8s-node-1: Get:7 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 Packages [22.0 kB]
k8s-node-1: Fetched 31.0 kB in 1s (25.2 kB/s)
k8s-node-1: Reading package lists...
k8s-node-1: Reading package lists...
k8s-node-1: Building dependency tree...
k8s-node-1: Reading state information...
k8s-node-1: The following additional packages will be installed:
k8s-node-1: cri-tools ebtables kubernetes-cni socat
k8s-node-1: The following NEW packages will be installed:
k8s-node-1: cri-tools ebtables kubeadm kubectl kubelet kubernetes-cni socat
k8s-node-1: 0 upgraded, 7 newly installed, 0 to remove and 1 not upgraded.
k8s-node-1: Need to get 45.9 MB of archives.
k8s-node-1: After this operation, 264 MB of additional disk space will be used.
k8s-node-1: Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 ebtables amd64 2.0.10.4-3.4ubuntu2.16.04.2 [79.9 kB]
k8s-node-1: Get:2 http://archive.ubuntu.com/ubuntu xenial/universe amd64 socat amd64 1.7.3.1-1 [321 kB]
k8s-node-1: Get:3 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 cri-tools amd64 1.12.0-00 [5,343 kB]
k8s-node-1: Get:4 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubernetes-cni amd64 0.6.0-00 [5,910 kB]
k8s-node-1: Get:5 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubelet amd64 1.13.1-00 [19.0 MB]
k8s-node-1: Get:6 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubectl amd64 1.13.1-00 [7,843 kB]
k8s-node-1: Get:7 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubeadm amd64 1.13.1-00 [7,359 kB]
k8s-node-1: dpkg-preconfigure: unable to re-open stdin: No such file or directory
k8s-node-1: Fetched 45.9 MB in 12s (3,572 kB/s)
k8s-node-1: Selecting previously unselected package cri-tools.
k8s-node-1: (Reading database ...
(Reading database ... 10%database ... 5%
(Reading database ... 25%database ... 15%
(Reading database ... 35%database ... 30%
k8s-node-1: (Reading database ... 40%
k8s-node-1: (Reading database ... 45%
(Reading database ... 55%database ... 50%
k8s-node-1: (Reading database ... 60%
k8s-node-1: (Reading database ... 65%
k8s-node-1: (Reading database ... 70%
k8s-node-1: (Reading database ... 75%
k8s-node-1: (Reading database ... 80%
k8s-node-1: (Reading database ... 85%
k8s-node-1: (Reading database ... 90%
k8s-node-1: (Reading database ... 95%
(Reading database ... ng database ... 100%
k8s-node-1: 54467 files and directories currently installed.)
k8s-node-1: Preparing to unpack .../cri-tools_1.12.0-00_amd64.deb ...
k8s-node-1: Unpacking cri-tools (1.12.0-00) ...
k8s-node-1: Selecting previously unselected package ebtables.
k8s-node-1: Preparing to unpack .../ebtables_2.0.10.4-3.4ubuntu2.16.04.2_amd64.deb ...
k8s-node-1: Unpacking ebtables (2.0.10.4-3.4ubuntu2.16.04.2) ...
k8s-node-1: Selecting previously unselected package kubernetes-cni.
k8s-node-1: Preparing to unpack .../kubernetes-cni_0.6.0-00_amd64.deb ...
k8s-node-1: Unpacking kubernetes-cni (0.6.0-00) ...
k8s-node-1: Selecting previously unselected package socat.
k8s-node-1: Preparing to unpack .../socat_1.7.3.1-1_amd64.deb ...
k8s-node-1: Unpacking socat (1.7.3.1-1) ...
k8s-node-1: Selecting previously unselected package kubelet.
k8s-node-1: Preparing to unpack .../kubelet_1.13.1-00_amd64.deb ...
k8s-node-1: Unpacking kubelet (1.13.1-00) ...
k8s-node-1: Selecting previously unselected package kubectl.
k8s-node-1: Preparing to unpack .../kubectl_1.13.1-00_amd64.deb ...
k8s-node-1: Unpacking kubectl (1.13.1-00) ...
k8s-node-1: Selecting previously unselected package kubeadm.
k8s-node-1: Preparing to unpack .../kubeadm_1.13.1-00_amd64.deb ...
k8s-node-1: Unpacking kubeadm (1.13.1-00) ...
k8s-node-1: Processing triggers for man-db (2.7.5-1) ...
k8s-node-1: Processing triggers for systemd (229-4ubuntu21.10) ...
k8s-node-1: Processing triggers for ureadahead (0.100.0-19) ...
k8s-node-1: Setting up cri-tools (1.12.0-00) ...
k8s-node-1: Setting up ebtables (2.0.10.4-3.4ubuntu2.16.04.2) ...
k8s-node-1: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
k8s-node-1: Setting up kubernetes-cni (0.6.0-00) ...
k8s-node-1: Setting up socat (1.7.3.1-1) ...
k8s-node-1: Setting up kubelet (1.13.1-00) ...
k8s-node-1: Setting up kubectl (1.13.1-00) ...
k8s-node-1: Setting up kubeadm (1.13.1-00) ...
k8s-node-1: Processing triggers for systemd (229-4ubuntu21.10) ...
k8s-node-1: Processing triggers for ureadahead (0.100.0-19) ...
k8s-node-1: kubelet set on hold.
k8s-node-1: kubeadm set on hold.
k8s-node-1: kubectl set on hold.
==> k8s-node-1: Running provisioner: shell...
k8s-node-1: Running: inline script
k8s-node-1: This is worker
k8s-node-1: Reading package lists...
k8s-node-1: Building dependency tree...
k8s-node-1:
k8s-node-1: Reading state information...
k8s-node-1: The following NEW packages will be installed:
k8s-node-1: sshpass
k8s-node-1: 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
k8s-node-1: Need to get 10.5 kB of archives.
k8s-node-1: After this operation, 56.3 kB of additional disk space will be used.
k8s-node-1: Get:1 http://archive.ubuntu.com/ubuntu xenial/universe amd64 sshpass amd64 1.05-1 [10.5 kB]
k8s-node-1: dpkg-preconfigure: unable to re-open stdin: No such file or directory
k8s-node-1: Fetched 10.5 kB in 0s (78.2 kB/s)
k8s-node-1: Selecting previously unselected package sshpass.
k8s-node-1: (Reading database ...
(Reading database ... 10%database ... 5%
k8s-node-1: (Reading database ... 15%
(Reading database ... 30%database ... 20%
k8s-node-1: (Reading database ... 35%
k8s-node-1: (Reading database ... 40%
k8s-node-1: (Reading database ... 45%
k8s-node-1: (Reading database ... 50%
k8s-node-1: (Reading database ... 55%
k8s-node-1: (Reading database ... 60%
k8s-node-1: (Reading database ... 65%
k8s-node-1: (Reading database ... 70%
k8s-node-1: (Reading database ... 75%
k8s-node-1: (Reading database ... 80%
k8s-node-1: (Reading database ... 85%
k8s-node-1: (Reading database ... 90%
k8s-node-1: (Reading database ... 95%
(Reading database ... ng database ... 100%
k8s-node-1: 54564 files and directories currently installed.)
k8s-node-1: Preparing to unpack .../sshpass_1.05-1_amd64.deb ...
k8s-node-1: Unpacking sshpass (1.05-1) ...
k8s-node-1: Processing triggers for man-db (2.7.5-1) ...
k8s-node-1: Setting up sshpass (1.05-1) ...
k8s-node-1: Warning: Permanently added '192.168.205.10' (ECDSA) to the list of known hosts.
k8s-node-1: [preflight] Running pre-flight checks
k8s-node-1: [discovery] Trying to connect to API Server "192.168.205.10:6443"
k8s-node-1: [discovery] Created cluster-info discovery client, requesting info from "https://192.168.205.10:6443"
k8s-node-1: [discovery] Requesting info from "https://192.168.205.10:6443" again to validate TLS against the pinned public key
k8s-node-1: [discovery] Cluster info signature and contents are valid and TLS certificate validates against pinned roots, will use API Server "192.168.205.10:6443"
k8s-node-1: [discovery] Successfully established connection with API Server "192.168.205.10:6443"
k8s-node-1: [join] Reading configuration from the cluster...
k8s-node-1: [join] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
k8s-node-1: [kubelet] Downloading configuration for the kubelet from the "kubelet-config-1.13" ConfigMap in the kube-system namespace
k8s-node-1: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
k8s-node-1: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
k8s-node-1: [kubelet-start] Activating the kubelet service
k8s-node-1: [tlsbootstrap] Waiting for the kubelet to perform the TLS Bootstrap...
k8s-node-1: [patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "k8s-node-1" as an annotation
k8s-node-1:
k8s-node-1: This node has joined the cluster:
k8s-node-1: * Certificate signing request was sent to apiserver and a response was received.
k8s-node-1: * The Kubelet was informed of the new secure connection details.
k8s-node-1:
k8s-node-1: Run 'kubectl get nodes' on the master to see this node join the cluster.
==> k8s-node-2: Box 'ubuntu/xenial64' could not be found. Attempting to find and install...
k8s-node-2: Box Provider: virtualbox
k8s-node-2: Box Version: 20180831.0.0
==> k8s-node-2: Loading metadata for box 'ubuntu/xenial64'
k8s-node-2: URL: https://vagrantcloud.com/ubuntu/xenial64
==> k8s-node-2: Adding box 'ubuntu/xenial64' (v20180831.0.0) for provider: virtualbox
==> k8s-node-2: Importing base box 'ubuntu/xenial64'...
==> k8s-node-2: Matching MAC address for NAT networking...
==> k8s-node-2: Checking if box 'ubuntu/xenial64' is up to date...
==> k8s-node-2: Setting the name of the VM: k8s-node-2
==> k8s-node-2: Fixed port collision for 22 => 2222. Now on port 2201.
==> k8s-node-2: Vagrant has detected a configuration issue which exposes a
==> k8s-node-2: vulnerability with the installed version of VirtualBox. The
==> k8s-node-2: current guest is configured to use an E1000 NIC type for a
==> k8s-node-2: network adapter which is vulnerable in this version of VirtualBox.
==> k8s-node-2: Ensure the guest is trusted to use this configuration or update
==> k8s-node-2: the NIC type using one of the methods below:
==> k8s-node-2:
==> k8s-node-2: https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type
==> k8s-node-2: https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type
==> k8s-node-2: Clearing any previously set network interfaces...
==> k8s-node-2: Preparing network interfaces based on configuration...
k8s-node-2: Adapter 1: nat
k8s-node-2: Adapter 2: hostonly
==> k8s-node-2: Forwarding ports...
k8s-node-2: 22 (guest) => 2201 (host) (adapter 1)
==> k8s-node-2: Running 'pre-boot' VM customizations...
==> k8s-node-2: Booting VM...
==> k8s-node-2: Waiting for machine to boot. This may take a few minutes...
k8s-node-2: SSH address: 127.0.0.1:2201
k8s-node-2: SSH username: vagrant
k8s-node-2: SSH auth method: private key
k8s-node-2: Warning: Connection reset. Retrying...
k8s-node-2: Warning: Remote connection disconnect. Retrying...
k8s-node-2:
k8s-node-2: Vagrant insecure key detected. Vagrant will automatically replace
k8s-node-2: this with a newly generated keypair for better security.
k8s-node-2:
k8s-node-2: Inserting generated public key within guest...
k8s-node-2: Removing insecure key from the guest if it's present...
k8s-node-2: Key inserted! Disconnecting and reconnecting using new SSH key...
==> k8s-node-2: Machine booted and ready!
==> k8s-node-2: Checking for guest additions in VM...
k8s-node-2: The guest additions on this VM do not match the installed version of
k8s-node-2: VirtualBox! In most cases this is fine, but in rare cases it can
k8s-node-2: prevent things such as shared folders from working properly. If you see
k8s-node-2: shared folder errors, please make sure the guest additions within the
k8s-node-2: virtual machine match the version of VirtualBox you have installed on
k8s-node-2: your host and reload your VM.
k8s-node-2:
k8s-node-2: Guest Additions Version: 5.1.38
k8s-node-2: VirtualBox Version: 5.2
==> k8s-node-2: Setting hostname...
==> k8s-node-2: Configuring and enabling network interfaces...
==> k8s-node-2: Mounting shared folders...
k8s-node-2: /vagrant => /home/hareesh/Projects_WS/kubernetes-cluster
==> k8s-node-2: Running provisioner: shell...
k8s-node-2: Running: inline script
k8s-node-2: Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
k8s-node-2: Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
k8s-node-2: Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
k8s-node-2: Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
k8s-node-2: Get:5 http://archive.ubuntu.com/ubuntu xenial/main Sources [868 kB]
k8s-node-2: Get:6 http://security.ubuntu.com/ubuntu xenial-security/main Sources [139 kB]
k8s-node-2: Get:7 http://security.ubuntu.com/ubuntu xenial-security/restricted Sources [2,116 B]
k8s-node-2: Get:8 http://security.ubuntu.com/ubuntu xenial-security/universe Sources [89.7 kB]
k8s-node-2: Get:9 http://archive.ubuntu.com/ubuntu xenial/restricted Sources [4,808 B]
k8s-node-2: Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse Sources [2,472 B]
k8s-node-2: Get:11 http://archive.ubuntu.com/ubuntu xenial/universe Sources [7,728 kB]
k8s-node-2: Get:12 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [589 kB]
k8s-node-2: Get:13 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [408 kB]
k8s-node-2: Get:14 http://security.ubuntu.com/ubuntu xenial-security/universe Translation-en [159 kB]
k8s-node-2: Get:15 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [3,724 B]
k8s-node-2: Get:16 http://security.ubuntu.com/ubuntu xenial-security/multiverse Translation-en [1,844 B]
k8s-node-2: Get:17 http://archive.ubuntu.com/ubuntu xenial/multiverse Sources [179 kB]
k8s-node-2: Get:18 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7,532 kB]
k8s-node-2: Get:19 http://archive.ubuntu.com/ubuntu xenial/universe Translation-en [4,354 kB]
k8s-node-2: Get:20 http://archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [144 kB]
k8s-node-2: Get:21 http://archive.ubuntu.com/ubuntu xenial/multiverse Translation-en [106 kB]
k8s-node-2: Get:22 http://archive.ubuntu.com/ubuntu xenial-updates/main Sources [327 kB]
k8s-node-2: Get:23 http://archive.ubuntu.com/ubuntu xenial-updates/restricted Sources [2,528 B]
k8s-node-2: Get:24 http://archive.ubuntu.com/ubuntu xenial-updates/universe Sources [237 kB]
k8s-node-2: Get:25 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse Sources [8,744 B]
k8s-node-2: Get:26 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [892 kB]
k8s-node-2: Get:27 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [715 kB]
k8s-node-2: Get:28 http://archive.ubuntu.com/ubuntu xenial-updates/universe Translation-en [292 kB]
k8s-node-2: Get:29 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages [16.6 kB]
k8s-node-2: Get:30 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse Translation-en [8,440 B]
k8s-node-2: Get:31 http://archive.ubuntu.com/ubuntu xenial-backports/main Sources [4,856 B]
k8s-node-2: Get:32 http://archive.ubuntu.com/ubuntu xenial-backports/universe Sources [6,740 B]
k8s-node-2: Get:33 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages [7,288 B]
k8s-node-2: Get:34 http://archive.ubuntu.com/ubuntu xenial-backports/main Translation-en [4,456 B]
k8s-node-2: Get:35 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages [7,804 B]
k8s-node-2: Get:36 http://archive.ubuntu.com/ubuntu xenial-backports/universe Translation-en [4,184 B]
k8s-node-2: Fetched 25.2 MB in 5s (4,441 kB/s)
k8s-node-2: Reading package lists...
k8s-node-2: Reading package lists...
k8s-node-2: Building dependency tree...
k8s-node-2: Reading state information...
k8s-node-2: apt-transport-https is already the newest version (1.2.29).
k8s-node-2: ca-certificates is already the newest version (20170717~16.04.1).
k8s-node-2: curl is already the newest version (7.47.0-1ubuntu2.11).
k8s-node-2: software-properties-common is already the newest version (0.96.20.7).
k8s-node-2: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
k8s-node-2: OK
k8s-node-2: Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
k8s-node-2: Hit:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
k8s-node-2: Get:3 https://download.docker.com/linux/ubuntu xenial InRelease [66.2 kB]
k8s-node-2: Hit:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
k8s-node-2: Hit:5 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
k8s-node-2: Get:6 https://download.docker.com/linux/ubuntu xenial/stable amd64 Packages [5,491 B]
k8s-node-2: Fetched 71.7 kB in 0s (137 kB/s)
k8s-node-2: Reading package lists...
k8s-node-2: Reading package lists...
k8s-node-2: Building dependency tree...
k8s-node-2:
k8s-node-2: Reading state information...
k8s-node-2: The following additional packages will be installed:
k8s-node-2: aufs-tools cgroupfs-mount libltdl7
k8s-node-2: Suggested packages:
k8s-node-2: mountall
k8s-node-2: The following NEW packages will be installed:
k8s-node-2: aufs-tools cgroupfs-mount docker-ce libltdl7
k8s-node-2: 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
k8s-node-2: Need to get 19.5 MB of archives.
k8s-node-2: After this operation, 89.4 MB of additional disk space will be used.
k8s-node-2: Get:1 http://archive.ubuntu.com/ubuntu xenial/universe amd64 aufs-tools amd64 1:3.2+20130722-1.1ubuntu1 [92.9 kB]
k8s-node-2: Get:2 https://download.docker.com/linux/ubuntu xenial/stable amd64 docker-ce amd64 17.03.3~ce-0~ubuntu-xenial [19.4 MB]
k8s-node-2: Get:3 http://archive.ubuntu.com/ubuntu xenial/universe amd64 cgroupfs-mount all 1.2 [4,970 B]
k8s-node-2: Get:4 http://archive.ubuntu.com/ubuntu xenial/main amd64 libltdl7 amd64 2.4.6-0.1 [38.3 kB]
k8s-node-2: dpkg-preconfigure: unable to re-open stdin: No such file or directory
k8s-node-2: Fetched 19.5 MB in 2s (6,567 kB/s)
k8s-node-2: Selecting previously unselected package aufs-tools.
k8s-node-2: (Reading database ...
k8s-node-2: (Reading database ... 5%
k8s-node-2: (Reading database ... 10%
k8s-node-2: (Reading database ... 15%
k8s-node-2: (Reading database ... 20%
k8s-node-2: (Reading database ... 25%
k8s-node-2: (Reading database ... 30%
k8s-node-2: (Reading database ... 35%
(Reading database ... 45%database ... 40%
k8s-node-2: (Reading database ... 50%
k8s-node-2: (Reading database ... 55%
k8s-node-2: (Reading database ... 60%
k8s-node-2: (Reading database ... 65%
k8s-node-2: (Reading database ... 70%
k8s-node-2: (Reading database ... 75%
k8s-node-2: (Reading database ... 80%
k8s-node-2: (Reading database ... 85%
k8s-node-2: (Reading database ... 90%
k8s-node-2: (Reading database ... 95%
(Reading database ... 54192 files and directories currently installed.)
k8s-node-2: Preparing to unpack .../aufs-tools_1%3a3.2+20130722-1.1ubuntu1_amd64.deb ...
k8s-node-2: Unpacking aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
k8s-node-2: Selecting previously unselected package cgroupfs-mount.
k8s-node-2: Preparing to unpack .../cgroupfs-mount_1.2_all.deb ...
k8s-node-2: Unpacking cgroupfs-mount (1.2) ...
k8s-node-2: Selecting previously unselected package libltdl7:amd64.
k8s-node-2: Preparing to unpack .../libltdl7_2.4.6-0.1_amd64.deb ...
k8s-node-2: Unpacking libltdl7:amd64 (2.4.6-0.1) ...
k8s-node-2: Selecting previously unselected package docker-ce.
k8s-node-2: Preparing to unpack .../docker-ce_17.03.3~ce-0~ubuntu-xenial_amd64.deb ...
k8s-node-2: Unpacking docker-ce (17.03.3~ce-0~ubuntu-xenial) ...
k8s-node-2: Processing triggers for libc-bin (2.23-0ubuntu10) ...
k8s-node-2: Processing triggers for man-db (2.7.5-1) ...
k8s-node-2: Processing triggers for ureadahead (0.100.0-19) ...
k8s-node-2: Processing triggers for systemd (229-4ubuntu21.10) ...
k8s-node-2: Setting up aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
k8s-node-2: Setting up cgroupfs-mount (1.2) ...
k8s-node-2: Setting up libltdl7:amd64 (2.4.6-0.1) ...
k8s-node-2: Setting up docker-ce (17.03.3~ce-0~ubuntu-xenial) ...
k8s-node-2: Processing triggers for libc-bin (2.23-0ubuntu10) ...
k8s-node-2: Processing triggers for systemd (229-4ubuntu21.10) ...
k8s-node-2: Processing triggers for ureadahead (0.100.0-19) ...
k8s-node-2: Reading package lists...
k8s-node-2: Building dependency tree...
k8s-node-2: Reading state information...
k8s-node-2: apt-transport-https is already the newest version (1.2.29).
k8s-node-2: curl is already the newest version (7.47.0-1ubuntu2.11).
k8s-node-2: 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
k8s-node-2: OK
k8s-node-2: Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease
k8s-node-2: Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
k8s-node-2: Hit:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
k8s-node-2: Hit:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
k8s-node-2: Hit:5 https://download.docker.com/linux/ubuntu xenial InRelease
k8s-node-2: Get:6 https://packages.cloud.google.com/apt kubernetes-xenial InRelease [8,993 B]
k8s-node-2: Get:7 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 Packages [22.0 kB]
k8s-node-2: Fetched 31.0 kB in 1s (18.8 kB/s)
k8s-node-2: Reading package lists...
k8s-node-2: Reading package lists...
k8s-node-2: Building dependency tree...
k8s-node-2: Reading state information...
k8s-node-2: The following additional packages will be installed:
k8s-node-2: cri-tools ebtables kubernetes-cni socat
k8s-node-2: The following NEW packages will be installed:
k8s-node-2: cri-tools ebtables kubeadm kubectl kubelet kubernetes-cni socat
k8s-node-2: 0 upgraded, 7 newly installed, 0 to remove and 1 not upgraded.
k8s-node-2: Need to get 45.9 MB of archives.
k8s-node-2: After this operation, 264 MB of additional disk space will be used.
k8s-node-2: Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 ebtables amd64 2.0.10.4-3.4ubuntu2.16.04.2 [79.9 kB]
k8s-node-2: Get:3 http://archive.ubuntu.com/ubuntu xenial/universe amd64 socat amd64 1.7.3.1-1 [321 kB]
k8s-node-2: Get:2 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 cri-tools amd64 1.12.0-00 [5,343 kB]
k8s-node-2: Get:4 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubernetes-cni amd64 0.6.0-00 [5,910 kB]
k8s-node-2: Get:5 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubelet amd64 1.13.1-00 [19.0 MB]
k8s-node-2: Get:6 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubectl amd64 1.13.1-00 [7,843 kB]
k8s-node-2: Get:7 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubeadm amd64 1.13.1-00 [7,359 kB]
k8s-node-2: dpkg-preconfigure: unable to re-open stdin: No such file or directory
k8s-node-2: Fetched 45.9 MB in 16s (2,854 kB/s)
k8s-node-2: Selecting previously unselected package cri-tools.
k8s-node-2: (Reading database ...
(Reading database ... 60%database ... 5%
k8s-node-2: (Reading database ... 65%
k8s-node-2: (Reading database ... 70%
k8s-node-2: (Reading database ... 75%
k8s-node-2: (Reading database ... 80%
k8s-node-2: (Reading database ... 85%
k8s-node-2: (Reading database ... 90%
k8s-node-2: (Reading database ... 95%
(Reading database ... 54467 files and directories currently installed.)
k8s-node-2: Preparing to unpack .../cri-tools_1.12.0-00_amd64.deb ...
k8s-node-2: Unpacking cri-tools (1.12.0-00) ...
k8s-node-2: Selecting previously unselected package ebtables.
k8s-node-2: Preparing to unpack .../ebtables_2.0.10.4-3.4ubuntu2.16.04.2_amd64.deb ...
k8s-node-2: Unpacking ebtables (2.0.10.4-3.4ubuntu2.16.04.2) ...
k8s-node-2: Selecting previously unselected package kubernetes-cni.
k8s-node-2: Preparing to unpack .../kubernetes-cni_0.6.0-00_amd64.deb ...
k8s-node-2: Unpacking kubernetes-cni (0.6.0-00) ...
k8s-node-2: Selecting previously unselected package socat.
k8s-node-2: Preparing to unpack .../socat_1.7.3.1-1_amd64.deb ...
k8s-node-2: Unpacking socat (1.7.3.1-1) ...
k8s-node-2: Selecting previously unselected package kubelet.
k8s-node-2: Preparing to unpack .../kubelet_1.13.1-00_amd64.deb ...
k8s-node-2: Unpacking kubelet (1.13.1-00) ...
k8s-node-2: Selecting previously unselected package kubectl.
k8s-node-2: Preparing to unpack .../kubectl_1.13.1-00_amd64.deb ...
k8s-node-2: Unpacking kubectl (1.13.1-00) ...
k8s-node-2: Selecting previously unselected package kubeadm.
k8s-node-2: Preparing to unpack .../kubeadm_1.13.1-00_amd64.deb ...
k8s-node-2: Unpacking kubeadm (1.13.1-00) ...
k8s-node-2: Processing triggers for man-db (2.7.5-1) ...
k8s-node-2: Processing triggers for systemd (229-4ubuntu21.10) ...
k8s-node-2: Processing triggers for ureadahead (0.100.0-19) ...
k8s-node-2: Setting up cri-tools (1.12.0-00) ...
k8s-node-2: Setting up ebtables (2.0.10.4-3.4ubuntu2.16.04.2) ...
k8s-node-2: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
k8s-node-2: Setting up kubernetes-cni (0.6.0-00) ...
k8s-node-2: Setting up socat (1.7.3.1-1) ...
k8s-node-2: Setting up kubelet (1.13.1-00) ...
k8s-node-2: Setting up kubectl (1.13.1-00) ...
k8s-node-2: Setting up kubeadm (1.13.1-00) ...
k8s-node-2: Processing triggers for systemd (229-4ubuntu21.10) ...
k8s-node-2: Processing triggers for ureadahead (0.100.0-19) ...
k8s-node-2: kubelet set on hold.
k8s-node-2: kubeadm set on hold.
k8s-node-2: kubectl set on hold.
==> k8s-node-2: Running provisioner: shell...
k8s-node-2: Running: inline script
k8s-node-2: This is worker
k8s-node-2: Reading package lists...
k8s-node-2: Building dependency tree...
k8s-node-2: Reading state information...
k8s-node-2: The following NEW packages will be installed:
k8s-node-2: sshpass
k8s-node-2: 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
k8s-node-2: Need to get 10.5 kB of archives.
k8s-node-2: After this operation, 56.3 kB of additional disk space will be used.
k8s-node-2: Get:1 http://archive.ubuntu.com/ubuntu xenial/universe amd64 sshpass amd64 1.05-1 [10.5 kB]
k8s-node-2: dpkg-preconfigure: unable to re-open stdin: No such file or directory
k8s-node-2: Fetched 10.5 kB in 0s (84.1 kB/s)
k8s-node-2: Selecting previously unselected package sshpass.
k8s-node-2: (Reading database ...
k8s-node-2: (Reading database ... 5%
k8s-node-2: (Reading database ... 10%
(Reading database ... 60%database ... 15%
k8s-node-2: (Reading database ... 65%
k8s-node-2: (Reading database ... 70%
k8s-node-2: (Reading database ... 75%
k8s-node-2: (Reading database ... 80%
k8s-node-2: (Reading database ... 85%
k8s-node-2: (Reading database ... 90%
k8s-node-2: (Reading database ... 95%
(Reading database ... ng database ... 100%
k8s-node-2: 54564 files and directories currently installed.)
k8s-node-2: Preparing to unpack .../sshpass_1.05-1_amd64.deb ...
k8s-node-2: Unpacking sshpass (1.05-1) ...
k8s-node-2: Processing triggers for man-db (2.7.5-1) ...
k8s-node-2: Setting up sshpass (1.05-1) ...
k8s-node-2: Warning: Permanently added '192.168.205.10' (ECDSA) to the list of known hosts.
k8s-node-2: [preflight] Running pre-flight checks
k8s-node-2: [discovery] Trying to connect to API Server "192.168.205.10:6443"
k8s-node-2: [discovery] Created cluster-info discovery client, requesting info from "https://192.168.205.10:6443"
k8s-node-2: [discovery] Requesting info from "https://192.168.205.10:6443" again to validate TLS against the pinned public key
k8s-node-2: [discovery] Cluster info signature and contents are valid and TLS certificate validates against pinned roots, will use API Server "192.168.205.10:6443"
k8s-node-2: [discovery] Successfully established connection with API Server "192.168.205.10:6443"
k8s-node-2: [join] Reading configuration from the cluster...
k8s-node-2: [join] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
k8s-node-2: [kubelet] Downloading configuration for the kubelet from the "kubelet-config-1.13" ConfigMap in the kube-system namespace
k8s-node-2: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
k8s-node-2: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
k8s-node-2: [kubelet-start] Activating the kubelet service
k8s-node-2: [tlsbootstrap] Waiting for the kubelet to perform the TLS Bootstrap...
k8s-node-2: [patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "k8s-node-2" as an annotation
k8s-node-2:
k8s-node-2: This node has joined the cluster:
k8s-node-2: * Certificate signing request was sent to apiserver and a response was received.
k8s-node-2: * The Kubelet was informed of the new secure connection details.
k8s-node-2:
k8s-node-2: Run 'kubectl get nodes' on the master to see this node join the cluster.

Prerequisites

Virtual box preconfig

When starting virtual box it was missing the required kernel headers. First get them by

sudo yum install kernel-devel 
sudo /sbin/vboxconfig

verify kernel headers are present in cd /usr/src/kernels

Get the code from Github git clone https://github.com/ecomm-integration-ballerina/kubernetes-cluster

Side note:

Vagrant is currently configured to create VirtualBox synced folders with the SharedFoldersEnableSymlinksCreate option enabled. If the Vagrant guest is not trusted, you may want to disable this option.

This option can be disabled globally with an environment variable:

VAGRANT_DISABLE_VBOXSYMLINKCREATE=1

or on a per folder basis within the Vagrantfile:

config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment