Skip to content

Instantly share code, notes, and snippets.

@v9n
Created July 30, 2017 06:02
Show Gist options
  • Save v9n/44c0f246fad9ea24fc095de5eb209995 to your computer and use it in GitHub Desktop.
Save v9n/44c0f246fad9ea24fc095de5eb209995 to your computer and use it in GitHub Desktop.
Vagrant up
==> master: Importing base box 'kureikain/k8s-cni-strongswan-master'...
==> master: Matching MAC address for NAT networking...
==> master: Setting the name of the VM: vagrant_master_1501394347964_12447
==> master: Clearing any previously set network interfaces...
==> master: Preparing network interfaces based on configuration...
master: Adapter 1: nat
master: Adapter 2: hostonly
==> master: Forwarding ports...
master: 22 (guest) => 2222 (host) (adapter 1)
==> master: Running 'pre-boot' VM customizations...
==> master: Booting VM...
==> master: Waiting for machine to boot. This may take a few minutes...
master: SSH address: 127.0.0.1:2222
master: SSH username: ubuntu
master: SSH auth method: private key
master: Warning: Connection reset. Retrying...
master: Warning: Remote connection disconnect. Retrying...
master: Warning: Connection reset. Retrying...
master: Warning: Remote connection disconnect. Retrying...
master: Warning: Connection reset. Retrying...
master: Warning: Remote connection disconnect. Retrying...
==> master: Machine booted and ready!
==> master: Checking for guest additions in VM...
master: The guest additions on this VM do not match the installed version of
master: VirtualBox! In most cases this is fine, but in rare cases it can
master: prevent things such as shared folders from working properly. If you see
master: shared folder errors, please make sure the guest additions within the
master: virtual machine match the version of VirtualBox you have installed on
master: your host and reload your VM.
master:
master: Guest Additions Version: 5.0.40
master: VirtualBox Version: 5.1
==> master: Setting hostname...
==> master: Configuring and enabling network interfaces...
==> master: Mounting shared folders...
master: /vagrant => /Users/kureikain/Sites/k8s-cni-ipsec/vagrant
==> master: Running provisioner: shell...
master: Running: inline script
==> minion1: Importing base box 'kureikain/k8s-cni-strongswan-minion'...
==> minion1: Matching MAC address for NAT networking...
==> minion1: Setting the name of the VM: vagrant_minion1_1501394423408_75789
==> minion1: Fixed port collision for 22 => 2222. Now on port 2200.
==> minion1: Clearing any previously set network interfaces...
==> minion1: Preparing network interfaces based on configuration...
minion1: Adapter 1: nat
minion1: Adapter 2: hostonly
==> minion1: Forwarding ports...
minion1: 22 (guest) => 2200 (host) (adapter 1)
==> minion1: Running 'pre-boot' VM customizations...
==> minion1: Booting VM...
==> minion1: Waiting for machine to boot. This may take a few minutes...
minion1: SSH address: 127.0.0.1:2200
minion1: SSH username: ubuntu
minion1: SSH auth method: private key
minion1: Warning: Connection reset. Retrying...
minion1: Warning: Remote connection disconnect. Retrying...
minion1: Warning: Connection reset. Retrying...
minion1: Warning: Remote connection disconnect. Retrying...
==> minion1: Machine booted and ready!
==> minion1: Checking for guest additions in VM...
minion1: The guest additions on this VM do not match the installed version of
minion1: VirtualBox! In most cases this is fine, but in rare cases it can
minion1: prevent things such as shared folders from working properly. If you see
minion1: shared folder errors, please make sure the guest additions within the
minion1: virtual machine match the version of VirtualBox you have installed on
minion1: your host and reload your VM.
minion1:
minion1: Guest Additions Version: 5.0.40
minion1: VirtualBox Version: 5.1
==> minion1: Setting hostname...
==> minion1: Configuring and enabling network interfaces...
==> minion1: Mounting shared folders...
minion1: /vagrant => /Users/kureikain/Sites/k8s-cni-ipsec/vagrant
==> minion1: Running provisioner: shell...
minion1: Running: inline script
==> minion1: [kubeadm] WARNING: kubeadm is in beta, please do not use it for production clusters.
==> minion1: [preflight] Skipping pre-flight checks
==> minion1: [discovery] Trying to connect to API Server "10.9.0.2:6443"
==> minion1: [discovery] Created cluster-info discovery client, requesting info from "https://10.9.0.2:6443"
==> minion1: [discovery] Cluster info signature and contents are valid, will use API Server "https://10.9.0.2:6443"
==> minion1: [discovery] Successfully established connection with API Server "10.9.0.2:6443"
==> minion1: [bootstrap] Detected server version: v1.7.2
==> minion1: [bootstrap] The server supports the Certificates API (certificates.k8s.io/v1beta1)
==> minion1: [csr] Created API client to obtain unique certificate for this node, generating keys and certificate signing request
==> minion1: [csr] Received signed certificate from the API server, generating KubeConfig...
==> minion1: [kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/kubelet.conf"
==> minion1:
==> minion1: Node join complete:
==> minion1: * Certificate signing request sent to master and response
==> minion1: received.
==> minion1: * Kubelet informed of new secure connection details.
==> minion1:
==> minion1: Run 'kubectl get nodes' on the master to see this machine join.
==> minion2: Importing base box 'kureikain/k8s-cni-strongswan-minion'...
==> minion2: Matching MAC address for NAT networking...
==> minion2: Setting the name of the VM: vagrant_minion2_1501394499537_56824
==> minion2: Fixed port collision for 22 => 2222. Now on port 2201.
==> minion2: Clearing any previously set network interfaces...
==> minion2: Preparing network interfaces based on configuration...
minion2: Adapter 1: nat
minion2: Adapter 2: hostonly
==> minion2: Forwarding ports...
minion2: 22 (guest) => 2201 (host) (adapter 1)
==> minion2: Running 'pre-boot' VM customizations...
==> minion2: Booting VM...
==> minion2: Waiting for machine to boot. This may take a few minutes...
minion2: SSH address: 127.0.0.1:2201
minion2: SSH username: ubuntu
minion2: SSH auth method: private key
minion2: Warning: Connection reset. Retrying...
minion2: Warning: Remote connection disconnect. Retrying...
==> minion2: Machine booted and ready!
==> minion2: Checking for guest additions in VM...
minion2: The guest additions on this VM do not match the installed version of
minion2: VirtualBox! In most cases this is fine, but in rare cases it can
minion2: prevent things such as shared folders from working properly. If you see
minion2: shared folder errors, please make sure the guest additions within the
minion2: virtual machine match the version of VirtualBox you have installed on
minion2: your host and reload your VM.
minion2:
minion2: Guest Additions Version: 5.0.40
minion2: VirtualBox Version: 5.1
==> minion2: Setting hostname...
==> minion2: Configuring and enabling network interfaces...
==> minion2: Mounting shared folders...
minion2: /vagrant => /Users/kureikain/Sites/k8s-cni-ipsec/vagrant
==> minion2: Running provisioner: shell...
minion2: Running: inline script
==> minion2: [kubeadm] WARNING: kubeadm is in beta, please do not use it for production clusters.
==> minion2: [preflight] Skipping pre-flight checks
==> minion2: [discovery] Trying to connect to API Server "10.9.0.2:6443"
==> minion2: [discovery] Created cluster-info discovery client, requesting info from "https://10.9.0.2:6443"
==> minion2: [discovery] Cluster info signature and contents are valid, will use API Server "https://10.9.0.2:6443"
==> minion2: [discovery] Successfully established connection with API Server "10.9.0.2:6443"
==> minion2: [bootstrap] Detected server version: v1.7.2
==> minion2: [bootstrap] The server supports the Certificates API (certificates.k8s.io/v1beta1)
==> minion2: [csr] Created API client to obtain unique certificate for this node, generating keys and certificate signing request
==> minion2: [csr] Received signed certificate from the API server, generating KubeConfig...
==> minion2: [kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/kubelet.conf"
==> minion2:
==> minion2: Node join complete:
==> minion2: * Certificate signing request sent to master and response
==> minion2: received.
==> minion2: * Kubelet informed of new secure connection details.
==> minion2:
==> minion2: Run 'kubectl get nodes' on the master to see this machine join.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment