Using Emissary-ingress

Application development teams use Emissary-ingress to manage edge policies associated with a specific service. This section of the documentation covers core Emissary-ingress elements that are typically used by the application development team.

• Introduction to Mappings The Mapping resource is the core resource used by every application development team.
• Mapping Configuration:
  • Automatic Retries
  • Canary Releases
  • Circuit Breakers
  • Cross Origin Resource Sharing
  • HTTP Headers
    • Header-based Routing
    • Host Header
    • Adding Request Headers
    • Adding Response Headers
    • Removing Request Headers
    • Remove Response Headers
  • Query Parameter Based Routing
  • Keepalive
  • Protocols
    • TCP
    • gRPC, HTTP/1.0, gRPC-Web, WebSockets
  • RegEx-based Routing
  • Redirects
  • Rewrites
  • Timeouts
  • Traffic Shadowing
• Advanced Mapping Configuration
• Rate Limiting
  • Introduction to Rate Limits
• Developer Portal
• Gateway API