Kubernetes on ubuntu 16.04

I test and learn kubernetes. I am using ubuntu 16.04 and was looking for a simple and easy installation guide but could not find it ... Any suggestion? My goal is to be able to run kubernetes as a master on one ubuntu 16.04 laptop, and later configure a second ubuntu 16.04 laptop to easily join a cluster. I wonder if this can be achieved with the current version of kubernetes and the 16.04 version of ubuntu ... Any pointer to a guide or useful resource would be appreciated ... Regards.

+5
source share
5 answers

You can check the way to create a cluster with one node, which is through cluster / get-kube-local.sh . It shows you how you can use hypercubes to create a cluster.

If you want to get into the baseline data, another method is to check the contents of hack / local-up-cluster.sh . This calls each component separately, for example:

  • Kube apiserver
  • Kube proxy
  • Kube DNS
  • Kube-controller-manager

One could use the same steps to create a cluster with two nodes, as mentioned in your question.

+1
source

Not sure if this suits your needs, but Minikube is IMO, it quickly launches Kubernetes cluster locally: https://github.com/kubernetes/minikube

In addition: setting up a multi-node cluster is not an easy task because you need to set up an overlay network, and Kubernetes consists of many components.

0
source

I came across an article to install Kubernetes on Ubuntu 16.04. https://www.techrepublic.com/article/how-to-quickly-install-kubernetes-on-ubuntu/

I suggest you upgrade with the latest version of Kubernetes, as the new version is supported by some extensions, such as deployments, replica sets (similar to the replication controller).

0
source

Try https://github.com/nitinmidha/kube-cluster It is tested with kube v1.4.6 and Ubuntu 16.04

These are bash scripts written to provide "Kubernetes HA (multi master with clustering etcd, multi minion) Secure (Client Certification on etcd and kube-api-server) Cluster on Ubuntu 16.04"

Limitations

  • https: // master_ip / ui will not work, as the master cannot reach the containers. The dashboard is hosted as a separate internal service, available on mini-nodes on port 9090 using the IP address of the service panel. If necessary, it can be proxied through any reverse proxy server, for example NGINX. Or the service may provide NodePort and may be available outside the cluster

  • kube-apiserver provides port 8080 for the 127.0.0.1 interface on master. Once https://github.com/kubernetes/kubernetes/issues/13598 is fixed and avialble, --insecure-port will be set to 0.

  • Flannel does not protect data packets. There is a PR ( https://github.com/coreos/flannel/pull/290 ) to add an ipsec backend that will encrypt data packets. Once this feature is available, the setting will be configured to protect it.

  • kubelet and kube-proxy do not support multiple cube-apiserver addresses. Thus, we still have one point of failure, since only one IP address can be configured. To get a workaround, we can expose all the main nodes under an external load balancer and then point to this address. The problem is recorded and processed in the quaternets. https://github.com/kubernetes/kubernetes/issues/19152

Functions

  • Multi Master cluster with ETCD clustering.
  • TLS communication and client certificate authentication between ETCD client and peer-to-peer communication.
  • TLS communication and client certificate authentication between all kube components
  • Flannel is used for networking. Flannel does not yet support TLS.
  • Node can only be Master, Worker Only and Master-Worker. Only Master Only nodes do not have flannels / kubels and kube-proxy, so they will not be able to get to the pods. Also the 'kubelet get nodes' command will not show this node.
  • Ability to connect to an existing ETCD cluster with TLS.
-1
source

All Articles