Cloudjur

Default-Namespace-Utilities

3 min read

Default Namespace Utilities

Relevant source files

The default namespace serves as the primary landing zone for general-purpose utility applications, workflow automation, and productivity tools. These services are characterized by their integration with the central dashboard and their reliance on shared cluster infrastructure such as the envoy-internal gateway and dragonfly cache.

Dashboard and Information Aggregation

The cluster utilizes Homepage as the central entry point for all services. It is configured to dynamically discover services via Kubernetes annotations.

Homepage Dashboard

Homepage is deployed using the app-templatekubernetes/apps/default/homepage/app/helmrelease.yaml5-10 It integrates with the cluster’s RBAC to allow the homepage ServiceAccount to query Kubernetes resources kubernetes/apps/default/homepage/app/helmrelease.yaml37-38

Glance

Glance provides a secondary dashboard/landing page, configured via glance.yml. It typically serves as a lightweight alternative or specialized view for specific metrics and links.

Sources:

Workflow and Automation

n8n Workflow Automation

n8n is the primary engine for low-code automation within the cluster.

Change Detection

changedetection.io monitors web pages for changes.

Sources:

Data Flow: Automation and Persistence

The following diagram illustrates the interaction between automation tools and the underlying storage and network layers.

Automation System Architecture

[Flowchart Diagram]

Sources:

Productivity and Utilities

The namespace hosts a variety of stateless and stateful utility tools:

AppPurposeImplementation Detail
AtuinShell History SyncUses SQLite backend at /config/atuin.dbkubernetes/apps/default/atuin/app/helmrelease.yaml30
CyberChefData ManipulationStateless; uses emptyDir for Nginx cache and run directories kubernetes/apps/default/cyberchef/app/helmrelease.yaml65-77
IT-ToolsDeveloper UtilitiesCollection of web-based tools for developers.
SurePersonal FinanceRails-based app using dragonfly for Redis kubernetes/apps/default/sure/app/helmrelease.yaml49 and postgres-init for DB setup kubernetes/apps/default/sure/app/helmrelease.yaml98-102
KaraKeepWeb ArchivingMulti-controller setup: karakeep (app), chrome (headless), and meilisearch (search engine) kubernetes/apps/default/karakeep/app/helmrelease.yaml22-114
RustDeskRemote DesktopSelf-hosted relay (hbbr) and ID server (hbbs) kubernetes/apps/default/rustdesk/app/helmrelease.yaml15-35

RustDesk Infrastructure

RustDesk is split into two controllers:

  1. hbbs (ID Server): Handles ID registration and keep-alive. It uses a SQLite database at /db/db_v2.sqlite3kubernetes/apps/default/rustdesk/app/helmrelease.yaml32
  2. hbbr (Relay Server): Facilitates connections when direct P2P fails.
    Both services are exposed via LoadBalancer services with static IPs assigned by Cilium kubernetes/apps/default/rustdesk/app/helmrelease.yaml50-66

Sources:

System Architecture: Utility Service Mapping

This diagram bridges the high-level utility names to their specific Kubernetes controller and service definitions.

Utility Entity Mapping

[Flowchart Diagram]

Sources:

Deployment Pattern

All applications in this namespace follow the standard app-template pattern:

Sources:

Graph View

Backlinks