[Story]: Unprivileged/non-root NGINX deployment on k8s & openshift
@y82 is already working on this.
Since Oct 20, 2025.
- Dominant language
- HTML
- Stars
- 94
- Forks
- 174
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 66
Description
Overview
As a user I want to run NGINX Plus in my Kubernetes and Openshift clusters as an unprivileged/non-root ("regular", non-ingress) pod. I'm expecting to get all fully documented steps to achieve that.
Which product or products does this request relate to?
NGINX Plus
Description
Documentation currently provides details and steps to run NGINX Plus on docker (https://docs.nginx.com/nginx/admin-guide/installing-nginx/installing-nginx-docker/) but there's nothing when the target infrastructure is kubernetes (or Openshift, which is common across EMEA).
Additionally, when deploying on Openshift, customers often have to comply with unprivileged uid and gid numbering (see https://www.redhat.com/en/blog/a-guide-to-openshift-and-uids).
The new documentation section should provide a full walkthrough allowing the user to:
- either pull a pre-built NGINX Plus "non-root" docker image from the F5 private registry or build a docker image based on a Dockerfile (for instance https://github.com/nginx/nginx-demos/tree/main/nginx/docker-image-builder). The docker image should optionally include the NGINX agent v2 or v3 and support unprivileged
gidanduid - provide sample manifests that can be used to deploy NGINX Plus on a Kubernetes or OpenShift cluster. The manifest(s) should support passing parameters to the NGINX agent in order to connect the NGINX pod to either NGINX Instance Manager or NGINX One Console
Acceptance criteria
As a user I want to be able to follow the documentation to deploy an unprivileged/non-root NGINX Plus pod in my Kubernetes and/or Openshift cluster. All steps should be fully described and I should be required to make only small modifications to the example manifests to get things up and running
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.