Moonin Documentation
Moonin Documentation
Operate Kubernetes with context, not guesswork.
Learn how Moonin connects cluster inventory, deployments, revisions, incidents and notifications into one operational workspace.
What Moonin connects
Section titled “What Moonin connects”Moonin is a Kubernetes operations platform centered on five connected jobs:
- model the runtime hierarchy of your estate
- track every rollout as a revision
- capture runtime failures with rollout context
- route notifications through reusable policies
- keep organizational access, clusters and channels governed from one place
This documentation is written so an operator can move from onboarding to day-2 operations without depending on hidden product knowledge.
Language entry points
Section titled “Language entry points”| Language | Start here |
|---|---|
| English | Getting Started |
| Español | Documentacion en espanol |
Resource hierarchy
Section titled “Resource hierarchy”The main mental model in Moonin is hierarchical. Most screens, filters and permissions follow this chain:
What each level means
Section titled “What each level means”Organizationis the tenant boundary for users, groups, billing, notification channels, policies and SSO settings.Projectgroups clusters that belong to the same business domain, team or environment.Clusteris the registered Kubernetes target connected through the Moonin agent.Namespacescopes workloads inside a cluster.Deploymentis the rollout unit tracked by Moonin for revision and incident correlation.Serviceis the traffic-facing view of a workload and is used to explore logs, events, metrics and dependencies.Revisionis the immutable snapshot created for a rollout.CronJobis the scheduled execution unit tracked separately from deployment revisions.
Core product flows
Section titled “Core product flows”1. Onboard and discover
Section titled “1. Onboard and discover”2. Follow a rollout
Section titled “2. Follow a rollout”3. Investigate an incident
Section titled “3. Investigate an incident”4. Notify the right channel
Section titled “4. Notify the right channel”Access model at a glance
Section titled “Access model at a glance”Moonin combines baseline membership with fine-grained roles:
organization.ownerhas full control of the organization.- Membership roles are
viewer,editorandadmin. vieweris the minimum role and follows least-privilege by default.- By default,
viewercan list organizations and depends on administrator-granted permissions for additional access. - Direct user roles can grant feature-specific permissions.
- Group roles let teams inherit the same permissions without editing users one by one.
- Some screens also enforce feature permissions such as revision viewing, error RCA, policy editing or cluster administration.
The full operating model is described in Administration and Azure AD.
Documentation map
Section titled “Documentation map”| Need | Page |
|---|---|
| Understand releases, revisions and rollout context | Revision History |
| Work with deployments and image inventory | Deployments & Images |
| Operate clusters and inspect node inventory | Clusters & Nodes |
| Understand services, CronJobs and execution history | Workloads, Services & CronJobs |
| Investigate active and historical failures | Incidents & Errors |
| Configure channels and understand delivery logic | Notifications |
| Configure alerting, event routing and scaling automation | Policies & Governance |
| Manage organizations, projects, users, groups and clusters | Administration |
| Set up Microsoft Entra ID per organization | Azure AD |