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

Build next NGINX image with NJS #11020

Open
rikatz opened this issue Feb 26, 2024 · 3 comments
Open

Build next NGINX image with NJS #11020

rikatz opened this issue Feb 26, 2024 · 3 comments
Assignees
@rikatz
Labels
kind/design Categorizes issue or PR as related to design. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@rikatz
Copy link
Contributor

rikatz commented Feb 26, 2024

NJS provides an easy way of scripting for NGINX.

Some features from openresty and from external nginx modules can be replaced by njs scripts.

We should:

  • Build the next NGINX image with NJS
  • Analyze and map all the modules / modules features, and what can be replaced by some NJS script
  • Make sure that there is no way a user can call njs from annotations
@rikatz rikatz added the kind/design Categorizes issue or PR as related to design. label Feb 26, 2024
@rikatz rikatz self-assigned this Feb 26, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 26, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@github-actions GitHub Actions
Copy link

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

@github-actions github-actions bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Mar 28, 2024
@longwuyuan
Copy link
Contributor

#12383

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rikatz rikatz

Labels
kind/design Categorizes issue or PR as related to design. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
[SIG Network] Ingress NGINX
Status: No status
Milestone
No milestone
Development

No branches or pull requests
3 participants
@longwuyuan @rikatz @k8s-ci-robot