Skip to content

Design for Technical Solutions for NGINX Customization #815

Closed
@mpstefan

Description

@mpstefan

Before pursuing a specific solution like NGINX Template Customization, we want to do a technical spike to investigate what solutions could be employed to allow users to customize NGINX behavior.

At the end of the spike, we want to determine:

  1. What solutions can be used to customize which behaviors?
  2. How much complexity and time will the solutions cost?
  3. What are the implications for security?
  4. What are the implications for support, when available?

The results of this investigation should be added to the provisional enhancement proposal for NGINX Customization.

Notes from our meetup on extensibility requirements are available here.

The answers to the above questions should be posted in the discussion here.

Metadata

Metadata

Assignees

Labels

refinedRequirements are refined and the issue is ready to be implemented.spikeIssue to investigate a problem or solution, but not implement.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions