google kubernetes

The role of Kubernetes Scheduler is to bind controller manager to a new pod according to a specific scheduling algorithm and scheduling policy to a suitable node in the cluster, and to write the binding information to the ETCD.I. Deployment OF SchedulerThe following generates the Kube-scheduler Kubeconfig file, as follows:cd/etc/kubernetesexport kube_apiserver="https://192.168.15.200:6443"Configure clusterKubectl config set---certificate-authority=/et

Brief Description:Using the Rke tool, on the 192.168.3.161 machine, create a kubernetes cluster with two nodes (192.168.3.162 and 192.168.3.163). Rke automatically creates KUBE_CONFIG_CLUSTER.YML configuration files in the/home/user directory.On another server (192.168.3.160), run the Rancher Server 2.0 container. After running, use the https://192.168.3.160 address to access Rancher Server 2.0 preview. (Note: No longer the previous 8080 port)In the R

Brief description:Using the Rke tool, on the 192.168.3.161 machine, create a kubernetes cluster with two nodes (192.168.3.162 and 192.168.3.163). Rke automatically creates KUBE_CONFIG_CLUSTER.YML configuration files in the/home/user directory.On another server (192.168.3.160), run the Rancher Server 2.0 container. After running, use the https://192.168.3.160 address to access Rancher Server 2.0 preview. (Note: No longer the previous 8080 port)In the R

previous Chapters Kubernetes All operations we are using command line tools kubectl completed. To provide a richer user experience, Kubernetes also developed a WEB-based Dashboard that enables users to deploy containerized applications with Kubernetes Dashboard, monitor the status of applications, perform troubleshooting tasks, and manage

Kubernetes has developed a Elasticsearch add-on to enable log management of the cluster. This is a combination of Elasticsearch, FLUENTD and Kibana. Elasticsearch is a search engine that is responsible for storing logs and providing query interfaces; Fluentd is responsible for collecting logs from Kubernetes and sending Elasticsearch;kibana a Web GUI that users can browse and search for stored in Logs in th

Deploy a kubernetes cluster on CentOS7.0I. Deployment environment and architecture OpenStack: hengtian cloud 3.4 Operating System: centos 7.0 Flannel: 0.5.5 Kubernetes: 1.2.0 Etcd version: 2.2.2 Docker version: 1.18.0 Cluster information: Role Hostname IP Address Master Master10.0.222.2 Node Node1 10.0.222.3 Node Node210.0.222.4 Node Node3 10.0.222.5 Node Node4 10.0.222.6 The master node contains

the original is from the "Listen to Cloud Technology blog": http://blog.tingyun.com/web/article/detail/1345Today, contact Kubernetes also has a period of time, and most of our business has been stably run in different sizes of kubernetes clusters, we have to say, whether from the application deployment, iteration, or resource scheduling management and other aspects have their unspeakable advantages, But as

Configuring the Kubernetes dashboard is relatively straightforward. Similarly, only need to obtain the Dashboard-controller.yaml and Dashboard-service.yaml files from the source code, slightly modify can:wget Https://rawgit.com/kubernetes/kubernetes/master/cluster/addons/dashboard/dashboard-controller.yamlwget Https://rawgit.com/

I. Introduction of COREDNSKubernetes includes the DNS server Kube-dns for service discovery. The DNS server leverages Skydns's libraries to provide DNS requests for kubernetes pods and services. SkyDNS2 's author, Miek Gieben, created a new DNS server, Coredns, which was built with a more modular, extensible framework. Infoblox has partnered with Miek to use this DNS server as a substitute for kube-dns.COREDNS leverages the server framework developed

first introduce what k8s is: (Quote from k8s Chinese community)Kubernetes is a container cluster management system, it is an open source platform, can realize the automatic deployment of container cluster, auto-scaling capacity, maintenance and other functions. Kubernetes you can: Quick Deploy app Rapid extension Application Seamless docking of new application features

This article will be based on the previous article on the configuration of the DNS service in the Kubernetes cluster environment, in the k8s cluster, pod life cycle is short, pod restart IP address will change, for the application this is unacceptable, in order to solve this problem, The k8s cluster cleverly introduces the DNS service to realize the discovery of the service, in which DNS requires a total of 4 components in the k8s cluster, each of whi

Environment:Kubernetes 1.5.2Kubernetes-dashboard 1.5.1Pull Mirror to local first:Docker Pull docker.io/ist0ne/kubernetes-dashboard-amd64:v1.5.1VI Kubernetes-dashboard.yaml' Kind:deploymentApiversion:extensions/v1beta1MetadataLabelsApp:kubernetes-dashboardName:kubernetes-dashboardNamespace:kube-systemSpecReplicas:1SelectorMatchlabels:App:kubernetes-dashboardTemplateMetadataLabelsApp:kubernetes-dashboardComme

Services deployed by users on Kubernetes typically run on private networks, and pod and service provide parameters such as Hostport,nodeport to expose these service ports to K8S nodes for user access. There are obvious drawbacks to this approach:1) Easy to occupy excessive host port;2) service ports exposed to multiple hosts increasing the difficulty of firewalls and security configuration3) The default hostport,nodeport mode does not function as load

1. The following error was reported during the creation of Nginx pod:#kubectlcreate-F Nginx-pod.yaml from " Nginx-pod.yaml " " Nginx " is for default/default is automatically created and added to the service accountWorkaround:1> Modify the Kube_admission_control parameter in the/etc/kubernetes/apiserver file.Before modification:Kube_admission_control="--admission_control=namespacelifecycle,namespaceexists,limitranger, Securitycontextdeny,serviceacco

components $ yum install-y etcd kubernetes NTP flannel 3, each node configuration ETCD Server # Modify config file $ vim/etc/etcd/etcd.conf Etcd_name=defaultEtcd_data_dir="/var/lib/etcd/default.etcd"Etcd_listen_client_urls="http://localhost:2379,http://192.168.80.139:2379"Etcd_advertise_client_urls="http://192.168.80.139:2379"# Start Service $ systemctl start ETCD $ systemctl enable etcd# check ETCD cluster status $ etcdctl cluster-Hea

1. Reference documentationhttp://traefik.cn/2. Simple way to accessReference documentshttps://tonybai.com/2018/06/25/the-kubernetes-ingress-practice-for-https-service/Previous: Traefik Basic deployment record, describes the simplest HTTP access Traefik, the access process reference is shown below:Client---(via HTTP)---> Traefik----(via HTTP)----;? ServicesNow to practice is more secure and more complex HTTPS access Traefik, there are two kinds of acce

The bottom of the Kubernetes node is supported by a software called a "container runtime," which is responsible for things like starting and stopping containers. The most well-known container runtime is Docker, but it is not unique. In fact, this field has developed rapidly in the container runtime. To make the expansion of kubernetes easier, we have been polishing the k8s plug-in API that supports containe

Service account for Kubernetes Service Account RoleThe service account is designed to facilitate the process within the pod to invoke the Kubernetes API or other external services. Service Account Usage ScenariosProcesses running in the pod need to invoke the Kubernetes API and other services of the non-Kubernetes