Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[SPIKE] What extension points should each functionality group utilize? #1411

Closed
mpstefan opened this issue Dec 19, 2023 · 2 comments · Fixed by #1567
Closed

[SPIKE] What extension points should each functionality group utilize? #1411

mpstefan opened this issue Dec 19, 2023 · 2 comments · Fixed by #1567
Assignees
@kate-osborn
Labels
area/nginx-configuration Relates to nginx configuration refined Requirements are refined and the issue is ready to be implemented. spike Issue to investigate a problem or solution, but not implement.
Milestone
v1.2.0

Comments

@mpstefan
Copy link
Collaborator

mpstefan commented Dec 19, 2023 •
edited
Loading

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.

  1. What attachment or extension points should each group of NGINX functionality use?
  2. What resources does each group affect?
  3. 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.
@mpstefan mpstefan mentioned this issue Dec 19, 2023
Closed
@mpstefan mpstefan added area/nginx-configuration Relates to nginx configuration spike Issue to investigate a problem or solution, but not implement. labels Dec 19, 2023
@mpstefan
Copy link
Collaborator Author

Some useful links:

Extension Points
Policy Attachment
Last extension point - TLS options in a Listener of the Gateway

@pleshakov
Copy link
Contributor

One more extension point - per Gateway Infrastructure field -- https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.GatewayInfrastructure. (currently, experimental)

@mpstefan mpstefan added this to the v1.2.0 milestone Jan 10, 2024
@mpstefan mpstefan added the refined Requirements are refined and the issue is ready to be implemented. label Jan 10, 2024
@mpstefan mpstefan mentioned this issue Jan 22, 2024
Closed
@kate-osborn kate-osborn self-assigned this Jan 25, 2024
@kate-osborn kate-osborn mentioned this issue Feb 13, 2024
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kate-osborn kate-osborn

Labels
area/nginx-configuration Relates to nginx configuration refined Requirements are refined and the issue is ready to be implemented. spike Issue to investigate a problem or solution, but not implement.
Projects
None yet
Milestone
v1.2.0
Development

Successfully merging a pull request may close this issue.

Add NGINX extensions enhancement proposal kate-osborn/nginx-gateway-fabric
3 participants
@pleshakov @mpstefan @kate-osborn