Zum Inhalt

Envoy Proxy

Plattform Befehl
Ubuntu/Debian curl -sL 'https://deb.dl.getenvoy.io/public/gpg.8115BA8E629CC074.key' \ | gpg --dearmor -o /usr/share/keyrings/getenvoy-keyring.gpg && echo "deb [arch=amd64 signed-by=/usr/share/keyrings/getenvoy-keyring.gpg] https://deb.dl.getenvoy.io/public/deb/ubuntu $(lsb_release -cs) main" \ | sudo tee /etc/apt/sources.list.d/getenvoy.list && sudo apt update && sudo apt install -y getenvoy-envoy
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' \ | sudo rpm --import - && sudo yum-config-manager --add-repo https://rpm.dl.getenvoy.io/public/rpm/el/8/x86_64 && sudo yum install -y getenvoy-envoy
Kubernetes (Helm) helm repo add bitnami https://charts.bitnami.com/bitnami && helm install my-envoy bitnami/envoy
Verify Installation envoy --version
# Envoy Proxy Spickzettel

Installation

Befehl Beschreibung
envoy -c envoy.yaml Starten Sie Envoy mit der angegebenen Konfigurationsdatei
envoy --version Envoy-Versionsinformationen anzeigen
envoy --help Zeige alle verfügbaren Befehlszeilenoptionen
envoy --mode validate -c envoy.yaml Konfigurationsdatei ohne Start validieren
envoy -c envoy.yaml --log-level info Beginnen Sie mit einer bestimmten Log-Ebene (trace, debug, info, warn, error, critical)
envoy -c envoy.yaml --component-log-level upstream:debug Log-Level für bestimmte Komponente festlegen
envoy -c envoy.yaml --service-cluster my-cluster Beginnen Sie mit der Service-Cluster-Kennung
envoy -c envoy.yaml --service-node node-1 Beginnen Sie mit der Service-Node-Kennung
envoy -c envoy.yaml --base-id 0 Basis-ID für Hot-Restart-Funktionalität festlegen
envoy -c envoy.yaml --restart-epoch 1 Führen Sie einen Hot Restart mit Epochennummer durch
envoy -c envoy.yaml --drain-time-s 60 Drain-Zeit für einen ordnungsgemäßen Shutdown festlegen (Sekunden)
envoy -c envoy.yaml --parent-shutdown-time-s 90 Eltern-Shutdown-Zeit während des Hot Restart festlegen
envoy -c envoy.yaml --concurrency 4 Anzahl der Worker-Threads festlegen
envoy -c envoy.yaml --disable-hot-restart Hot Restart-Funktionalität deaktivieren
envoy --help-hidden Ausgeblendete/erweiterte Befehlszeilenoptionen anzeigen
## Grundlegende Befehle
Befehl Beschreibung
curl http://localhost:9901/server_info Server-Informationen und aktuellen Status abrufen
curl http://localhost:9901/stats Rufe alle Statistiken im Plain-Text-Format ab
curl http://localhost:9901/stats/prometheus Exportstatistiken im Prometheus-Format
curl http://localhost:9901/stats?format=json Statistiken im JSON-Format abrufen
curl http://localhost:9901/stats?filter=cluster.outbound Statistiken nach Präfix filtern
curl http://localhost:9901/stats?usedonly Zeige nur Statistiken mit Werten ungleich Null
curl http://localhost:9901/config_dump Aktuelle Konfiguration vollständig ablegen
curl http://localhost:9901/config_dump?resource=bootstrap Nur Bootstrap-Konfiguration ablegen
curl http://localhost:9901/config_dump?resource=dynamic_listeners Dynamische Listener-Konfiguration ablegen
curl http://localhost:9901/config_dump?resource=dynamic_clusters Dynamische Cluster-Konfiguration ablegen
curl http://localhost:9901/clusters Detaillierte Cluster-Informationen und Gesundheitsstatus abrufen
curl http://localhost:9901/listeners Detaillierte Listener-Informationen abrufen
curl http://localhost:9901/ready Überprüfe, ob Envoy bereit ist, Verkehr zu bedienen
curl -X POST http://localhost:9901/healthcheck/fail Server für Gesundheitschecks als fehlgeschlagen markieren
curl -X POST http://localhost:9901/healthcheck/ok Server für Gesundheitschecks als gesund markieren
curl -X POST http://localhost:9901/reset_counters Alle Statistik-Zähler auf Null zurücksetzen
curl -X POST http://localhost:9901/drain_listeners Listener für einen eleganten Shutdown abbauen
curl -X POST http://localhost:9901/logging?level=debug Log-Level global zur Laufzeit ändern
curl -X POST http://localhost:9901/logging?upstream=debug Log-Level für Komponente ändern
curl -X POST http://localhost:9901/runtime_modify?key=value Laufzeit-Konfigurationswerte ändern
## Admin-Schnittstellen-Befehle
Befehl Beschreibung
curl http://localhost:9901/stats \ | grep circuit_breakers Schaltkreissicherungs-Statistiken überwachen
curl http://localhost:9901/stats \ | grep outlier_detection Überprüfe Ausreißererkennung-Ereignisse
curl http://localhost:9901/stats \ | grep ratelimit Rate Limiting-Statistiken anzeigen
curl http://localhost:9901/stats \ | grep upstream_rq_retry Monitor-Wiederholungsstatistiken
curl http://localhost:9901/stats \ | grep ssl TLS/SSL-Verbindungsstatistiken überprüfen
curl http://localhost:9901/stats \ | grep http.ingress.downstream_rq Eingehende HTTP-Anfragen überwachen
curl http://localhost:9901/clusters \ | grep health_flags Cluster-Gesundheitsstatus-Flags überprüfen
curl http://localhost:9901/config_dump \ | jq '.configs[].bootstrap.tracing' Tracing-Konfiguration extrahieren
curl http://localhost:9901/config_dump \ | jq '.configs[].dynamic_active_clusters' Aktive dynamische Cluster anzeigen
curl http://localhost:9901/stats?format=json \ | jq '.stats[] \ | select(.name \ | contains("upstream_cx_"))' Verbindungsstatistiken mit jq filtern
curl http://localhost:9901/listeners \ | grep -A 5 "address" Listener-Adressen und Ports anzeigen
curl http://localhost:9901/stats/prometheus \ | grep envoy_cluster_upstream_rq_total Metrik zu Prometheus exportieren
docker run -d -v $(pwd)/envoy.yaml:/etc/envoy/envoy.yaml -p 9901:9901 -p 10000:10000 envoyproxy/envoy:v1.28-latest Envoy in Docker mit eingebundener Konfiguration ausführen
kubectl create configmap envoy-config --from-file=envoy.yaml Erstellen Sie Kubernetes ConfigMap für Envoy-Konfiguration
kubectl logs -f deployment/envoy Envoy-Logs in Kubernetes verfolgen
envoy -c envoy.yaml --log-format '[%Y-%m-%d %T.%e][%t][%l] %v' Mit benutzerdefiniertem Protokollformat beginnen
curl http://localhost:9901/certs Geladene TLS-Zertifikate-Informationen anzeigen
curl http://localhost:9901/memory Speicherbelegungsstatistiken anzeigen
curl http://localhost:9901/contention Mutex-Konfliktsstatistiken anzeigen (falls aktiviert)
curl -X POST http://localhost:9901/cpuprofiler?enable=y CPU-Profiling aktivieren (falls mit Profiling kompiliert)
## Erweiterte Nutzung 
# 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
## Konfiguration

Grundlegende Konfigurationsstruktur

# 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

Dynamische Konfiguration (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

Erweiterte Funktionen-Konfiguration

# 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

TLS-Konfiguration

# 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

Häufige Anwendungsfälle

Anwendungsfall: Einfacher HTTP-Proxy

Richten Sie Envoy als einfachen HTTP-Proxy ein, der Datenverkehr an Backend-Dienste weiterleitet. 

# 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'

Anwendungsfall: Lastverteilung mehrerer Backends

Konfigurieren Sie Envoy zur Lastverteilung über mehrere Backend-Instanzen mit Gesundheitsprüfung. 

# 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

Anwendungsfall: TLS-Terminierung und Neu-Verschlüsselung

Konfigurieren Sie Envoy zur TLS-Terminierung von Clients und Neu-Verschlüsselung zu Backends. 

# 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

Anwendungsfall: Ratenbegrenzung und Schutzschaltung

Implementieren Sie Ratenbegrenzung und Schutzschaltung für robuste Dienst-Kommunikation.