Update glossary.md for namespace switching #1174
Open
Conversation
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
github-actions
bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
y82
approved these changes
Sep 26, 2025
JTorreG
approved these changes
Oct 14, 2025
|
Shared with Kamal C for SME review. |
|
Do we document anywhere how can customer perform this deregistering ? Might be confusing for the customer to figure it out unless we explicitly state it. |
vrmare
reviewed
Oct 16, 2025
| | **Namespace** | In F5 Distributed Cloud, a namespace groups a tenant’s configuration objects, similar to administrative domains. Every object in a namespace must have a unique name, and each namespace must be unique to its tenant. This setup ensures isolation, preventing cross-referencing of objects between namespaces. You'll see the namespace in the NGINX One Console URL as `/namespaces/<namespace name>/` | | ||
| | **Namespace** | In F5 Distributed Cloud, a namespace groups a tenant’s configuration objects, similar to administrative domains. Every object in a namespace must have a unique name, and each namespace must be unique to its tenant. This setup ensures isolation, preventing cross-referencing of objects between namespaces. You'll see the namespace in the NGINX One Console URL as `/namespaces/<namespace name>/`. | ||
|
|
||
| To switch an instance between namespaces, you have to deregister an instance from an old namespace, and register it on the new namespace. | |
There was a problem hiding this comment.
Don't think we have these instructions anywhere? Probably worth writing as part of this MR.
There was a problem hiding this comment.
I'd welcome it. I recommend doing so in a 2nd PR. I suggest one of these options:
- Include it as a 2nd procedure in https://docs.nginx.com/nginx-one/nginx-configs/one-instance/view-edit-nginx-configurations/
- Set up a new procedure under https://docs.nginx.com/nginx-one/nginx-configs/one-instance/
If we do this in a 2nd PR, we can merge this, and continue our work there
There was a problem hiding this comment.
Ok. I don't want to hold this but could file a ticket. Would need to get prioritized at some point as I consider this doc tech debt
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Proposed changes
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩