Skip to content

Commit e1b5511

Browse files
committed
Lab 5 updates for R34
1 parent 262cb55 commit e1b5511

File tree

3 files changed

+3
-4
lines changed

3 files changed

+3
-4
lines changed

labs/lab5/docker-compose.yml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
# NGINX Plus / OSS with NGINX Agent
22
# NGINX webservers with ingress-demo pages
33
# NGINX One Console Instance Registration
4-
# NGINX Basics, Dec 2024
54
# Chris Akker, Shouvik Dutta, Adam Currier
65
#
76
services:

labs/lab5/readme.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Upgrading NGINX Plus Instances to R33
1+
# Upgrading NGINX Plus Instances to R34
22

33
## Introduction
44

@@ -226,7 +226,7 @@ First, you will create a new Config Sync Group to add machines that you want to
226226
227227
```bash
228228
hostnamectl hostname $NAME-nplus-vm
229-
229+
230230
```
231231
232232
```bash
@@ -452,7 +452,7 @@ Let's take the R32 install and upgrade it. This time you will do it with assista
452452
453453
1. NGINX Agent detected the NGINX upgrade and automatically send this information to NGINX One Console. You can also confirm this with NGINX One Console that the NGINX Plus version was upgraded for the VM. Click on the `Instances` menu on the left-hand side and you will see the instance was upgraded:
454454
455-
![NGINX Plus](media/lab5-upgrade-confirmed.png)
455+
![NGINX Plus](media/lab5-upgrade-confirmed-r34.png)
456456
457457
You can update a single instance following this procedure for adding a license.jwt to the server. However, using a Config Sync Group, you can prepare 100's or 1000's of instances in your NGINX fleet and have them ready for the upgrade.
458458

0 commit comments

Comments
 (0)