hoeghh / kubernetes_the_easy_way Goto Github PK

Automating Kubernetes the hard way with Vagrant and scripts

License: MIT License

Shell 100.00%

kubernetes vagrant virtualbox cluster k8s k8s-cluster kubernetes-cluster kubernetes-setup cncf containers

kubernetes_the_easy_way's Introduction

Kubernetes the easy way

This repository tries to automate the guide "Kubernetes The Hard Way" by Kelsey Hightower, using Vagrant and Virtualbox.

Prerequisites

Vagrant
VirtualBox 5.2
kubectl
cfssl
cfssljson

Documentation

Find my attempt at documenting this here Documentation

Installing cfssl and cfssljson

PKI and TLS Tools by Cloudflare (https://github.com/cloudflare/cfssl)

For Linux :
 curl -o /usr/local/bin/cfssl https://pkg.cfssl.org/R1.2/cfssl_linux-amd64
 curl -o /usr/local/bin/cfssljson https://pkg.cfssl.org/R1.2/cfssljson_linux-amd64
 chmod +x /usr/local/bin/cfssl*

For Mac :
 curl -o /usr/local/bin/cfssl https://pkg.cfssl.org/R1.2/cfssl_darwin-amd64
 curl -o /usr/local/bin/cfssljson https://pkg.cfssl.org/R1.2/cfssljson_darwin-amd64
 chmod +x /usr/local/bin/cfssl*

For Windows :
  Download https://pkg.cfssl.org/R1.2/cfssl_windows-amd64.exe
  Download https://pkg.cfssl.org/R1.2/cfssljson_windows-amd64.exe
  Do whatever Windows people do

Getting started

First off, edit the file config. Here you can specify how many of each type of nodes you want. Eg. 3 master nodes. Also you can specify the number of CPU and Memory for each type.

Once thats done, just run ./install.sh.

What just happend

The script set the number of nodes you want and the resources they get. It then generates a hosts file with ip's and hostnames. This is used to configure each node in the cluster. Then it generates certificates, based on the hostfile.

Now it calls Vagrant to provition the nodes. While provitioning the nodes, Vagrant will copy scripts and certifiates to each node and execute them. The script can be found under the scripts folder and the certificates under the folder ssl.

Connect local kubectl to the new cluster

Set the current context to kubernets-the-easy-way

kubectl config use-context kubernetes-the-easy-way

Test connection and see worker nodes connected

kubectl get nodes

SSH into machines

Because we trick Vagrant into being dynamic in regards to number of machines, we need to set our variables before we can use Vagrant commands. So in order to use Vagrant commands, after the install.sh script has finished, run this

source config
vagrant ssh k8s-worker-1

Destroy machines

If Kubernetes is not your thing after all, or that you for other reasons want to remove the cluster, simply run this script

./destroy.sh

Important

Remember to run the destroy.sh script before running the install.sh script again.

kubernetes_the_easy_way's People

Contributors

Stargazers

Watchers

Forkers

jonasvinther aniamin mcontos anrizal onuryaz onek0708 gangchentfs manudiy deplon nnps255 scloud-swebz

kubernetes_the_easy_way's Issues

Unable to connect to the server: x509: certificate signed by unknown authority

Getting below mentioned error message, please assist

Deploying KubeDNS...
Unable to connect to the server: x509: certificate signed by unknown authority ( possibly because of "crypto/rsa: verification error" while trying to verify cand idate authority certificate "Kubernetes")
Deploying WeaveNet...
Unable to connect to the server: x509: certificate signed by unknown authority ( possibly because of "crypto/rsa: verification error" while trying to verify cand idate authority certificate "Kubernetes")
./install.sh: line 45: ../logs/weavenet.log: No such file or directory

Regards,
Vikas

Accessibility of the cluster

Hi,

Eager to know that, if cluster is accessible/expose outside of the system like in the LAN,WAN and the internet.

Regards,Vikas

Generate-certs.sh has wrong location of hosts file

Generate-certs.sh still cat ../hosts.
But it has moved to ../output/hosts

how to get kubernetes dashboard

how to get kubernetes dashboard from local host.

Implement loadbalacer

Let's start with traefik and give people a choice later on to use eg nginx.

Create floating ip on loadbalancers

The loadbalancers need a floating ip just like the masters have right now.

More or less copy paste.

info required for storage provisor

Hi,

currently which storage provisor is being used for the setup.

Regards,Vikas

Pods are ContainerCreating state for long time

Pods are ContainerCreating state for long time, please advice

kubectl describe pods
Name: kubernetes-dashboard-64b6f585dd-mctwj
Namespace: default
Node: k8s-worker-2/192.168.50.32
Start Time: Fri, 02 Feb 2018 17:26:57 +0530
Labels: pod-template-hash=2062914188
run=kubernetes-dashboard
Annotations:
Status: Pending
IP:
Controlled By: ReplicaSet/kubernetes-dashboard-64b6f585dd
Containers:
kubernetes-dashboard:
Container ID:
Image: k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.2
Image ID:
Port: 8888/TCP
State: Waiting
Reason: ContainerCreating
Ready: False
Restart Count: 0
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-8nn45 (ro)
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
Volumes:
default-token-8nn45:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-8nn45
Optional: false
QoS Class: BestEffort
Node-Selectors:
Tolerations:
Events:
Type Reason Age From Message

Warning FailedCreatePodSandBox 59m kubelet, k8s-worker-2 Failed create pod sandbox.
Normal SuccessfulMountVolume 59m kubelet, k8s-worker-2 MountVolume.SetUp succeeded for volume "default-token-8nn45"
Normal SuccessfulMountVolume 59m kubelet, k8s-worker-2 MountVolume.SetUp succeeded for volume "default-token-8nn45"
Warning FailedCreatePodSandBox 59m kubelet, k8s-worker-2 Failed create pod sandbox.
Normal SuccessfulMountVolume 59m kubelet, k8s-worker-2 MountVolume.SetUp succeeded for volume "default-token-8nn45"
Warning FailedCreatePodSandBox 59m kubelet, k8s-worker-2 Failed create pod sandbox.

Loadbalancer dublicates deploy of k8s objects when > 2 nodes

When provitioning more then one loadbalancer, the script will create rbac objects.
This should only be done on the first node.

Create data encryption for master nodes

We need to generate encryption key and an encryption config suitable for encrypting Kubernetes Secrets.

As described in https://github.com/kelseyhightower/kubernetes-the-hard-way/blob/master/docs/06-data-encryption-keys.md

This should be copied to the master nodes by Vagrant.

Implement worker nodes

Worker nodes should be installed in accordance with kubernetes the hard way.

Internal_ip i etcd should be based host file

The var internal_ip in the install-etcd.sh is based on a grep on ifconfig. This is risky. The info is already in the generated host file. Grep ip from hosts via $(hostname).

error during File Provisiner

getting below error message

OS : ubuntu16.04.03-x64-desktop
virtualbox:virtualbox-5.2_5.2.6-120293~~Ubuntu~~xenial_amd64.deb
vagrant:vagrant_2.0.1_x86_64.deb

k8s-master-2: Installing master...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

File provisioner:

File upload source file /root/kubernetes_the_easy_way/output/k8s-worker-1.kubeconfig must exist
File upload source file /root/kubernetes_the_easy_way/output/kube-proxy.kubeconfig must exist

Make loadbalancer survice a reboot

Right now the loadbalancer does not work if rebooted, as weavenet does not start on boot.

Clean up scripts folder for old kube-adm scripts

The old scripts in the scripts folder is legacy from another project that uses kube-adm. The should be deleted.

Use a private network range for Pod CIDR

The network range 20.0.0.0/16 is in the public network area (this is owned by Microsoft)

https://en.wikipedia.org/wiki/Private_network

In time, this should be configurable in the config file

Implement api-severs

The script should install the API servers in accordance with kubernetes the hard way

Services does not work duo to kube-proxy bug

Kube-proxy does not write iptable rules on nodes, as a result of an error in kube-proxy.
This happens when iptables version is above 1.4.20 on the nodes.

Issue found here :
kubernetes/kubernetes#58956

The PR can be found here :
kubernetes/kubernetes#60133

password for vagrant boxes to do scp

Hi,

Please provide password for vagrant boxes to do scp.

Regards,Vikas

kubectl get nodes , master node is missing

Hi,

when i executed kubectl get nodes, master node is missing and nodes are not ready.

Regards,Vikas

Describe end goal in readme

In rhe readme, describe the end goal. What will I get when the script is done.

X x etcd, resources
X x api-seevers ..... And so on

more hostnames should be valid for certificates

Traefik should connect to the masters hostname, not ip. This hostname should be valid with regards to the certificate, which its not right now.

Configuring kubectl for Remote Access

Hi,

How to Configuring kubectl for Remote Access .Please provide steps for the same.

Regards,
Vikas

Update to 1.10.7

Upgrade to newest version of 1.10 kubernetes and release

Comment for hosts generation is wrong

The last sections, the comments still reads etcd for other types of nodes. Copy/paste but forgot to edit names

unable to do ssh to the machine

Hi,

$vagrant ssh k8s-master-1
The machine with the name 'k8s-master-1' was not found configured for
this Vagrant environment.

unable to do ssh to the machine.

Regards,Vikas

Define custom hosts entries in /etc/hosts on each machine

In cases where you have an external NFS server, which is not resolvable via an DNS server, it would be nice to be able to add custom entries.

Unable to connect to the server: dial tcp 192.168.50.20:6443: i/o timeout

Hi,

cluster setup for the first time works fine, when we do vagrant halt it shutdown properly.
For the next attempt when we do vagrant up, we are getting below message

### Unable to connect to the server: dial tcp 192.168.50.20:6443: i/o timeout,
what needs to be done for the same.

Investigate change from ubuntu to centos

I would like to change to centos. Let's see if its easy, before installing corosync and pacemaker.

Add load balancers to weave net network

The load balancer(s) are not connected to the pod network, so it/they can't serve any traffic at all. Lb is connected to the API server so it does configure itself with all frot and backends.

We need to manually install weave net on load balancer(s). Before that, nothing will be served by ingress.

Update to 1.9.9 and release

Tools: Add prometheus example

Make a small example deployment that gets Promethues up and running.

Generate certificates, or use provided to traefik

Right now we have the following in the traefik.toml file

#CertFile = "/root/ssl/traefik-wildcard.pem"
#KeyFile = "/root/ssl/traefik-wildcard.key"

We need to create these certificates, and put them in use

How to make use of own docker registry

Hi,

How to make use of own private docker registry or export/import of docker image for deployment. Is it possible for both the methods.

Regards,Vikas

Switch to coreDNS

https://github.com/coredns/deployment/blob/master/kubernetes/README.md

Update traefik to newest version

https://github.com/containous/traefik/releases

Describe how to upgrade cluster components

Describe how to upgrade cluster components like kubelet, kube-apiserver ect. manually.

Create floating ip on masters

Use corosync and pacemaker to create a floating ip between all master nodes. This will then be the external IP for master nodes.

Remove todo in etcd script

The todo was done. Remove the todo about copying certs to node. That's done by vagrant.

Describe how to add another worker

Once the cluster is provisioned, one might want to add yet another worker node. We should have a guide and some scripts for doing this.

Add log output to file

Certificates generation and vagrant output shout be directed to a file in a log directory.

Eg.
vagrant up --debug &> logs/vagrant_$(date)_log

no route to host

Hi,

Getting below message, firewall is disabled in host machine

docker@node2:~/kubernetes_the_easy_way$ kubectl get nodes
Unable to connect to the server: dial tcp 192.168.50.20:6443: getsockopt: no route to host

Regards,Vikas

Simplify install scripts with an install config

Right now each host needs to look into a host file and do a lot of jumps to configure itself.

I think it would be smart to generate an install config file that is copied to each host, and used by the install script.

It will make it easier to add more nodes, as it is only to generate a config and then run the same script as the others

It will also make it easier later, to use the scripts outside of this project, or with a provitioning master.

Add certificate info to config

I should be able to define the information going into the certificates, in the config file.

hoeghh / kubernetes_the_easy_way Goto Github PK

kubernetes_the_easy_way's Introduction

Kubernetes the easy way

Prerequisites

Documentation

Installing cfssl and cfssljson

Getting started

What just happend

Connect local kubectl to the new cluster

Set the current context to kubernets-the-easy-way

Test connection and see worker nodes connected

SSH into machines

Destroy machines

Important

kubernetes_the_easy_way's People

Contributors

Stargazers

Watchers

Forkers

kubernetes_the_easy_way's Issues

Getting below mentioned error message, please assist

Pods are ContainerCreating state for long time, please advice

Recommend Projects

Recommend Topics

Recommend Org