Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add more information to agent v3 upgrade page.#1566

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
nginx-seanmoloney wants to merge3 commits intomain
base:main
Choose a base branch
Loading
fromadd-info-to-agent-upgrade

Conversation

@nginx-seanmoloney
Copy link
Contributor

Proposed changes

Checklist

Before sharing this pull request, I completed the following checklist:

Footnotes

  1. Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to thestyle guide for guidance about placeholder content.

@github-actionsgithub-actionsbot added documentationImprovements or additions to documentation product/agentIssues related to NGINX Agent labelsDec 11, 2025
@github-actions
Copy link

Deploy Preview will be available once build job completes!

NameLink
😎 Deploy Previewhttps://frontdoor-test-docs.nginx.com/previews/docs/1566/

When upgrading to NGINX Agent v3, the installer automatically backs up all configuration files before proceeding. It also converts your v2 configuration to the v3 format, ensuring compatibility and preserving settings.

{{< call-out "note" >}}
If you are using a version**older than NGINX Agent v2.31.0**, you must stop NGINX Agent before updating:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

You may want to include the syntax to get the version. I know you have it in a later step, but having it earlier would help the user settle any doubts about the version they have installed.

nginx-seanmoloney reacted with thumbs up emoji

1. Open an SSH connection to the server where you've installed NGINX Agent.

1. Make a backup copy of the following locations to ensure that you can successfully recover if the upgrade does not complete
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

The document earlier explains that the upgrade process makes a backup of your config files for you. Yet, step one has the use make backup files themselves. Why both?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

The installer will only back up the nginx-agent.conf file not the /nginx-agent directory.

- [Full list of v3 environment variables]({{< ref"/nginx-one-console/agent/configure-instances/configuration-overview/">}})


Taking an example docker-compose file running a NGINX Agent v2 and update to v3.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

It might be better to show the v2 ENV vars right beside the updated v3 names for them in a table, rather than showing multiple examples files.

fabriziofiorucci reacted with thumbs up emoji
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

It might be a good idea to show an example on what each variable value should look like/its format etc

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Good point. Including whether or not to use quotes.

Co-authored-by: Daniel Edgar <d.edgar@f5.com>
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@aknot242aknot242aknot242 requested changes

+1 more reviewer

@fabriziofioruccifabriziofioruccifabriziofiorucci left review comments

Reviewers whose approvals may not affect merge requirements

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

documentationImprovements or additions to documentationproduct/agentIssues related to NGINX Agent

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@nginx-seanmoloney@aknot242@fabriziofiorucci

[8]ページ先頭

©2009-2025 Movatter.jp