[zh]fix 2018 blogs: add slug and remove url
This commit is contained in:
@@ -1,16 +1,16 @@
|
||||
---
|
||||
title: 'Kubernetes 内的动态 Ingress'
|
||||
title: 'Kubernetes 的动态 Ingress'
|
||||
date: 2018-06-07
|
||||
layout: blog
|
||||
Author: Richard Li (Datawire)
|
||||
slug: dynamic-ingress-in-kubernetes
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Dynamic Ingress in Kubernetes
|
||||
date: 2018-06-07
|
||||
Author: Richard Li (Datawire)
|
||||
-->
|
||||
|
||||
作者: Richard Li (Datawire)
|
||||
|
||||
<!--
|
||||
Kubernetes makes it easy to deploy applications that consist of many microservices, but one of the key challenges with this type of architecture is dynamically routing ingress traffic to each of these services. One approach is Ambassador, a Kubernetes-native open source API Gateway built on the Envoy Proxy. Ambassador is designed for dynamic environment where services may come and go frequently.
|
||||
Ambassador is configured using Kubernetes annotations. Annotations are used to configure specific mappings from a given Kubernetes service to a particular URL. A mapping can include a number of annotations for configuring a route. Examples include rate limiting, protocol, cross-origin request sharing, traffic shadowing, and routing rules.
|
||||
|
||||
Reference in New Issue
Block a user