The Junovy Glossary
What You Will Learn
- Definitions for the key terms used throughout this book
- A reference table you can come back to anytime
How to Use This Glossary
You do not need to memorize these terms now. Skim them once, then come back whenever you hit a word you do not recognize. Each term gets a full explanation in its own chapter later.
| Term |
Definition |
Learn More |
| Kubernetes (K8s) |
A system that runs and manages containers across multiple servers. Think of it as a game server manager. |
Chapter 3 |
| Container |
A packaged application with everything it needs to run. Like a Godot HTML5 export. |
Chapter 2 |
| Docker |
The tool used to build container images. |
Chapter 2 |
| Pod |
The smallest unit in Kubernetes. One or more containers running together. |
Chapter 3 |
| Deployment |
A Kubernetes object that manages copies of a Pod and handles updates. |
Chapter 3 |
| Service |
A stable network address that routes traffic to Pods. |
Chapter 3 |
| Ingress |
A rule that exposes a Service to the internet with a domain name. |
Chapter 3 |
| Namespace |
An isolated area within the cluster. Each client gets one. |
Chapter 3 |
GitOps and Deployment Terms
| Term |
Definition |
Learn More |
| GitOps |
A workflow where Git is the single source of truth for infrastructure. Push to Git, and the cluster updates. |
Chapter 4 |
| Flux CD |
The GitOps tool Junovy uses. It watches Git and applies changes to the cluster. |
Chapter 4 |
| Kustomize |
A tool that customizes Kubernetes YAML without editing the originals. Uses base + overlay. |
Chapter 4 |
| Helm |
A package manager for Kubernetes. Apps are packaged as "charts" with configurable values. |
Chapter 4 |
| Reconciliation |
The process where Flux compares Git to the cluster and applies any differences. |
Chapter 4 |
| HelmRelease |
A Flux object that tells the cluster to install/update a Helm chart. |
Chapter 4 |
Junovy-Specific Terms
| Term |
Definition |
Learn More |
| Tenant |
A client's isolated environment. One namespace, their apps, their secrets. |
Chapter 5 |
| hst- |
The namespace prefix for all client tenants. Example: hst-bizdom, hst-junovy. |
Chapter 5 |
| DDS |
Drake Design Studio, the original name for Junovy. You will see it in repo names. |
Chapter 1 |
| Bird names |
Internal DNS codenames for infrastructure: robin (K8s API LB), penguin (Vault), hawk (Ops LB), finch (External LB), sparrow (WireGuard VPN), hummingbird (CoTurn). All on spynl.net. |
Chapter 5 |
| ECR |
Elastic Container Registry (AWS). Where Junovy stores container images. |
Chapter 2 |
Security Terms
| Term |
Definition |
Learn More |
| Secret |
Sensitive data like passwords, API keys, or certificates. Never commit to Git unencrypted. |
Chapter 7 |
| SOPS |
A tool for encrypting secrets in Git files. Legacy system, being replaced by Vault. |
Chapter 7 |
| HashiCorp Vault |
A secrets management server. The preferred way to store secrets at Junovy. |
Chapter 7 |
| External Secrets Operator |
A Kubernetes component that syncs secrets from Vault into the cluster automatically. |
Chapter 7 |
| GPG signing |
Cryptographic proof that a Git commit came from you. Required on all commits. |
Chapter 6 |
Infrastructure and Networking Terms
| Term |
Definition |
Learn More |
| Traefik |
The ingress controller that routes external web traffic to applications inside the cluster. |
Chapter 3 |
| Linkerd |
A service mesh that provides mutual TLS (mTLS) between services inside the cluster. |
Chapter 5 |
| Longhorn |
A distributed storage system that provides persistent volumes for databases and file storage. |
Chapter 5 |
| SeaweedFS |
An S3-compatible object storage system running in the cluster for file and media storage. |
Chapter 5 |
| external-dns |
Automatically creates DNS records when you create an Ingress resource. No manual DNS configuration needed. |
Chapter 5 |
| Keycloak |
An identity and single sign-on (SSO) server used for authentication across Junovy services. |
Chapter 5 |
| CoreDNS |
The internal DNS server running on a VM at 10.42.1.9 that resolves bird-name and service DNS records. |
Chapter 5 |
| Weave GitOps |
A web dashboard for visualizing Flux CD state, available at gitops.spynl.net. |
Chapter 5 |
| HAProxy |
Load balancers at the infrastructure layer that sit in front of the cluster (robin, hawk, finch). |
Chapter 5 |
| spynl.net |
The primary internal DNS domain. Infrastructure bird names and service names resolve here. |
Chapter 5 |
Key Takeaways
- This glossary covers ~35 key terms you will encounter in this book
- You do not need to memorize them now - come back as needed
- Each term links to the chapter where it is fully explained
What Is Next
Next up: What Is a Container (Chapter 2) where you will learn how containers work using a Godot export analogy.
