NGINX Ingress Controller observability in NGINX One & NGINX Instance Manager

[shaun-nx]

Overview

As a user of NGINX Ingress Controller, I would like my deployments to be visible and manageable in both NGINX One and NGINX Instance Manager so that I can more easily manage my deployments.

References

NGINX One Cloud Environments for testing

High-level Functional Requirements

• Allow NGINX Ingress Controller to send metrics to NGINX Instance Manager
• Allow NGINX Ingress Controller deployments to be visible in NGINX Instance Manager
• Allow NGINX Ingress Controller to send metrics to NGINX One SaaS Console
• Allow NGINX Ingress Controller deployments to be visible in NGINX One SaaS Console

Definition of Done

Development

• Unit tests are written to cover functionality delivered in the story.
• Make sure that the unit test passes before creating a pull request.
• Make sure that the test coverage stays optimal.
• Run make lint locally before creating a PR.

Testing

• Automated tests are written as part of the story.
• Run “make lint-python“ from root
• Acceptance criteria are met.
• Stories are demonstrated to the team.
• Product Manager accepts the story as done.
• If a feature requires changes/extensions of the Helm chart, those shall be done as part of the story.

Release Notes & Documentation

• PR is labeled appropriately so they display in GitHub release notes.
• Create/update documentation related to the user story.
• Create/update the example in our codebase when applicable.

[github-actions]

Hi @shaun-nx thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!