Skip to content

Commit 82567cf

Browse files
Merge branch 'main' into epic-472-port-nginx-one-labs
2 parents 2e00869 + c6a4ac4 commit 82567cf

File tree

4 files changed

+3
-26
lines changed

4 files changed

+3
-26
lines changed

_banners/agent-v3-release.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{{< banner "notice" "NGINX Agent 3.0 is now available" >}}
22

33

4-
F5 NGINX One Console does not currently support Agent 3.x. If you are using NGINX One Console in your environment, upgrade to the latest Agent 2.x version by following the [Upgrade NGINX Agent](/nginx-agent/installation-upgrade/upgrade/) guide.
4+
F5 NGINX One Console and NGINX Instance Manager (NIM) do not currently support Agent 3.x. If you are using NGINX One Console or NGINX Instance Manager in your environment, upgrade to the latest Agent 2.x version by following the [Upgrade NGINX Agent](/nginx-agent/installation-upgrade/upgrade/) guide.
55

66
Please see the [Technical specifications](/nginx-agent/technical-specifications/) for product compatibility.
77

content/includes/nim/kubernetes/access-webui-helm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,10 @@ You can access the NGINX Instance Manager web interface using the external IP ad
77
1. To look up the external IP address for the API Gateway, run the following command:
88

99
```bash
10-
kubectl -n nms get svc apigw
10+
kubectl -n nim get svc apigw
1111
```
1212

13-
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.
13+
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.
1414

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

content/includes/nim/kubernetes/nms-chart-supported-module-versions.md

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -20,24 +20,5 @@ docs: DOCS-1324
2020
| 1.10.1 | ngnx-stable/nms | 2.13.1 |
2121
| 1.10.0 | ngnx-stable/nms | 2.13.1 |
2222
| 1.9.0 | ngnx-stable/nms | 2.13.0 |
23-
| 1.8.2 | ngnx-stable/nms | 2.12.0 |
24-
| 1.8.1 | ngnx-stable/nms | 2.12.0 |
25-
| 1.8.0 | ngnx-stable/nms | 2.12.0 |
26-
| 1.7.2 | ngnx-stable/nms | 2.11.0 |
27-
| 1.7.1 | ngnx-stable/nms | 2.11.0 |
28-
| 1.7.0 | ngnx-stable/nms | 2.11.0 |
29-
| 1.6.0 | ngnx-stable/nms | 2.10.1 |
30-
| 1.5.2 | ngnx-stable/nms | 2.10.0 |
31-
| 1.5.1 | ngnx-stable/nms | 2.10.0 |
32-
| 1.5.0 | ngnx-stable/nms | 2.10.0 |
33-
| 1.4.0 | ngnx-stable/nms | 2.9.1 |
34-
| 1.3.1 | ngnx-stable/nms | 2.9.0 |
35-
| 1.3.0 | ngnx-stable/nms | 2.9.0 |
36-
| 1.2.1 | ngnx-stable/nms | 2.8.0 |
37-
| 1.2.0 | ngnx-stable/nms | 2.8.0 |
38-
| 1.1.2 | ngnx-stable/nms | 2.7.0 |
39-
| 1.1.1 | ngnx-stable/nms | 2.7.0 |
40-
| 1.1.0 | ngnx-stable/nms | 2.7.0 |
41-
| 1.0.0 | ngnx-stable/nms | 2.6.0 |
4223

4324
{{</bootstrap-table>}}

content/nim/deploy/kubernetes/deploy-using-helm.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,10 +29,6 @@ Make sure to update your chart references if you’re using version 2.20.0 or la
2929

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

32-
## Requirements
33-
34-
To deploy NGINX Instance Manager using a Helm chart, you need:
35-
3632
{{< bootstrap-table "table table-striped table-bordered" >}}
3733
| Requirements | Notes |
3834
|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

0 commit comments

Comments
 (0)