Ingress Controller Features

[kshinn]

I started thinking about what kind of requirements would be needed for an ingress. As a starting point for a discussion, I'll post what I was thinking:

Since this would be routing in a dynamic environment, flexibility and ease of traffic control would be a primary quality to focus on. We would want to give operators control over traffic shaping, upstream weighting, and routing according to the governance and current capabilities of the overall network participants.

• Support multiple upstreams
• Implement a reputation metric based on an arbitrary combination of relevant qualities
  • Latency
  • Uptime
  • Data correctness
• Be able to select upstreams weighted on the reputation metric
• May persist reputational metrics into shared datastores such as Redis
• Should be able to randomly sample correct answers between 2 providers
• Dynamically change configs with no downtime
• Enabling response to traffic / incident conditions without requiring deployment
• Provide configuration through SRV, Consul, central configuration storage
• Support request / response compression
• Support routing via any combination of:
  • jsonrpc method name using wild card semantics
  • Custom header values
  • Project key routing
• Support multiple domain names or high level “server routes”