-
Notifications
You must be signed in to change notification settings - Fork 141
Closed
Labels
area/nginx-configurationRelates to nginx configurationRelates to nginx configurationrefinedRequirements are refined and the issue is ready to be implemented.Requirements are refined and the issue is ready to be implemented.spikeIssue to investigate a problem or solution, but not implement.Issue to investigate a problem or solution, but not implement.
Milestone
Description
Once the groups of NGINX functionality are organized, we need to determine the best way to utilize extension points and attachment to apply the configuration to NGINX in a Gateway API oriented way.
- What attachment or extension points should each group of NGINX functionality use?
- What resources does each group affect?
- Where can we document the results of this spike?
When we answer the above questions, we want an enhancement proposal to be created that describes the outcome of the functionality grouping.
Metadata
Metadata
Assignees
Labels
area/nginx-configurationRelates to nginx configurationRelates to nginx configurationrefinedRequirements are refined and the issue is ready to be implemented.Requirements are refined and the issue is ready to be implemented.spikeIssue to investigate a problem or solution, but not implement.Issue to investigate a problem or solution, but not implement.