Epic 472 port nginx one labs #681

travisamartin · 2025-06-16T15:17:27Z

Proposed changes

Write a clear and concise description that helps reviewers understand the purpose and impact of your changes. Use the
following format:

Problem: Give a brief overview of the problem or feature being addressed.

Solution: Explain the approach you took to implement the solution, highlighting any significant design decisions or
considerations.

Testing: Describe any testing that you did.

Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.

If this PR addresses an issue on GitHub, ensure that you link to it here:

Closes #ISSUE

Checklist

Before merging a pull request, run through this checklist and mark each as complete.

Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩

…-lab-3

github-actions · 2025-06-17T20:02:32Z

✅ Deploy Preview will be available once build job completes!

Name	Link
😎 Deploy Preview	https://frontdoor-test-docs.nginx.com/previews/docs/681/

content/nginx-one/workshops/lab2/run-workshop-components-with-docker.md

content/nginx-one/workshops/lab3/explore-nginx-one-console-and-features.md

content/nginx-one/workshops/lab4/config-sync-groups.md

static/workshops/nginx-one/lab2/nginx-oss/etc/nginx/conf.d/stub_status.conf

static/workshops/nginx-one/lab2/nginx-oss/etc/nginx/conf.d/tls-cars.example.com.conf

content/nginx-one/workshops/LICENSE

* Ported lab 5

…entation into epic-472-port-nginx-one-labs

edits from tech review Co-authored-by: yar <[email protected]>

…entation into epic-472-port-nginx-one-labs

travisamartin · 2025-07-08T22:32:28Z

content/includes/use-cases/monitoring/enable-nginx-plus-api-with-config-sync-group.md

@@ -0,0 +1,18 @@
+---
+docs:
+files:


Note to self: add file references here.

mjang

Review in progress

mjang · 2025-07-09T14:09:38Z

content/nginx-one/_index.md

+{{<card-layout>}}
+  {{<card-section showAsCards="true">}}
+    {{<card title="NGINX One Console workshops" titleUrl="/nginx-one/workshops/" icon="wrench" >}}
+      Learn how to register and manage NGINX instances in NGINX One Console. View CVE and configuration recommendations. Use Config Sync Groups to deploy JWT licenses and upgrade to the latest NGINX Plus.


Is there a way to set this up with bullets?

Alternatively, I'm tempted to set up different cards for the "unique" use cases

We already cover your first sentence in "Manage your NGINX instances"

Use case: "Review CVEs and our recommended config changes"

Use case: "Manage groups of instances (Config Sync Groups) to update licenses and upgrade systems with one command"

mjang · 2025-07-09T14:54:20Z

content/nginx-one/workshops/lab1/getting-started-with-nginx-one.md

+- An F5 Distributed Cloud (XC) account
+- NGINX One service enabled in your account


You might be able to use these includes:

nginx-one/cloud-access.md
nginx-one/cloud-access-nginx.md

If enabling NGINX One is a separate step, I might need to update cloud-access-nginx.md

mjang · 2025-07-09T14:56:14Z

content/nginx-one/workshops/lab1/getting-started-with-nginx-one.md

+- Manage all your NGINX instances from one place
+- Monitor performance and health metrics
+- Catch security risks like expired SSL certificates and known vulnerabilities
+- Keep track of software versions and get performance tips


I'd be tempted to add links, but that's a "stretch" goal IMO

mjang · 2025-07-09T14:57:08Z

content/nginx-one/workshops/lab1/getting-started-with-nginx-one.md

+- Use public Docker images of NGINX Open source that already include NGINX Agent
+- Use NGINX Plus containers with NGINX Agent preinstalled
+- Install manually using package managers like `apt` or `yum`
+- Use the one-line curl command that NGINX One provides during registration
+


I think I'd like some links to examples

mjang · 2025-07-09T14:58:49Z

content/nginx-one/workshops/lab1/getting-started-with-nginx-one.md

+
+## Open and use NGINX One Console
+
+1. Go to [https://console.ves.volterra.io/login/start](https://console.ves.volterra.io/login/start).


When I go to this URL, I get the following screen. We're referring to domain as a tenant

In cloud-access.md, I'm using:

"Navigate to https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io/ to access F5 Distributed Cloud."

Related -- we're about ready to release #731 (Once XC makes their June release, maybe on July 14)

mjang

This PR may be step 1. I see no showstoppers in this PR. I've made a number of suggestions. If you agree with them and want to move to the next task, I'm good if you want to "save them for later".

mjang · 2025-07-09T15:32:51Z

content/nginx-one/workshops/lab1/getting-started-with-nginx-one.md

+
+## Open and use NGINX One Console
+
+1. Go to [https://console.ves.volterra.io/login/start](https://console.ves.volterra.io/login/start).


Related -- we're about ready to release #731 (Once XC makes their June release, maybe on July 14)

mjang · 2025-07-09T15:33:56Z

content/nginx-one/workshops/lab1/getting-started-with-nginx-one.md

+
+---
+
+## Create and save a data plane key


Future issue: we may be able to set up more common content

mjang · 2025-07-09T17:07:35Z

content/nginx-one/workshops/lab3/explore-nginx-one-console-and-features.md

+
+By the end of this tutorial, you’ll know how to:
+
+- Navigate the Overview Dashboard panels  


Comment only. Today I realize,

. it is Overview Dashboard

mjang · 2025-07-09T17:10:39Z

content/nginx-one/workshops/lab3/explore-nginx-one-console-and-features.md

+
+## Next steps
+
+Go to [Lab 4: Config Sync Groups]({{< ref "nginx-one/workshops/lab4/config-sync-groups.md" >}})


I like what was done with the previous labs, which intro'd the next lab as <some use case>. Maybe we can do something similar here? Brainstorm idea only:

"Now you're ready to learn how you can modify groups of NGINX instances with one click."

mjang · 2025-07-09T17:16:26Z

content/nginx-one/workshops/lab4/config-sync-groups.md

+
+## Overview
+
+In this lab, you create and manage Config Sync Groups in NGINX One Console. Config Sync Groups keep your NGINX instances in sync with a shared configuration. You learn to create a group, add instances, apply a shared config, and fix sync errors.


(maybe for the future)... I tried something, and it feels wordy:

With a Config Sync Group, you can manage multiple NGINX instances as if they were a single system. For example, you may want to set up a group of NGINX instances in different geographic zones with the same configuration files. When uo set up a Config Sync Group, when you update one file, you're updating the files of every instance in that group.

mjang

I've made a number of suggestions. I've spot checked some of the steps, and they work fine

My suggestions are not mandatory, though this comment bothers me. Maybe the best approach is to change the UI

travisamartin and others added 9 commits May 29, 2025 19:57

Added lab 1

9698077

added lab2

2df7454

added steps for lab 2

25f374f

moved lab files out of content dir

411d3b8

added lab 3

1e1af12

Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs

56fa0e5

edits to lab 3

c44decd

Merge branch 'port-lab-3' of github.com:nginx/documentation into port…

5bd0015

…-lab-3

deleted unused file

d03aa23

github-actions bot added documentation Improvements or additions to documentation product/nginx-one NGINX One Console labels Jun 16, 2025

travisamartin added 4 commits June 17, 2025 10:44

edits to lab 3

5f50bea

Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs

a4b29ca

Merge branch 'epic-472-port-nginx-one-labs' into port-lab-3

a9ecc38

fixed link

67423e7

deleted 1-day and 30-day certs and keys

7d42168

travisamartin self-assigned this Jun 18, 2025

travisamartin and others added 4 commits June 20, 2025 15:05

Ported lab 4

f6faf61

Merge branch 'epic-472-port-nginx-one-labs' into port-n1-lab-4-workshop

d437960

edits to note re combining NOSS and N+ in config sync groups

a04b3e7

Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs

8c8580e

y82 approved these changes Jun 24, 2025

View reviewed changes

travisamartin and others added 7 commits June 24, 2025 08:29

Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs

bd9ada1

Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs

c3046e1

Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs

7a90fb8

Port lab 5 (#733)

fa6260f

* Ported lab 5

edits per tech review

fac3953

Merge branch 'epic-472-port-nginx-one-labs' of github.com:nginx/docum…

f46af90

…entation into epic-472-port-nginx-one-labs

Apply suggestions from code review

b461555

edits from tech review Co-authored-by: yar <[email protected]>

added card for workshops to index page

e7b1ede

travisamartin added customer-success onboarding labels Jun 25, 2025

This was linked to issues Jun 25, 2025

Port and Publish NGINX One Workshop Labs to Public Documentation #472

Open

Create guide: Use NGINX One Config Sync Groups to apply license.jwt across instances (R33 prep) #491

Open

travisamartin and others added 7 commits June 25, 2025 16:06

Merge branch 'main' into epic-472-port-nginx-one-labs

54faf01

fixed workshops card link

5d33ebd

Merge branch 'main' into epic-472-port-nginx-one-labs

8a59ccc

Update workshops card link

2e00869

Merge branch 'main' into epic-472-port-nginx-one-labs

82567cf

Merge branch 'main' into epic-472-port-nginx-one-labs

e5982d4

Fix url link in N1 landing + changed to workshop for featured card

9bc04c0

lamATnginx force-pushed the epic-472-port-nginx-one-labs branch from 675aa73 to 9bc04c0 Compare July 1, 2025 16:20

travisamartin and others added 7 commits July 1, 2025 11:09

Merge branch 'main' into epic-472-port-nginx-one-labs

a6b54bf

Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs

a939950

edited N1 card text to include Console

a1b62b3

removed Apache license

c6b5352

Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs

5083348

added workshop card

61b7954

Merge branch 'main' into epic-472-port-nginx-one-labs

c4daaa7

travisamartin marked this pull request as ready for review July 8, 2025 20:58

travisamartin requested review from a team as code owners July 8, 2025 20:58

travisamartin added 2 commits July 8, 2025 14:08

added wrench icon to workshop card

7b5786e

Merge branch 'epic-472-port-nginx-one-labs' of github.com:nginx/docum…

bd1fd9d

…entation into epic-472-port-nginx-one-labs

travisamartin commented Jul 8, 2025

View reviewed changes

Merge branch 'main' into epic-472-port-nginx-one-labs

275abe7

mjang reviewed Jul 9, 2025

View reviewed changes

mjang approved these changes Jul 9, 2025

View reviewed changes

@@ @@ -0,0 +1,18 @@ @@
+              ---
+              docs:
+              files:

		- An F5 Distributed Cloud (XC) account
		- NGINX One service enabled in your account


		## Open and use NGINX One Console

		1. Go to [https://console.ves.volterra.io/login/start](https://console.ves.volterra.io/login/start).


		By the end of this tutorial, you’ll know how to:

		- Navigate the Overview Dashboard panels


		## Next steps

		Go to [Lab 4: Config Sync Groups]({{< ref "nginx-one/workshops/lab4/config-sync-groups.md" >}})


		## Overview

		In this lab, you create and manage Config Sync Groups in NGINX One Console. Config Sync Groups keep your NGINX instances in sync with a shared configuration. You learn to create a group, add instances, apply a shared config, and fix sync errors.

Epic 472 port nginx one labs #681

Are you sure you want to change the base?

Epic 472 port nginx one labs #681

Uh oh!

Conversation

travisamartin commented Jun 16, 2025

Proposed changes

Checklist

Footnotes

Uh oh!

github-actions bot commented Jun 17, 2025

✅ Deploy Preview will be available once build job completes!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mjang left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mjang left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mjang left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!