TazLab K8s Operators

Scope

This page covers the operator and namespace layers in the active tazlab-k8s Flux graph.

Current Synthesis

The operator side of tazlab-k8s is the platform layer that establishes the cluster’s base capabilities before application workloads are allowed to converge.

Covered Layers

infrastructure-operators-namespaces

  • creates the ai-agents namespace
  • serves as the namespace foundation for agent workloads

infrastructure-operators-core

  • installs cert-manager
  • installs traefik
  • installs reloader
  • creates namespace scaffolding for dex, auth, cloudflare-ddns, tazlab-db, and hugo-blog

infrastructure-operators-data

  • installs postgres-operator (Crunchy PGO)
  • prepares the operator that backs tazlab-db

infrastructure-monitoring

  • installs metrics-server
  • installs kube-prometheus-stack
  • creates Grafana ingress and bootstrap-secret sync surfaces
  • provides dashboards and metric visibility for the cluster

Why It Matters

These layers are the prerequisites for nearly everything else in the cluster. If an operator layer is wrong, every downstream workload can fail even when its manifest is correct.

Relationships

Source Basis

  • tazlab-k8s/clusters/tazlab-k8s/infrastructure-operators-namespaces.yaml
  • tazlab-k8s/clusters/tazlab-k8s/infrastructure-operators-core.yaml
  • tazlab-k8s/clusters/tazlab-k8s/infrastructure-operators-data.yaml
  • tazlab-k8s/clusters/tazlab-k8s/infrastructure-monitoring.yaml
  • tazlab-k8s/infrastructure/operators/*