Shulou(Shulou.com)06/01 Report--

As we all know, Amazon has EC2 Container Service, which is the solution Amazon uses to run Docker containers. But I don't think EC2 container service works very well, so now I'm going to test Rancher and Kubernetes on AWS.

Kubernetes is an open source system for automating deployment, self-scaling, and managing containerized applications. Rancher is a complete container management and running platform that can be used within an enterprise. It provides enterprise-level access control and container orchestration.

Deployment of Rancher environment

As a first step, I will follow the default wizard to create a new virtual private cloud for Rancher. The next thing to do is to create one or more new hosts, the Rancher documentation says to install Docker manually, and I chose RancherOS AMI here. AMI is created specifically for this purpose, and it is very small (not even curl is installed).

The security group restricts access to TCP port k8080 only to my IP. This is important because the default setting does not enable authorization. It's also great to allow access to each other between different hosts, which can be done by saving the security group (and then getting the sg- identifier) and adding all access rights to that security group.

When the new instance is ready, just use the SSH connection and start the Rancher server Docker p_w_picpath with sudo docker run-d-- restart=always-p 8080 restart=always rancher/server. Rancher's application will run itself within Docker p_w_picpath.

You can use the the docker logs-f {containerid} command to track the log:

Everything is perfect! Rancher server is starting to start. You can browse to the IP of this instance, and by default, Rancher server will run on port 8080. All hosts can use public IP, but if you have a host on a virtual private cloud, this is a bit of a hassle, so you can choose to use private IP instead of public IP. This can be changed in management and settings.

When Rancher server is up and running, we need to add some Docker hosts. You can start a new host (which is great because it will launch another instance with the same configuration), or you can add the same host as the host in server (although this is not the best way).

Deployment of Kubernetes environment

Next, add a new host in Rancher server, click Infrastructure, and then click Add Host. After you have added the host, you can add the Kubernetes environment. Kubernetes will then be automatically deployed to the new host.

This will take a few minutes, and you can monitor its current status by selecting the environment:

After the Kubernetes environment is created, you can navigate to Catalog to deploy a container. For example, select the K8S Example Ghost container-- it takes almost no time to get up and running instantly:

During the deployment of Kubernetes, the stack is created along with the following instances:

Rancher Ingress Controller 1 (rancher/ingress-controller): Rancher Ingress Controller will make full use of the existing load balancing functions of Rancher and combine the characteristics of Kubernetes ingress to integrate Rancher load balancing.

Rancher Server (rancher/server): Rancher management server, which will run the web front end and API.

Rancher Agent (rancher/agent): each node gets a relatively independent agent to manage the node.

Rancher Kubernetes Agent 1 (rancher/kubernetes-agent): the agent responsible for handling communication between Rancher and Kubernetes.

Rancher Agent Instance (rancher/agent-instance): the p_w_picpath of the proxy instance of Rancher.

Kubernetes ETCD 1 (rancher/etc): etcd is a highly available key storage component for persistent, secure distributed storage of objects and metadata.

Kubernetes Proxy 1 (rancher/k8s): Kubernetes network proxy running on each node.

Kubernetes Scheduler 1 (rancher/k8s): Kubernetes controller manager is a core component of Kubernetes.

Kubelet 1 (rancher/k8s): kubelet is the most important "node agent" running on each node.

When you want to add an additional host, the following will also be added synchronously:

Kubernetes Proxy2

Kubernetes Etcd 2

Kubelet 2

Because I didn't want to maintain my own registry, I created an Amazon Container Registry and used Rancher's registry. You can directly copy the address in Amazon Container Registry, the user name AWS (case sensitive) and the password (base64 encoded string).

You can get credentials like this:

Then create the Docker p_w_picpath:

Label p_w_picpath:

Push, this p_w_picpath goes to registry:

If you want to learn more about how to run Kubernetes on Rancher, you can visit:

Http://rancher.com/kubernetes/, or come here to read the free ebook: http://info.rancher.com/deploying-scaling-kubernetes-ebook.

Original source: Rancher Labs

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.