blocks|key|2377611|text|如果您使用的是Kubernetes，以下是高级步骤：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2377612|2377613|使用您的docker映像创建您的微服务部署/工作负载，|ordered-list-item|2377614|Create服务指向这些服务入口，使用指向服务|2377615|的基于路径的规则|2377616|以下是示例清单/yaml文件：(根据需要更改docker图像、端口等)|2377617|apiVersion:+v1
kind:+Service
metadata:
++name:+svc-gateway
spec:
++ports:
++++-+port:+80
++selector:
++++app:+gateway
---
apiVersion:+v1
kind:+Service
metadata:
++name:+svc-messaging
spec:
++ports:
++++-+port:+80
++selector:
++++app:+messaging
---
apiVersion:+extensions/v1beta1
kind:+Deployment
metadata:
++name:+deployment-gateway
spec:
++replicas:+1
++template:
++++metadata:
++++++labels:
++++++++app:+gateway
++++spec:
++++++containers:
++++++-+name:+gateway
++++++++image:+gateway/image:v1.0
++++++++ports:
++++++++-+containerPort:+80
---
apiVersion:+extensions/v1beta1
kind:+Deployment
metadata:
++name:+deployment-messaging
spec:
++replicas:+1
++template:
++++metadata:
++++++labels:
++++++++app:+messaging
++++spec:
++++++containers:
++++++-+name:+messaging
++++++++image:+messaging/image:v1.0
++++++++ports:
++++++++-+containerPort:+80
---
apiVersion:+extensions/v1beta1
kind:+Ingress
metadata:
++name:+ingress-for-chat-application
spec:
++rules:
++-+host:+chat.example.com
++++http:
++++++paths:
++++++-+backend:
++++++++++serviceName:+svc-gateway
++++++++++servicePort:+80
++++++++path:+/api/v1/users
++++++-+backend:
++++++++++serviceName:+svc-messaging
++++++++++servicePort:+80
++++++++path:+/api/v1/messages|code-block|syntax|javascript|2377618|如果您有其他容器在同一名称空间中运行，并且希望与这些服务通信，则可以直接使用它们的服务名称。|2377619|例如：curl+http://svc-messaging或curl+http://svc-gateway|offset|length|style|CODE|2377620|您不需要运行自己的服务发现，这由Kubernetes负责！|2377621|一些视觉效果：|2377622|步骤1：|2377623|📷|atomic|2377624|​|2377625|第2步：|2377626|2377627|2377628|第3步：|2377629|2377630|2377631|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/e5e012598432acc6603c72c70ebfe43c.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/5bc3ec27a14512c1d901a7dcbce47158.png|2|https://ask.qcloudimg.com/http-save/yehe-900000/b800f2f59a50a47166547e394ae44d36.png^0|0|0|0|0|0|0|0|0|3|P|T|N|0|0|0|0|0|1|0|0|0|0|0|1|1|0|0|0|0|1|2|0|0^^$0|@$1|2|3|4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1W|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|1X|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|20|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|21|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|22|8|@$U|23|V|24|W|X]|$U|25|V|26|W|X]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|27|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|28|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|29|8|@]|9|@]|A|$]]|$1|14|3|15|5|16|7|2A|8|@]|9|@$U|2B|V|2C|1|2D]]|A|$]]|$1|17|3|18|5|6|7|2E|8|@]|9|@]|A|$]]|$1|19|3|1A|5|6|7|2F|8|@]|9|@]|A|$]]|$1|1B|3|15|5|16|7|2G|8|@]|9|@$U|2H|V|2I|1|2J]]|A|$]]|$1|1C|3|18|5|6|7|2K|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|2L|8|@]|9|@]|A|$]]|$1|1F|3|15|5|16|7|2M|8|@]|9|@$U|2N|V|2O|1|2P]]|A|$]]|$1|1G|3|18|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|1H|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]]|1I|$1J|$5|1K|1L|1M|A|$1N|1O|1P|-4]]|1Q|$5|1K|1L|1M|A|$1N|1R|1P|-4]]|1S|$5|1K|1L|1M|A|$1N|1T|1P|-4]]]]

If you are using Kubernetes, here are the high level steps:

<ol>
<li>Create your micro-service Deployments/Workloads using your docker images</li>
<li>Create Services pointing to these deployments</li>
<li>Create Ingress using Path Based rules pointing to the services</li>
</ol>

Here is sample manifest/yaml files: (change docker images, ports etc as needed)

<pre><code>apiVersion: v1
kind: Service
metadata:
 name: svc-gateway
spec:
 ports:
 - port: 80
 selector:
 app: gateway
---
apiVersion: v1
kind: Service
metadata:
 name: svc-messaging
spec:
 ports:
 - port: 80
 selector:
 app: messaging
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
 name: deployment-gateway
spec:
 replicas: 1
 template:
 metadata:
 labels:
 app: gateway
 spec:
 containers:
 - name: gateway
 image: gateway/image:v1.0
 ports:
 - containerPort: 80
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
 name: deployment-messaging
spec:
 replicas: 1
 template:
 metadata:
 labels:
 app: messaging
 spec:
 containers:
 - name: messaging
 image: messaging/image:v1.0
 ports:
 - containerPort: 80
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
 name: ingress-for-chat-application
spec:
 rules:
 - host: chat.example.com
 http:
 paths:
 - backend:
 serviceName: svc-gateway
 servicePort: 80
 path: /api/v1/users
 - backend:
 serviceName: svc-messaging
 servicePort: 80
 path: /api/v1/messages
</code></pre>

If you have other containers running in the same namespace and would like to communicate with these services you can directly use their service names.

For example:
<code>curl http://svc-messaging</code> or <code>curl http://svc-gateway</code>

You don't need to run your own service discovery, that's taken care by Kubernetes!

Some visuals:

Step 1:
<a href="https://i.stack.imgur.com/XmqWW.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/XmqWW.png" alt="deployments"></a>

Step 2:
<a href="https://i.stack.imgur.com/OO6yB.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/OO6yB.png" alt="services"></a>

Step 3:
<a href="https://i.stack.imgur.com/adRzU.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/adRzU.png" alt="ingress"></a>

Let's say I am creating a chat app with microservice architecture. I have 2 services:

<ol>
<li>Gateway service: responsible for user authentication (API endpoint <code>/api/v1/users</code>), and routing requests to appropriate service.</li>
<li>Messaging service: responsible for creating, retrieving, updating, and deleting messages (API endpoint <code>/api/v1/messages</code>).</li>
</ol>

If I use Docker Compose or Kubernetes, how does my gateway service know which service should it forwards to if there is a request sending to <code>/api/v1/messages</code> API endpoint?

I used to write my own dynamic service discovery middleware (<a href="https://github.com/zicodeng/tahc-z/blob/master/servers/gateway/handlers/dsd.go" rel="nofollow noreferrer">https://github.com/zicodeng/tahc-z/blob/master/servers/gateway/handlers/dsd.go</a>). The idea is that I pre-register services with API endpoints they are responsible for. And my gateway service relies on request resource path to decide which service this request should be forwarded to. But how do you do this with Docker Compose or Kubernetes? Do I still need to keep my own version of dynamic service discovery middleware?

Thanks in advance!

How Does Dynamic Service Discovery Work When Using Docker Compose Or Kubernetes?

微服务架构

身份验证

Kubernetes

中间件

容器

Docker

路由

假设我正在创建一个具有微服务架构的聊天应用程序。我有两个服务：API网关服务:负责用户身份验证(API端点/api/v1/messages). )，并将请求路由到适当的服务:负责创建、检索、更新和删除消息(API端点 /api/v1/users)。如果我使用Docker Compose或Kubernetes，如果有请求...

问使用Docker Compose或Kubernetes时，动态服务发现是如何工作的？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Docker Compose或Kubernetes时，动态服务发现是如何工作的？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Docker Compose或Kubernetes时，动态服务发现是如何工作的？
EN