Skip to content

fix: cleanup of nim charts + minor fixes #737

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

Merged
merged 4 commits into from
Jun 26, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/includes/nim/kubernetes/access-webui-helm.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,10 @@ You can access the NGINX Instance Manager web interface using the external IP ad
1. To look up the external IP address for the API Gateway, run the following command:

```bash
kubectl -n nms get svc apigw
kubectl -n nim get svc apigw
```

This `kubectl` command retrieves the service named `apigw` from the namespace `nms`. It outputs the details of the service, such as its type, port, cluster and external IP addresses.
This `kubectl` command shows details for the `apigw` service in the `nim` namespace. You’ll see the service type, port, cluster IP, and external IP addresses.

The default service type is `ClusterIP` and the output looks similar to the following example:

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -20,24 +20,5 @@ docs: DOCS-1324
| 1.10.1 | ngnx-stable/nms | 2.13.1 |
| 1.10.0 | ngnx-stable/nms | 2.13.1 |
| 1.9.0 | ngnx-stable/nms | 2.13.0 |
| 1.8.2 | ngnx-stable/nms | 2.12.0 |
| 1.8.1 | ngnx-stable/nms | 2.12.0 |
| 1.8.0 | ngnx-stable/nms | 2.12.0 |
| 1.7.2 | ngnx-stable/nms | 2.11.0 |
| 1.7.1 | ngnx-stable/nms | 2.11.0 |
| 1.7.0 | ngnx-stable/nms | 2.11.0 |
| 1.6.0 | ngnx-stable/nms | 2.10.1 |
| 1.5.2 | ngnx-stable/nms | 2.10.0 |
| 1.5.1 | ngnx-stable/nms | 2.10.0 |
| 1.5.0 | ngnx-stable/nms | 2.10.0 |
| 1.4.0 | ngnx-stable/nms | 2.9.1 |
| 1.3.1 | ngnx-stable/nms | 2.9.0 |
| 1.3.0 | ngnx-stable/nms | 2.9.0 |
| 1.2.1 | ngnx-stable/nms | 2.8.0 |
| 1.2.0 | ngnx-stable/nms | 2.8.0 |
| 1.1.2 | ngnx-stable/nms | 2.7.0 |
| 1.1.1 | ngnx-stable/nms | 2.7.0 |
| 1.1.0 | ngnx-stable/nms | 2.7.0 |
| 1.0.0 | ngnx-stable/nms | 2.6.0 |

{{</bootstrap-table>}}
4 changes: 0 additions & 4 deletions content/nim/deploy/kubernetes/deploy-using-helm.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,10 +29,6 @@ Make sure to update your chart references if you’re using version 2.20.0 or la

To deploy NGINX Instance Manager using a Helm chart, you need:

## Requirements

To deploy NGINX Instance Manager using a Helm chart, you need:

{{< bootstrap-table "table table-striped table-bordered" >}}
| Requirements | Notes |
|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
Expand Down