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.

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

[SPIKE] What NGINX functionality should we plan for? #1410

Closed
mpstefan opened this issue Dec 19, 2023 · 1 comment
Closed

[SPIKE] What NGINX functionality should we plan for? #1410

mpstefan opened this issue Dec 19, 2023 · 1 comment
Assignees
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

Comments

@mpstefan
Copy link
Collaborator

mpstefan commented Dec 19, 2023

As an NGINX product, we need to identify a set of high-priority nginx directives to plan for implementation for NGF maintainers and contributors. This spike is to identify that set of functionality and document them.

  1. What set of NGINX directives/features are the most important to include using Ingress as a baseline?
  2. How large of a set is feasible?
  3. Where can we document the set of functionality that is planned for implementation?
@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 mpstefan added this to the v1.2.0 milestone Jan 3, 2024
@mpstefan mpstefan added the refined Requirements are refined and the issue is ready to be implemented. label Jan 3, 2024
@mpstefan
Copy link
Collaborator Author

mpstefan commented Jan 3, 2024

Check this doc for a subset of NGINX configuration: #708

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

3 participants