Guida di Riferimento Envoy Proxy

📋 Copy All Envoy Proxy Commands 📄 Generate Envoy Proxy PDF Guide

Piattaforma	Comando
Ubuntu/Debian	`curl -sL ‘https://deb.dl.getenvoy.io/public/gpg.8115BA8E629CC074.key’ \
macOS	brew install envoy
Docker	docker pull envoyproxy/envoy:v1.28-latest
Binary (Linux)	curl -L https://github.com/envoyproxy/envoy/releases/download/v1.28.0/envoy-1.28.0-linux-x86_64 -o envoy && chmod +x envoy && sudo mv envoy /usr/local/bin/
RHEL/CentOS	`curl -sL ‘https://rpm.dl.getenvoy.io/public/gpg.CF716AF503183491.key’ \
Kubernetes (Helm)	helm repo add bitnami https://charts.bitnami.com/bitnami && helm install my-envoy bitnami/envoy
Verify Installation	envoy --version

Guida di Riferimento Envoy Proxy

Installazione

Comando	Descrizione
envoy -c envoy.yaml	Avvia Envoy con il file di configurazione specificato
envoy --version	Mostra informazioni sulla versione di Envoy
envoy --help	Mostra tutte le opzioni disponibili della riga di comando
envoy --mode validate -c envoy.yaml	Convalida file di configurazione senza avviare
envoy -c envoy.yaml --log-level info	Inizia con un livello di log specifico (trace, debug, info, warn, error, critical)
envoy -c envoy.yaml --component-log-level upstream:debug	Imposta il livello di log per un componente specifico
envoy -c envoy.yaml --service-cluster my-cluster	Inizia con l’identificatore del cluster di servizio
envoy -c envoy.yaml --service-node node-1	Inizia con l’identificatore del nodo di servizio
envoy -c envoy.yaml --base-id 0	Imposta l’ID base per la funzionalità di hot restart
envoy -c envoy.yaml --restart-epoch 1	Esegui hot restart con numero di epoch
envoy -c envoy.yaml --drain-time-s 60	Imposta il tempo di drenaggio per l’arresto graceful (secondi)
envoy -c envoy.yaml --parent-shutdown-time-s 90	Imposta l’ora di arresto del parent durante l’hot restart
envoy -c envoy.yaml --concurrency 4	Imposta il numero di thread di lavoro
envoy -c envoy.yaml --disable-hot-restart	Disabilita la funzionalità di hot restart
envoy --help-hidden	Visualizza opzioni della riga di comando nascoste/avanzate

Comandi Base

Comando	Descrizione
curl http://localhost:9901/server_info	Ottieni informazioni sul server e stato corrente
curl http://localhost:9901/stats	Recupera tutte le statistiche in formato testo normale
curl http://localhost:9901/stats/prometheus	Esporta statistiche in formato Prometheus
curl http://localhost:9901/stats?format=json	Ottieni statistiche in formato JSON
curl http://localhost:9901/stats?filter=cluster.outbound	Filtra le statistiche per prefisso
curl http://localhost:9901/stats?usedonly	Mostra solo statistiche con valori diversi da zero
curl http://localhost:9901/config_dump	Dump configurazione corrente completa
curl http://localhost:9901/config_dump?resource=bootstrap	Dump solo la configurazione bootstrap
curl http://localhost:9901/config_dump?resource=dynamic_listeners	Dump configurazione listener dinamico
curl http://localhost:9901/config_dump?resource=dynamic_clusters	Dump configurazione cluster dinamico
curl http://localhost:9901/clusters	Ottieni informazioni dettagliate sul cluster e stato di salute
curl http://localhost:9901/listeners	Ottieni informazioni dettagliate sull’ascoltatore
curl http://localhost:9901/ready	Verifica se Envoy è pronto a servire il traffico
curl -X POST http://localhost:9901/healthcheck/fail	Contrassegna server come non funzionante per i controlli di integrità
curl -X POST http://localhost:9901/healthcheck/ok	Contrassegna il server come integro per i controlli di salute
curl -X POST http://localhost:9901/reset_counters	Azzera tutti i contatori delle statistiche
curl -X POST http://localhost:9901/drain_listeners	Svuotare i listener per un arresto graduale
curl -X POST http://localhost:9901/logging?level=debug	Modificare il livello di log globale durante l’esecuzione
curl -X POST http://localhost:9901/logging?upstream=debug	Cambia livello di log specifico del componente
curl -X POST http://localhost:9901/runtime_modify?key=value	Modificare i valori di configurazione del runtime

Comandi dell’Interfaccia Admin

Comando	Descrizione
`curl http://localhost:9901/stats \	grep circuit_breakers`
`curl http://localhost:9901/stats \	grep outlier_detection`
`curl http://localhost:9901/stats \	grep ratelimit`
`curl http://localhost:9901/stats \	grep upstream_rq_retry`
`curl http://localhost:9901/stats \	grep ssl`
`curl http://localhost:9901/stats \	grep http.ingress.downstream_rq`
`curl http://localhost:9901/clusters \	grep health_flags`
`curl http://localhost:9901/config_dump \	jq ‘.configs[].bootstrap.tracing’`
`curl http://localhost:9901/config_dump \	jq ‘.configs[].dynamic_active_clusters’`
`curl http://localhost:9901/stats?format=json \	jq ‘.stats[] \
`curl http://localhost:9901/listeners \	grep -A 5 “address”`
`curl http://localhost:9901/stats/prometheus \	grep envoy_cluster_upstream_rq_total`
docker run -d -v $(pwd)/envoy.yaml:/etc/envoy/envoy.yaml -p 9901:9901 -p 10000:10000 envoyproxy/envoy:v1.28-latest	Esegui Envoy in Docker con configurazione montata
kubectl create configmap envoy-config --from-file=envoy.yaml	Crea ConfigMap Kubernetes per la configurazione di Envoy
kubectl logs -f deployment/envoy	Segui i log di Envoy in Kubernetes
envoy -c envoy.yaml --log-format '[%Y-%m-%d %T.%e][%t][%l] %v'	Inizia con un formato di log personalizzato
curl http://localhost:9901/certs	Visualizza informazioni dei certificati TLS caricati
curl http://localhost:9901/memory	Mostra statistiche di allocazione della memoria
curl http://localhost:9901/contention	Visualizza le statistiche di contesa mutex (se abilitate)
curl -X POST http://localhost:9901/cpuprofiler?enable=y	Abilita il profiling della CPU (se compilato con profiling)

Utilizzo Avanzato

# envoy.yaml - Minimal configuration
static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address:
        address: 0.0.0.0
        port_value: 10000
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          route_config:
            name: local_route
            virtual_hosts:
            - name: backend
              domains: ["*"]
              routes:
              - match:
                  prefix: "/"
                route:
                  cluster: service_backend
          http_filters:
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router

  clusters:
  - name: service_backend
    connect_timeout: 0.25s
    type: STRICT_DNS
    lb_policy: ROUND_ROBIN
    load_assignment:
      cluster_name: service_backend
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: backend-service
                port_value: 8080

admin:
  address:
    socket_address:
      address: 0.0.0.0
      port_value: 9901

Configurazione

Struttura Base della Configurazione

# envoy-dynamic.yaml - Control plane configuration
node:
  cluster: my-cluster
  id: node-1

dynamic_resources:
  lds_config:
    resource_api_version: V3
    api_config_source:
      api_type: GRPC
      transport_api_version: V3
      grpc_services:
      - envoy_grpc:
          cluster_name: xds_cluster
  cds_config:
    resource_api_version: V3
    api_config_source:
      api_type: GRPC
      transport_api_version: V3
      grpc_services:
      - envoy_grpc:
          cluster_name: xds_cluster

static_resources:
  clusters:
  - name: xds_cluster
    connect_timeout: 1s
    type: STRICT_DNS
    lb_policy: ROUND_ROBIN
    http2_protocol_options: {}
    load_assignment:
      cluster_name: xds_cluster
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: control-plane
                port_value: 18000

admin:
  address:
    socket_address:
      address: 0.0.0.0
      port_value: 9901

Configurazione Dinamica (xDS)

# Circuit breaker and outlier detection
clusters:
- name: backend_service
  connect_timeout: 0.25s
  type: STRICT_DNS
  lb_policy: ROUND_ROBIN
  circuit_breakers:
    thresholds:
    - priority: DEFAULT
      max_connections: 1024
      max_pending_requests: 1024
      max_requests: 1024
      max_retries: 3
  outlier_detection:
    consecutive_5xx: 5
    interval: 30s
    base_ejection_time: 30s
    max_ejection_percent: 50
    enforcing_consecutive_5xx: 100
  load_assignment:
    cluster_name: backend_service
    endpoints:
    - lb_endpoints:
      - endpoint:
          address:
            socket_address:
              address: backend
              port_value: 8080
          health_check_config:
            port_value: 8081

Configurazione Funzionalità Avanzate

# TLS termination
listeners:
- name: https_listener
  address:
    socket_address:
      address: 0.0.0.0
      port_value: 443
  filter_chains:
  - filters:
    - name: envoy.filters.network.http_connection_manager
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
        stat_prefix: ingress_https
        route_config:
          name: local_route
          virtual_hosts:
          - name: backend
            domains: ["*"]
            routes:
            - match:
                prefix: "/"
              route:
                cluster: backend_service
        http_filters:
        - name: envoy.filters.http.router
          typed_config:
            "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
    transport_socket:
      name: envoy.transport_sockets.tls
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext
        common_tls_context:
          tls_certificates:
          - certificate_chain:
              filename: /etc/ssl/certs/server.crt
            private_key:
              filename: /etc/ssl/private/server.key

Configurazione TLS

# Create configuration file
cat > envoy.yaml << EOF
static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address:
        address: 0.0.0.0
        port_value: 8080
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          route_config:
            name: local_route
            virtual_hosts:
            - name: backend
              domains: ["*"]
              routes:
              - match:
                  prefix: "/"
                route:
                  cluster: backend_cluster
          http_filters:
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
  clusters:
  - name: backend_cluster
    connect_timeout: 0.25s
    type: STRICT_DNS
    lb_policy: ROUND_ROBIN
    load_assignment:
      cluster_name: backend_cluster
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: localhost
                port_value: 3000
admin:
  address:
    socket_address:
      address: 0.0.0.0
      port_value: 9901
EOF

# Start Envoy
envoy -c envoy.yaml

# Test the proxy
curl http://localhost:8080

# Monitor statistics
curl http://localhost:9901/stats | grep http

Casi d’Uso Comuni

Caso d’Uso: Proxy HTTP Base

Configurare Envoy come un semplice proxy HTTP che inoltra il traffico ai servizi backend.

# Create load balancing configuration
cat > envoy-lb.yaml << EOF
static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address:
        address: 0.0.0.0
        port_value: 8080
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          route_config:
            name: local_route
            virtual_hosts:
            - name: backend
              domains: ["*"]
              routes:
              - match:
                  prefix: "/"
                route:
                  cluster: backend_cluster
          http_filters:
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
  clusters:
  - name: backend_cluster
    connect_timeout: 0.25s
    type: STRICT_DNS
    lb_policy: ROUND_ROBIN
    health_checks:
    - timeout: 1s
      interval: 10s
      unhealthy_threshold: 2
      healthy_threshold: 2
      http_health_check:
        path: /health
    load_assignment:
      cluster_name: backend_cluster
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: backend1.example.com
                port_value: 8080
        - endpoint:
            address:
              socket_address:
                address: backend2.example.com
                port_value: 8080
        - endpoint:
            address:
              socket_address:
                address: backend3.example.com
                port_value: 8080
admin:
  address:
    socket_address:
      address: 0.0.0.0
      port_value: 9901
EOF

# Start Envoy with load balancing
envoy -c envoy-lb.yaml

# Check cluster health status
curl http://localhost:9901/clusters

# Monitor load distribution
watch -n 1 'curl -s http://localhost:9901/stats | grep backend_cluster.upstream_rq_total'

Caso d’Uso: Bilanciamento del Carico su Più Backend

Configurare Envoy per bilanciare il carico tra più istanze backend con controllo di salute.

# Generate self-signed certificates for testing
openssl req -x509 -newkey rsa:4096 -keyout server.key -out server.crt -days 365 -nodes -subj "/CN=localhost"

# Create TLS configuration
cat > envoy-tls.yaml << EOF
static_resources:
  listeners:
  - name: https_listener
    address:
      socket_address:
        address: 0.0.0.0
        port_value: 443
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_https
          route_config:
            name: local_route
            virtual_hosts:
            - name: backend
              domains: ["*"]
              routes:
              - match:
                  prefix: "/"
                route:
                  cluster: secure_backend
          http_filters:
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
      transport_socket:
        name: envoy.transport_sockets.tls
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext
          common_tls_context:
            tls_certificates:
            - certificate_chain:
                filename: server.crt
              private_key:
                filename: server.key
  clusters:
  - name: secure_backend
    connect_timeout: 0.25s
    type: STRICT_DNS
    lb_policy: ROUND_ROBIN
    transport_socket:
      name: envoy.transport_sockets.tls
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
    load_assignment:
      cluster_name: secure_backend
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: backend.example.com
                port_value: 443
admin:
  address:
    socket_address:
      address: 0.0.0.0
      port_value: 9901
EOF

# Start Envoy with TLS
envoy -c envoy-tls.yaml

# Test TLS connection
curl -k https://localhost

# Check TLS statistics
curl http://localhost:9901/stats | grep ssl

Caso d’Uso: Terminazione e Re-crittografia TLS

Configurare Envoy per terminare TLS dai client e ri-crittografare verso i backend.

# Create resilience configuration
cat > envoy-resilience.yaml << EOF
static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address:
        address: 0.0.0.0
        port_value: 8080
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          route_config:
            name: local_route
            virtual_hosts:
            - name: backend
              domains: ["*"]
              routes:
              - match:
                  prefix: "/"
                route:
                  cluster: protected_backend
                  retry_policy:
                    retry_on: "5xx"
                    num_retries: 3
                    per_try_timeout: 1s
          http_filters:
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
  clusters:
  - name: protected_backend
    connect_timeout: 0.25s
    type: STRICT_DNS
    lb_policy: ROUND_ROBIN
    circuit_breakers:
      thresholds:
      - priority: DEFAULT
        max_connections: 100
        max_pending_requests: 100
        max_requests: 100
        max_retries: 3
    outlier_detection:
      consecutive_5xx: 5
      interval: 10s
      base_ejection_time: 30s
      max_ejection_percent: 50
    load_assignment:
      cluster_name: protected_backend
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: backend.example.com
                port_value: 8080
admin:
  address:
    socket_address:
      address: 0.0.0.0
      port_value: 9901
EOF

# Start Envoy with resilience features
envoy -c envoy-resilience.yaml

# Monitor circuit breaker status
curl http://localhost:9901/stats | grep circuit_breakers

# Check outlier detection events
curl http://localhost:9901/stats | grep outlier_detection

# View retry statistics
curl http://localhost:9901/stats | grep retry

Caso d’Uso: Rate Limiting e Circuit Breaking

Implementare rate limiting e circuit breaking per una comunicazione di servizi resiliente.

Caso d’Uso: Osservabilità con Tracciamento Distribuito

Configurare Envoy con tracciamento distribuito per l’osservabilità dei microservizi.

# Creare configurazione di tracciamento
cat > envoy-tracing.yaml << EOF
static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address:
        address: 0.0.0.0
        port_value: 8080
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix