Bug 1467684 - [RFE] Limit the maximum number of concurrent connections a pod can receive through a route annotation
[RFE] Limit the maximum number of concurrent connections a pod can receive th...
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE (Show other bugs)
3.5.0
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Eric Paris
Xiaoli Tian
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-04 10:57 EDT by Sergi Jimenez Romero
Modified: 2017-07-24 09:56 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Origin (Github) 14822 None None None 2017-07-04 10:59 EDT

  None (edit)
Description Sergi Jimenez Romero 2017-07-04 10:57:55 EDT
> 3. What is the nature and description of the request?

Through a route annotation, I want to be able to set the maximum number of concurrent connections a pod exposed under a route can receive. If the pod were to be scaled, the new replicas would inherit the same limit. E.g. if limit is 100 connectoins for a single pod and it's scaled up to 4 replicas, the new limit would be 4x100.

Some use cases:

As a developer, I want that the platform controls the amount of traffic my app can receive. This can save my app from going down under extreme loads.

As a project admin, I want to protect the apps that are exposed externally through routes from DDoS like attacks.

> 4. Why does the customer need this? (List the business requirements here)

To limit app traffic, and avoid apps from going down under extreme loads.
To protect the apps that are exposed externally through routes from DDoS like attacks.

> 5. How would the customer like to achieve this? (List the functional requirements here)

By specifying a route annotation.

> 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Having a route annotation will effectively limit connections against a pod.

10. List any affected packages or components.
Router and routes.

Note You need to log in before you can comment on or make changes to this bug.