nginx / nginx/documentation

[Story]: Airgapped NIM installation on k8s & openshift using Helm

Open
#1,335 0 comments 0 reactions 1 assignee View on GitHub

@travisamartin is already working on this.

Since Nov 12, 2025.

P3 - Normal (TTR: 1 month) product/nim
Dominant language
HTML
Stars
94
Forks
174
Avg merge
1d 10h
Merged PRs (30d)
66

Description

Overview

As a user, I want to deploy NGINX Instance Manager on my air-gapped kubernetes/openshift cluster using Helm. This will allow me to seamlessly manage NIM's entire operational lifecycle

Which product or products does this request relate to?

NGINX Instance Manager

Description

NGINX documentation provides steps needed to deploy NGINX Instance Manager on a "disconnected" virtual machine (see https://docs.nginx.com/nginx-instance-manager/disconnected/offline-install-guide/). Several users share the same requirements/infrastructure:

  • Kubernetes and/or Openshift clusters
  • Fully airgapped / no Internet connectivity
  • Helm used to manage all software deployments

The docs should include a section providing walkthrough guidance on how to deploy and upgrade NGINX Instance Manager by complying with these requirements

Acceptance criteria

As a user, I want to be able to follow the documentation to successfully deploy NGINX Instance Manager on my Internet-disconnected Kubernetes / Openshift cluster. The documentation should allow me to run NIM and publish it through my cluster's Ingress Controller (ideally, NGINX Ingress Controller) and optionally NGINX Gateway Fabric, that I might already be running in my cluster.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.