Shulou(Shulou.com)06/03 Report--

At present, open source projects in the industry based on cloud native ideas focus on the management and control of micro-services and the communication between services under the micro-service architecture. They effectively solve the problem of east/west traffic control caused by "service isomerization", "dynamic" and "multi-protocol" scenarios, while the flow control for north/south only provides ingress/egress as the management of flow entry and exit.

In order to solve the problem of north/south flow control in the cloud native environment, Ambassador began to come into everyone's attention. Ambassador is a gateway, in which Enovy is used as the executor of specific policies, and Ambassador is abstracted to the control plane to issue some gateway control instructions. The specific architecture is as follows:

From the architecture diagram, we can clearly see that Ambassador is extended from the Enovy foundation, and the design idea of "control plane" and data plane is also adopted. In the container ecological environment, both the traefik of kubernetes and the Ingress-gateway of istio are powerful extensions.

What are the features of Ambassador?

Isomerization service support

Each service under the cloud native architecture requires only to follow the same communication specification, so it no longer emphasizes the consistency issues such as language, architecture and so on. Ambassador happens to be able to effectively import request traffic to various heterogeneous services, and complete the management and control of service requests.

Support the configuration based on each service, and further achieve fine-grained control at the gateway level, such as "timeout", "rate limit", "authentication policy" and so on.

Can support different levels of communication protocols, L7 protocols include HTTP, HTTP/2, grpc, trpc-web, websocket,L4 protocols TCP.

Dynamic service

Service updates can cause applications to change. Ambassador can amicably support the dynamic characteristics of cloud native applications, with the following features:

Allow production testing and support different grayscale publishing strategies

Refine observability indicators and effectively control service behavior

Insensitive changes to configuration information will not affect the end user

Decentralized workflow

Cloud native applications allow different service developers to optimize their own services.

In order to meet this feature, Ambassador can allow each development team to maintain its own services, and independently access and use the configuration information of Ambassador, changing the previous gateway layer configuration change ideas, so as to avoid affecting other running services.

Ambassador deployment

Ambassador provides a variety of different deployment methods to meet the needs of users. It includes kubernetes yaml deployment, helm deployment, docker image deployment and docker compose deployment. It can not only run as an independent program to provide gateway capabilities, but also integrate with cloud native frameworks such as kubernetes,istio to act as the manager of ingress traffic.

Use docker image deployment to illustrate the deployment configuration of Ambassador.

Docker run-it-d-p 808014-name=ambassador-- rm quay.io/datawire/ambassador:0.73.0-- demo

Check the Ambassador log to determine the operation.

AMBASSADOR: using'/ ambassador/ambassador-demo-config' for configuration

AMBASSADOR: not watching for Kubernetes config

2019-07-17 08:22:55 kubewatch [9 TMainThread] 0.73.0 INFO: No K8s

2019-07-17 08:22:55 kubewatch [9 TMainThread] 0.73.0 DEBUG: cluster ID URL is d6e_id://00000000-0000-0000-0000-000000000000/default

2019-07-17 08:22:55 kubewatch [9 TMainThread] 0.73.0 DEBUG: Kubernetes is not available, so not doing CRD check

2019-07-17 08:22:55 kubewatch [9 TMainThread] 0.73.0 DEBUG: cluster ID is 07eb43c8-1166-5145-a060-45e4dd907e10 (from hardcoded ID)

AMBASSADOR: starting with environment:

=

AMBASSADOR_CLUSTER_ID=07eb43c8-1166-5145-a060-45e4dd907e10

AMBASSADOR_CONFIG_BASE_DIR=/ambassador

AMBASSADOR_NAMESPACE=default

AMBASSADOR_NO_KUBEWATCH=no_kubewatch

AMBASSADOR_ROOT=/ambassador

=

AMBASSADOR: launching worker process: 'env'' PORT=5050' 'python3'' demo-services/auth.py'

AMBASSADOR: launching worker process: 'python3'' demo-services/qotm.py'

AMBASSADOR: starting ads

.

08:24:00] "GET / auth/v0//ambassador/v0/favicon.ico HTTP/1.1" 200-

ACCESS [2019-07-17T08:23:59.084Z] "GET / ambassador/v0/diag/ HTTP/1.1" 200-0 17012 69 62 "10.20.50.164"Mozilla/5.0 (Macintosh; Intel Mac OS X 10-14-5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36"7481ee18-307e-4d23-9c82-e0a623389655"10.20.1.180 Fran 8080"127.0.0.1Ze8877"

ACCESS [2019-07-17T08:24:00.254Z] "GET / ambassador/v0/favicon.ico HTTP/1.1" 401 UAEX 057 4-"10.20.50.164"Mozilla/5.0 (Macintosh; Intel Mac OS X 101405) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36"0013e864-1128-4e03-8814-49ed6e498d11"10.20.1.180 8080"-"

ACCESS [2019-07-17T08:24:00.259Z] "GET / ambassador/v0/favicon.ico HTTP/1.1" 200-0 1150 8 4 "10.20.50.164"Mozilla/5.0 (Macintosh; Intel Mac OS X 10-14-5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36"9b0702c0-3800-4447-90aa-6bebb5a711fb"10.20.1.180 8080" 127.0.0.1 ambassador/v0/favicon.ico HTTP/1.1 8877 "

When starting based on docker image, ambassador uses the default config configuration information to complete the initialization work.

Visit Ambassador:

Http://{ip}:8080/ambassador/v0/diag/

Initialize the default username admin and password admin. You can see the visit page normally.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.