generated from nginx/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 121
Open
Open
[Story]: Add documentation for how a customer can switch their instance to the new target namespace.#1339
Enhancement
Copy link
Labels
P4 - Low (TTR: 90 days)Minor cleanup or content updates (stylistic, cosmetic, or low-impact gaps). Fix when convenient.Minor cleanup or content updates (stylistic, cosmetic, or low-impact gaps). Fix when convenient.enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomersproduct/nginx-oneIssues related to NGINX One ConsoleIssues related to NGINX One Console
Description
Overview
Clearly document steps for the customer on steps to take when switching their instance to the new target namespace.
Which product or products does this request relate to?
NGINX One Console
Description
The switch to the new target namespace requires customer to complete the following steps to deregister their existing instance and register it as per the target namespace:
- Switch to target namespace
- Create a new data-plane key
- Update configuration of the already installed agent, to point to the new data-plane key.
- Restart agent
- Verify the instance shows up in the target namespace
This task is to document this process for the customer.
Acceptance criteria
- Documentation added to showcase to the customer how to achieve the instance switch to a new target namespace.
- The link to the documentation is added to the
content/nginx-one/glossary.mdpage.
Metadata
Metadata
Assignees
Labels
P4 - Low (TTR: 90 days)Minor cleanup or content updates (stylistic, cosmetic, or low-impact gaps). Fix when convenient.Minor cleanup or content updates (stylistic, cosmetic, or low-impact gaps). Fix when convenient.enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomersproduct/nginx-oneIssues related to NGINX One ConsoleIssues related to NGINX One Console