kubernetes course

Service discovery mechanism Kubernetes provides two ways to discover the service:1. Environment Variables When the pod is running, Kubernetes writes the information for the service that existed before This method requires that the pod must be started after the service. The pod that was started before the service will not have an environment variable for that service. There is no such limit in the way

This is a creation in Article, where the information may have evolved or changed. Kris Nova, of Microsoft, shares lessons on over-engineering from she experience contributing to Kubernetes Kops. In hers spare time, she runs a Kubernetes special Interest Group bringing Kubernetes to AWS, all and working on Microsoft Acs. She ' s writing a book called Cloud Native

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

beginners.Then there are classmates asked, there are a lot of binary installation of the tutorial, why do I also repeat the wheel? Indeed, K8s's binary installation method does have a lot of tutorials, I also have to look at the introduction, there are two main tutorials, one is a fool, also called a button, run a command, execute a script, all done (of course, will encounter some problems, you need to find a way to solve the ^_^). There is also a co

-ingress-lb spec:terminationgraceperiodseconds:60 Volume S:-Name:ssl secret:secretname:traefik-cert-name:config Configmap:name: traefik-conf hostnetwork:true restartpolicy:always serviceaccountname:ingress containers:-Im Age:traefik name:traefik-ingress-lb volumemounts:-Mountpath: "/opt/conf/k8s/ssl" Name: " SSL "-Mountpath:"/opt/conf/k8s/conf "Name:" Config "ports:-name:http Container port:80 hostport:80-name:admin containerport:8580 hostport:8580 args: ---configfile=/opt/conf/k8s/CONF/T

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

Kubernetes 1.5 installation and cluster environment deploymentArticle reprinted from: http://www.cnblogs.com/tynia/p/k8s-cluster.htmlBrief introduction:Docker: An open-source application container engine that can create a lightweight, portable, self-sufficient container for your application.Kubernetes: The Docker container Cluster Management system, which is open source by Google, provides the functions of resource scheduling, deployment operation, se

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

Please be sure to keep the environment consistent To download the required system packages during installation, be sure to connect all the nodes to the Internet . Cluster node information for this installationLab environment: VMware's virtual machines IP Address Host name CPU Memory 192.168.77.133 K8s-m1 6 cores 6G 192.168.77.134 k8s-m2 6 cores 6G 192.168.77.135

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