kubernetes service

Outline: ? How to discover services in Kubernetes ? How to discover the services provided by pod ? How to use service discovery Services ? How to use the Kube-dns discovery service ? Kube-dns principle ? Composition ? Domain name format ? Configuration Note: this share is based on the

Outline: How to discover services in KubernetesHow to discover how pod-provided services use the Service Discovery service to use the Kube-dns discovery service Kube-dns principleCompose domain name format configuration Note: This share is based on the Kubernetes 1.2 version. Let's start with a simple example. 1. How

Environment Construction _c5-6 Adjusting the micro-service adaptation Mesos5-7 Micro-Service Deployment _a5-8 Micro-Service Deployment _b5-9 Micro-Service Deployment _c6th Chapter Service Orchestration-dockerswarmThe process of learning is similar to Mesos, which is to star

Service on the line to the top of the live pressure, carry the test, or to be said or we do things brother, remember this scene above? The old method is a service cluster deployment, but there is always a limit, before with Ali when they have a flexible calculation can be set by the CPU's threshold to dynamically expand and shrink computing capacity, at that time the feeling is very strong, at least at that

[TOC]Introduction to Rolling UpdatesWhen a service in a kubernetes cluster needs to be upgraded, it is a traditional practice to go offline with the service that is being updated, to update the version and configuration after the business is stopped, and then to restart and provide the service. If the business cluster

footprint.3. Log in hub.docker.com using the Docker login command4. Push the local image to hub.docker.com using a command such as Docker push Chenxizhang/mvcapp, which may take a certain amount of time, depending on your network configurationIf all goes well, you can see the following resultsNote: If you are creating your own Docker warehouse, you can learn about the Azure Container Registry service. (https://azure.microsoft.com/zh-cn/services/conta

The previous article describes the use of Traefik for service publishing in Kubernetes 1.5.2 cluster environments. Traefik is deployed in Daemonset mode, and the connection Api-server is the HTTP protocol, and RBAC is not configured. This article describes the deployment of Traefik for service publishing in the K8s 1.9 release using the deployment method.Before y

There are two requirements for stateful cluster services: one is storage requirements and the other is cluster requirements.For storage requirements, the Kubernetes solution is: Volume, persistent Volume. For PV, in addition to manually creating a PV pool, the storage system can be automatically created by storage class.For cluster requirements, the Kubernetes solution is pet Set. The Pet Set also initializ

This article will introduce the creation and use of Kube-ui (also called dashboard) on the basis of the previous article. This thing is essentially the WebUI connection Master API interface, through the API to obtain information about the k8s cluster, and then on the web display, for the user is more friendly, the actual use is not very large.One, download the image file and incorporate the unified management of the local warehouse# docker pull docker.io/mritd/

health check function for Skydns service Working principle Analysis 1. The Kube2sky container application obtains all srvice information in the cluster by invoking the API of K8s Master, and continuously monitors the generation of the new service and writes to ETCD 2, according to the Kubelet startup parameter setting (--CLUSTER-DNS), KUBECTL will set the DNS domain name resolution profil

Kubernetes (k8s) DNS Service Restarts the resolution repeatedly: k8s.io/dns/pkg/dns/dns.go:150:failed to List *v1. Service:get https://10.96.0.1:443/api/v1/services?resourceVersion=0:dial TCP 10.96.0.1:443:getsockopt:no route to Host When deploying the Kubernetes service using Minikube, the Kube DNS

design of swarm, understand its service discovery, service orchestration, and then build swarm cluster environment, then adjust our microservices to adapt to swarm, and finally deploy them in the swarm cluster. 7th Chapter Service Orchestration-kubernetesThe whole idea of kubernetes learning is also from concept to cl

Kubernetes Service Discovery has two ways of environment variables and DNS The way of environment variables In the way of environment variable, SVC must be started before RC, otherwise the cluster IP-related environment variables of this SVC will not be available in other pod. How DNS is DNS must be started, then the resolve.conf file in the container in the pod that is started will take Kube-dns as nam

the IP needs to be within the specified IP address range of the Kube-apiserver boot parameter –service-cluster-ip-range. and Skydns If it is a localized installation, it is not possible to bind the IP of the DNS server to the IP of a virtual network (that is, the value of the parameter-addr). I would prefer to install it using mirroring mode. InstallationThe contents of the file Kubernetes-dns.yaml as foll

This is a creation in Article, where the information may have evolved or changed. A service is a process, that:1. is designed to do a small number of things (often just one).2. Have no user interface and is invoked solely via some kind of APIs.An application, on the other hand, was pretty much the opposite of that. It has a user interface (even if it's just a command line) and often performs lots of different tasks. It can also expose an API, bu

Kube-dns compositionKube-dns can solve the service discovery problem, k8s registers the service name as a domain name into Kube-dns, and can access the services it provides through the name of the service.Kube-dns of four components: ETCD, which is used to save DNS rules. kube2sky, the role is to write DNS rules. skydns, provides DNS resolution services. healthz, provides health check function. whi

1. Introduction1.1. Functions implemented: DNS resolution and intelligent forwarding1.2. Official documents:1.3. Basic concept: http://www.cnblogs.com/demonzk/p/6494968.html2. Environment:2.1. os:red Hat Enterprise Linux Server release 7.4 (Maipo)2.2. kernel:3.10.0-693.el7.x86_642.3. bind:9.9.4-51.el7_4.13. Installation:3.1. Operating system: (slightly)3.2. Configure Yum: (slightly)3.2. Install bindYum Install Bind3.3. Modify the configuration file"Linux" "Services" "SaaS" Docker+

Kube-proxy Questions: Apr1209:42:Compute1 kube-proxy[12965]: E041209:42:49.60234212965 Reflector.go:205] Pkg/proxy/config/api.go:33: Failed to List *api. Endpoints:get http://109.105.46.94:8080/api/v1/endpoints?resourceversion=0:dial TCP 109.105.46.94:8080: getsockopt:connection refusedapr: $ compute1 kube-proxy[12965]: E0412 49.602373: 12965 reflector.go:205] Pkg/proxy/config/api.go: Failed tolist *api. Service:get http://109.105.46.94:8080/api/v1/services?resourceversion=0:dial TCP 109.

To start the Nginx service:Kubectl Run Nginx--image=nginxTo view service status:Get ServicesDiscover only Kubernets service:Kubernetes 10.254.0.1 Use the following command to expose Nginx:Kubectl expose deployment Nginx--port= --type=loadbalancerCheck the service status again:Get ServicesDiscover Nginx Service:Reference Link: http://kubernetes.io/docs/user-guide/simple-nginx/

Recently started to study kubernetes, the operation of the container, the discovery has been in the containercreating state, sad a reminder, just started to encounter a bit of trouble, the following talk about how to find the problem and solve theTo run the container command:KUBECTL-F Create Redis.yamlKubectl Get pod RedisNAME Ready STATUS RestartsREDIS-MASTER-6JGSL 0/1 containercreating 0 12sAlways in containercreating, not in running stateView relat