generated from nginx/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 103
Epic 472 port nginx one labs #681
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
Changes from 45 commits
Commits
Show all changes
58 commits
Select commit
Hold shift + click to select a range
9698077
Added lab 1
travisamartin 2df7454
added lab2
travisamartin 25f374f
added steps for lab 2
travisamartin 411d3b8
moved lab files out of content dir
travisamartin 1e1af12
added lab 3
travisamartin 56fa0e5
Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs
travisamartin c44decd
edits to lab 3
travisamartin 5bd0015
Merge branch 'port-lab-3' of github.com:nginx/documentation into port…
travisamartin d03aa23
deleted unused file
travisamartin 5f50bea
edits to lab 3
travisamartin a4b29ca
Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs
travisamartin a9ecc38
Merge branch 'epic-472-port-nginx-one-labs' into port-lab-3
travisamartin 67423e7
fixed link
travisamartin 7d42168
deleted 1-day and 30-day certs and keys
travisamartin f6faf61
Ported lab 4
travisamartin d437960
Merge branch 'epic-472-port-nginx-one-labs' into port-n1-lab-4-workshop
travisamartin a04b3e7
edits to note re combining NOSS and N+ in config sync groups
travisamartin 8c8580e
Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs
travisamartin bd9ada1
Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs
travisamartin c3046e1
Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs
travisamartin 7a90fb8
Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs
travisamartin fa6260f
Port lab 5 (#733)
travisamartin fac3953
edits per tech review
travisamartin f46af90
Merge branch 'epic-472-port-nginx-one-labs' of github.com:nginx/docum…
travisamartin b461555
Apply suggestions from code review
travisamartin bfb0fec
reordered N1 workshops in nav
travisamartin 4b312a1
edits
travisamartin 16c7d06
added verification step for enabling N+ API using CSG
travisamartin e7b1ede
added card for workshops to index page
travisamartin 54faf01
Merge branch 'main' into epic-472-port-nginx-one-labs
travisamartin 5d33ebd
fixed workshops card link
travisamartin 8a59ccc
Merge branch 'main' into epic-472-port-nginx-one-labs
lamATnginx 2e00869
Update workshops card link
lamATnginx 82567cf
Merge branch 'main' into epic-472-port-nginx-one-labs
travisamartin e5982d4
Merge branch 'main' into epic-472-port-nginx-one-labs
lamATnginx 9bc04c0
Fix url link in N1 landing + changed to workshop for featured card
lamATnginx a6b54bf
Merge branch 'main' into epic-472-port-nginx-one-labs
travisamartin a939950
Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs
travisamartin a1b62b3
edited N1 card text to include Console
travisamartin c6b5352
removed Apache license
travisamartin 5083348
Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs
travisamartin 61b7954
added workshop card
travisamartin c4daaa7
Merge branch 'main' into epic-472-port-nginx-one-labs
travisamartin 7b5786e
added wrench icon to workshop card
travisamartin bd1fd9d
Merge branch 'epic-472-port-nginx-one-labs' of github.com:nginx/docum…
travisamartin 275abe7
Merge branch 'main' into epic-472-port-nginx-one-labs
travisamartin 00221ae
Merge remote-tracking branch 'origin/main' into epic-472-port-nginx-o…
travisamartin 257b1af
Merge remote-tracking branch 'origin' into epic-472-port-nginx-one-labs
travisamartin 9f7dc44
Merge branch 'main' into epic-472-port-nginx-one-labs
travisamartin e2871ce
tightened up the text in lab 1
travisamartin 7f23814
edits to cloud-access-nginx and cloud-access includes
travisamartin b7cfc43
fixed number in cloud-access-nginx.md include
travisamartin 53cbf0e
edits to lab for reading level and style
travisamartin d7d3be1
added include for XC tenant requirement bullet
travisamartin c4f2295
added files metadata to xc-account.md include
travisamartin f8c0037
added files metadata to enable-nginx-plus-api-with-config-sync-group.…
travisamartin 14c1ebd
tweaked the workshops card text
travisamartin dfdb785
Merge branch 'main' into epic-472-port-nginx-one-labs
travisamartin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -34,4 +34,4 @@ server { | |
root /usr/share/nginx/html; | ||
} | ||
} | ||
``` | ||
``` |
18 changes: 18 additions & 0 deletions
18
...t/includes/use-cases/monitoring/enable-nginx-plus-api-with-config-sync-group.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
--- | ||
docs: | ||
files: | ||
- | ||
- | ||
--- | ||
|
||
1. In the NGINX One Console, select **Manage > Config Sync Groups**, then pick your config sync group's name. | ||
2. Select the **Configuration** tab, then select **Edit Configuration**. | ||
3. Select **Add File**. | ||
4. Select **New Configuration File**. | ||
5. In the **File name** box, enter `/etc/nginx/conf.d/dashboard.conf`, then select **Add**. | ||
6. Paste the following into the new file workspace: | ||
|
||
{{< include "config-snippets/enable-nplus-api-dashboard.md" >}} | ||
|
||
7. Select **Next**, review the diff, then select **Save and Publish**. | ||
8. Open your browser to `http://<instance-ip>:9000/dashboard.html` (replace `<instance-ip>` with the IP or hostname of one of your group members). You should see the NGINX Plus dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
--- | ||
docs: | ||
files: | ||
- content/nginx-one/workshops/lab4/config-sync-groups.md | ||
- content/nginx-one/workshops/lab5/upgrade-nginx-plus-to-r34.md | ||
|
||
--- | ||
|
||
Set these environment variables: | ||
|
||
- **TOKEN**: your data plane key, for example: | ||
|
||
```shell | ||
export TOKEN="your-data-plane-key" | ||
``` | ||
|
||
- **JWT**: your NGINX Plus license JWT. Save it as `nginx-repo.jwt`, then run: | ||
|
||
```shell | ||
export JWT=$(cat path/to/nginx-repo.jwt) | ||
``` | ||
|
||
- **NAME**: a unique ID for your workshop (for example, `s.jobs`): | ||
|
||
```shell | ||
export NAME="s.jobs" | ||
``` |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
--- | ||
title: Workshops | ||
description: | ||
weight: 750 | ||
url: /nginx-one/workshops | ||
--- |
126 changes: 126 additions & 0 deletions
126
content/nginx-one/workshops/lab1/getting-started-with-nginx-one.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,126 @@ | ||
--- | ||
title: "Lab 1: Get started with NGINX One Console" | ||
weight: 100 | ||
toc: true | ||
nd-content-type: tutorial | ||
nd-product: NGINX-ONE | ||
--- | ||
|
||
## Introduction | ||
|
||
This guide helps you log in to NGINX One Console and understand the basics of how it works. You’ll learn how to get started, find your way around the console, and manage your NGINX instances using data plane keys. | ||
|
||
## What you’ll learn | ||
|
||
By the end of this tutorial, you’ll know how to: | ||
|
||
- Open and use NGINX One Console | ||
- Understand what NGINX One Console does and how it works | ||
- Create, copy, and save a data plane key | ||
- Revoke or delete a data plane key (optional) | ||
|
||
## Before you begin | ||
|
||
Make sure you have: | ||
|
||
- An F5 Distributed Cloud (XC) account | ||
- NGINX One service enabled in your account | ||
travisamartin marked this conversation as resolved.
Show resolved
Hide resolved
|
||
- Basic knowledge of Linux and NGINX | ||
|
||
--- | ||
|
||
## Learn what NGINX One Console does | ||
|
||
NGINX One Console is a cloud-based service in the F5 Distributed Cloud platform. It helps you: | ||
|
||
- 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 | ||
travisamartin marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
With NGINX One Console, you don’t need to switch between tools. You get a single dashboard with real-time data and alerts. | ||
|
||
--- | ||
|
||
## How NGINX One Console works | ||
|
||
NGINX One Console connects to each NGINX instance using a lightweight agent called **NGINX Agent**. | ||
|
||
NGINX Agent is responsible for securely registering and managing each instance through the console. | ||
|
||
There are a few ways to install NGINX Agent: | ||
|
||
- 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 | ||
|
||
travisamartin marked this conversation as resolved.
Show resolved
Hide resolved
|
||
When you register a new instance in the console, you'll get a ready-to-use `curl` command that downloads and installs the NGINX Agent on your target system. | ||
|
||
For more information about NGINX Agent, see the [NGINX Agent documentation]({{< ref "/agent/about.md" >}}). | ||
|
||
--- | ||
|
||
## Open and use NGINX One Console | ||
|
||
1. Go to [https://console.ves.volterra.io/login/start](https://console.ves.volterra.io/login/start). | ||
travisamartin marked this conversation as resolved.
Show resolved
Hide resolved
|
||
2. Sign in using your Distributed Cloud account. | ||
3. On the home page, find the **NGINX One** tile. | ||
4. Select the tile to open the console. | ||
5. Make sure the service status shows **Enabled**. | ||
6. Select **Visit Service** to go to the **Overview** dashboard. | ||
|
||
If NGINX One Console isn’t enabled, contact your XC administrator to request access. | ||
|
||
When no NGINX instances are connected, the dashboard will be empty. Once you add instances, it will show metrics like availability, version, and usage trends. | ||
|
||
--- | ||
|
||
## Create and save a data plane key | ||
travisamartin marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
To register NGINX instances, you need a data plane key. | ||
|
||
1. In the console, go to **Manage > Data Plane Keys**. | ||
2. Select **Add Data Plane Key**. | ||
3. Enter a name for the key. | ||
4. Set an expiration date (or keep the default of one year). | ||
5. Select **Generate**. | ||
6. Copy the key when it appears—**you won’t be able to see it again**. | ||
7. Save it somewhere safe. | ||
|
||
You can use the same key to register many instances. If you lose the key, you’ll need to create a new one. | ||
|
||
--- | ||
|
||
## (Optional) Revoke a data plane key | ||
|
||
To disable a key: | ||
|
||
1. On the **Data Plane Keys** page, find the key you want to revoke. | ||
2. Select the key. | ||
3. Choose **Revoke**, then confirm. | ||
|
||
--- | ||
|
||
## (Optional) Delete a revoked key | ||
|
||
You can only delete a key after you revoke it. | ||
|
||
1. On the **Revoked Keys** tab, find the key you want to delete. | ||
2. Select the key. | ||
3. Choose **Delete Selected**, then confirm. | ||
|
||
--- | ||
|
||
## Next steps | ||
|
||
Now that you’ve explored NGINX One Console and created a key, you’re ready to connect your first NGINX instance. | ||
|
||
Go to [Lab 2: Run workshop components with Docker]({{< ref "nginx-one/workshops/lab2/run-workshop-components-with-docker.md" >}}) | ||
|
||
--- | ||
|
||
## References | ||
|
||
- [Create and manage data plane keys]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}) | ||
- [NGINX Agent overview]({{< ref "/agent/about.md" >}}) |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.