Skip to content

Add v2 to v3 migration guide#1843

Draft
nginx-seanmoloney wants to merge 1 commit intomainfrom
agent/upgrade-v2-v3-doc
Draft

Add v2 to v3 migration guide#1843
nginx-seanmoloney wants to merge 1 commit intomainfrom
agent/upgrade-v2-v3-doc

Conversation

@nginx-seanmoloney
Copy link
Copy Markdown
Contributor

Proposed changes

  • Add v2 to v3 migration guide

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 the style guide for guidance about placeholder content.

@nginx-seanmoloney nginx-seanmoloney requested a review from a team as a code owner April 9, 2026 14:00
@nginx-seanmoloney nginx-seanmoloney marked this pull request as draft April 9, 2026 14:00
@github-actions github-actions bot added documentation Improvements or additions to documentation product/nginx-one-console Issues related to NGINX One Console labels Apr 9, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 9, 2026

Deploy Preview will be available once build job completes!

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

@fabriziofiorucci
Copy link
Copy Markdown
Contributor

Migrate NGINX Agent running in containers - I presume this refers to the case where I have a pod running NGINX and the Agent, and the Agent's config file is mounted through a ConfigMap. Am I correct here? In case I am, it might be worth mentioning this in the MD file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation product/nginx-one-console Issues related to NGINX One Console

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants