-
Notifications
You must be signed in to change notification settings - Fork 101
NGINX Agent: Add v3.0 upgrade guide #318
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
Conversation
* chore: Update call-out shortcode usage in Contributing * Update with suggestion Co-authored-by: Mike Jang <3287976+mjang@users.noreply.github.com> --------- Co-authored-by: Mike Jang <3287976+mjang@users.noreply.github.com>
✅ All required contributors have signed the F5 CLA for this PR. Thank you! |
I have hereby read the F5 CLA and agree to its terms |
✅ Deploy Preview will be available once build job completes!
|
./upgrade-agent-config.sh --v2-config-file=./nginx-agent-v2.conf --v3-config-file=nginx-agent-v3.conf | ||
``` | ||
|
||
If your NGINX Agent container was apart of a config sync group, then your NGINX Agent config needs to be manually updated to add the config sync group label. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If your NGINX Agent container was apart of a config sync group, then your NGINX Agent config needs to be manually updated to add the config sync group label. | |
If your NGINX Agent container was not a member of a config sync group, then your NGINX Agent config must be manually updated to add the config sync group label. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dhurley can you confirm that apart
in here means it was outside of config sync groups and not a typo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this is a better way to say it.
If your NGINX Agent container was previously a member of a config sync group, then your NGINX Agent config must be manually updated to add the config sync group label.
@dhurley @nginx-seanmoloney , finished my 1st review pass. I think it will still need more refining |
Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com>
Proposed changes
Add a page describing how to upgrade from NGINX Agent v2 to v3 and also document the rollback procedure.
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.md
andCHANGELOG.md
Footnotes
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. ↩