IBM Application Navigator is a tool that extends the Kubernetes® console to provide display, inspection, understanding and expose day 2 operations of applications comprised of Kubernetes resources and existing middleware, such as WebSphere Application Server. AppNav extends the open source Kubernetes Application Navigator (kAppNav) by providing integration to WebSphere ND Cells and Liberty Collectives, enabling visibility to existing and containerized applications.
This repository is the primary source of documentation IBM Application Navigator. The actual documentation starts here: https://ibm.github.io/appnav/. IBM Application Navigator is installed as part of IBM Cloud Pak for Applications. The installation documentation is available in the Knowledge Center.
If you find any issues with the documentation, please open an issue. Functional issues should be reported using IBM's support ticket process.
Because IBM Application Navigator (AppNav) extends Kubernetes Application Navigator (kAppNav), a sound documentation strategy is required to ensure minimal duplication and to reuse existing documentation and to promote the kAppNav project. Before contributing documentation for AppNav, consider whether the documentation is better provided in kAppNav.
- Reduce duplication and promote re-use of existing documentation
- Promote and cross-link to the kAppNav project
- Honor the inheritance from the open source
- Each ‘tier’ of documentation is sufficient for the audience but can rely on a ‘lower tier’ for elaboration of details
- Convert kAppNav users to AppNav users
- IBM Application Navigator
- Installation documentation: Knowledge Center
- Usage documentation: https://ibm.github.io/appnav/
- Kabanero
- Kubernetes Application Navigator
- See kappnav.io and https://github.com/kappnav/README
The goal of the UI is to be as intuitive as possible. Similarly, the goal of the documentation is to be as instructive as possible, without being overly burdensome. The documentation should assume minimal knowledge on the part of the user, while still being quick to follow for experienced users (i.e. next steps are obvious, clearly indicated, and an experienced user can skip ahead quickly). To that end, augment the documentation with screenshots, command examples and code (YAML) examples.
- Screenshots should include as much of the UI as is necessary for context. Unless important, the browser URL bar does not need to be included.
- Annotated screenshots should use the "Bradley Hand" font (available by default on MacOS) and dark blue shape outlines.
- Small, focused screenshots are encouraged when filling in forms