docs: Update N1 NGF installation doc - #1618
Merged
Merged
Conversation
github-actions
Bot
added
documentation
Contributor
Author
|
@ADubhlaoich Realized that these docs may have overlap with your installation rework, just an FYI. |
sjberman
changed the title
The N1 doc for NGF integration was missing the step to deploy a Gateway. Without this, nothing can be seen on the console.
sjberman
force-pushed
the
docs/ngf-console
branch
from
December 22, 2025 19:02
cf745b8 to
1f6fa96
Compare
bjee19
reviewed
Dec 22, 2025
bjee19
approved these changes
Dec 22, 2025
ADubhlaoich
approved these changes
Dec 23, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
The N1 doc for NGF integration was missing the step to deploy a Gateway. Without this, nothing can be seen on the console.
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. ↩