Docs for connecting NIC to NGINX One Console

[AlexFenlon]

Proposed changes

Docs for connecting NGINX Ingress Controller to NGINX One Console

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

[github-actions]

✅ Deploy Preview will be available once build job completes!

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

---

[mjang]

cc @jasonclopper

I didn't realize this was already on the roadmap.

[mjang]

I've been told that we're not yet ready for this. We're currently working on integration with NAP.

[mjang]

Is there a Jira/GitHub issue that you've been working from?

[jputrino]

Please hold off on this. @shaun-nx & @jasonclopper -- We need to sync up on the approach to documenting this use case. NIC does not exist in a vacuum, nor should the docs for an integrated use case such as this.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 52.28%. Comparing base (38094d2) to head (ce07302).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7815      +/-   ##
==========================================
- Coverage   52.30%   52.28%   -0.02%     
==========================================
  Files          90       90              
  Lines       21472    21472              
==========================================
- Hits        11231    11227       -4     
- Misses       9772     9774       +2     
- Partials      469      471       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ADubhlaoich]

Generally LGTM: please take a look at my earlier edit suggestion for the frontmatter data.

Adjusting indentation of codeblocks in GitHub suggestions seems to also be parsed very oddly.

[travisamartin]

The draft focuses on deployment from the NIC side, but not on the value of integration with NGINX One.
NGINX One should be the hero of the story — not the sidekick.

Recommendations:

• Reframe from the perspective of NGINX One; open with the benefits of this integration: central monitoring, visibility, operational efficiency.
• Make this doc discoverable through both the N1 and NIC content sets, but maintain one canonical version in N1.

[ADubhlaoich]

@travisamartin I'll bring this up during the internal meeting this week about it: I recommend we merge this doc as-is (With the important caveat that it retains the draft parameter), and update this for tone/consistency with N1C as part of content planning for full feature implementation.

NIC documentation is due to be migrated into the main documentation repository, which this PR is blocking, and once it has been migrated, it'll be very easy to transform this document however necessary.

[travisamartin]

@ADubhlaoich -- Please work w/ @mjang on placement for the N1 integration docs. We want to minimize hops between docs, and prioritize N1 as a point of entry in the user journey.

Additionally, the doc should end with a "What's next" section to guide the user toward additional "value adds." "Now that you're integrated, check out these useful things you can do!"