As a maintainer of NGINX Ingress Controller, I would like to provide our product as an add-on install option for Azure AKS clusters so that users can configure and install NGINX Ingress Controller when their cluster is being created.
High-level Functional Requirements
Provide an Azure AKS add-on option for NGINX Ingress Controller
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.
Overview
As a maintainer of NGINX Ingress Controller, I would like to provide our product as an add-on install option for Azure AKS clusters so that users can configure and install NGINX Ingress Controller when their cluster is being created.
High-level Functional Requirements
Definition of Done
Development
make lint
locally before creating a PR.Testing
Release Notes & Documentation