Overview:

A high level summary that describes the Epic in a clear, concise way. Complete during New status.

Currently, the routes are created as passthrough or re-encrypt without the insecureEdgeTerminationPolicy set to Redirect. This means that users who navigate to the Central URL using http:// will not be automatically redirected to https://.

The proposal is to modify the default configuration to set insecureEdgeTerminationPolicy: Redirect for the Central routes.

Additionally, a new field should be introduced in the Central Custom Resource (CR) to allow administrators to easily enable or disable this redirection.

Requirements:

A list of specific needs or objectives that an epic must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc. Initial completion during Refinement status.

<enter general Epic requirements here>

Technical Scope:

High-level list of items that are in scope; usually completed by a staff engineer or a lead from the Feature Delivery Team. Initial completion during Refinement status.

<your text here>

Out of Scope:

High-level list of items that are out of scope. Initial completion during Refinement status.

<your text here>

Outstanding Questions (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.

<your text here>