etcd kubernetes

Before installation, the three CENTOS7 servers are banned from the firewall, and the mirror that needs to be started 2 node machines must be kept consistent, otherwise the pod will not start1 has three CENTOS7 servers: 10.1.1.170 (Master), 10.1.1.169 node1,10.1.1.171 Node22 Install NTP service on three machines to ensure all time can be synchronized#yum-y Install NTP#systemctl Start NTPD#systemctl Enable NTPD3 Installing Kubernetes Master on 10.1.1.17

hypernetes:bringing Security and Multi-tenancy to KubernetesApplication ArchitectureMicroserviceHere's a Chinese blog about what to select Open Source tools for building a micorservice.Https://mp.weixin.qq.com/s/bsuveX-E6E2fKZ24mj03nQServcie MeshLinkerdEnvoyIstioTrainingKnowledgekubernetsDocumentKubernetes Handbook (Chinese Version)ETCDFor more information, please see ETCD Document.ContainterDockerFor Moe information, please see https://docs.docker.c

Deploy Kubernetes in Docker Kubernetes is an open-source container management framework of Google. It provides a series of functions such as host, cluster management, container deployment, high availability, and auto scaling of Docker containers; kubernetes's design goals include putting the container cluster in the desired state at any time. Therefore, a complete cluster management mechanism is established

1. Single ETCD node (for test development)Before I have been developing a test that has been used for a ETCD node, then the Start command has been directly hitting a ETCD (I have added the bin directory of the ETCD installation directory to the PATH environment variable), and then the boot information shows

First, prerequisites1, first you will have ready-made kubernetes cluster, if you have nothing now, please refer to:http://zlyang.blog.51cto.com/1196234/19510102, the proposed use ETCD cluster, the construction process please refer to:http://zlyang.blog.51cto.com/1196234/1951164Ii. Deployment of Kubernetes-dashboard[All machines: Master, Node1, Node2]1, install fl

, but each label key can only correspond to one value;The entire system is associated with a label to get the target that really needs to be manipulated.5. ProxyProxy not only solves the same host service port conflict problem, also provides service forwarding service port to provide services, the proxy backend using a random, round-robin load balancing algorithm.Third, kubernetes related componentsKubernetes mainly include: Kubectl, Kube-apiserver, K

service designed by the CoreOS team for kubernetes, which simply means that the Docker container created by the different node hosts in the cluster has a unique virtual IP address for the complete cluster. It also creates an overlay network between these IP addresses, which, through this overlay network, passes the packets intact to the target container (Overlay).Here is a schematic diagram of its network:As you can see, flannel first creates a bridg

Preface The previous article talked about some common cluster operations in ETCD, which mainly covered some common problems that might be encountered, after all, the God (Operational dimension) perspective always sees the problem and then recovers. For a cluster, it is common to process crashes, physical machine downtime, data migration backups, capacity reduction, and so on. The rest of the operation is nothing more than some common problem-handling

This blog from my space reproduced over, http://user.qzone.qq.com/29185807/blog/1458542207Code is GITHUB.COM/COREOS/GO-ETCD/ETCDNote: This version is the ETCD client used in k8s v1.1.1.First I look at how the next k8s is used. Location in K8s.io\kubernetes\cmd\kube-apiserver\app\server.goCode directory, from this point of view, the code is very clearSo we're goin

This is a creation in Article, where the information may have evolved or changed. "Editor's note" This article compares three service discovery tools for zookeeper, ETCD, and Consul, and explores the best solution for service discovery, for informational purposes only. If you use a predefined port, the more services you have, the greater the likelihood of a conflict, after all, it is impossible to have two services listening on the same port. Managin

information consistency and other information, CPU and memory resources such as monitoring we use cadvisor and our internal monitoring system to achieve. Auto scale, we did not use the automatic expansion mechanism of the Kubernetes itself, but developed it separately, mainly to support a more flexible scaling strategy. Configuration Layer (ETCD)The configuration information required by the applic

dashboard is "naked", there is no security to say:-Dashboard UI does not have access management mechanism, any access can take over the dashboard completely;-At the same time behind, dashboard accesses the apiserver through Insecure-port, without using the encryption mechanism. Second, dashboard through the Kubeconfig file information access Apiserver Let's start by establishing a secure communication mechanism between dashboard and apiserver. The startup parameters for Kube-apiserver on the cu

Recently tried a little etcd to do the registration discovery of the service "Etcd Service" Download the binary file from Etcd's official website and allocate three machines to do the cluster 10.0.1.98 etcd-001 10.0.1.205 etcd-002 10.0.1.182 etcd-003 Then start the service

Yum-y Install ETCD Docker flannel kubenetesGeneral will encounter no k8s source problem, first Yum update-y see if it is effective, if still useless to create a Yum source, and then install KubenetesDo the following:Create a Yum sourcevi virt7-docker-common-release.repoAdd the following content:[virt7-docker-common-release]name=virt7-docker-common-releasebaseurl=http://cbs.centos.org/repos/virt7-docker-common-release/x86_64/os/gpgcheck=0Installation