About This Architecture

k3s single-node Kubernetes cluster running a complete application stack with NGINX Ingress Controller, cert-manager for TLS, and microservices including GoTrue authentication, Medbar UI, Medbar API, and PostgreSQL backend. External traffic routes through the Ingress Service on ports 443 (HTTPS) and 80 (HTTP) to the NGINX Ingress Controller, which applies Ingress Rules to distribute requests to backend services. The architecture demonstrates production-grade patterns including certificate management, persistent storage via StatefulSet and local-path StorageClass, and service-to-service networking within the kube-system and default namespaces. This single-node setup is ideal for development, testing, edge deployments, or resource-constrained environments where full multi-node HA is unnecessary. Fork this diagram on Diagrams.so to customize service ports, add NetworkPolicy rules, or adapt the storage backend for your infrastructure.

People also ask

How do I set up a production-ready single-node Kubernetes cluster with ingress, TLS, and microservices?

This k3s diagram shows a complete single-node Kubernetes deployment where external traffic enters via NGINX Ingress Controller on ports 80/443, cert-manager handles TLS certificates, and microservices (GoTrue, Medbar UI/API) communicate through Kubernetes Services. PostgreSQL runs as a StatefulSet with persistent storage using local-path StorageClass, making this architecture suitable for edge dep