How croyce97/k8s_prooject works
Project type and purpose
• This is a full-stack, containerized web application for “Restaurant Finder”–style amenity and review management.
• The client folder is a React single-page app; the server folder is a Node/Express REST API with PostgreSQL; k8s contains Kubernetes deployment manifests.
File structure
• Top-level:
• client/ – React front-end with Dockerfile and nginx.conf
• server/ – Node.js/Express back-end with Dockerfile, database SQL script, and .env
• k8s/ – YAML manifests for frontend, backend, and Postgres
• Patterns:
• Client and server are containerized separately.
• Back-end follows MVC-style (server.js + db/).
• Kubernetes manifests suggest three Deployments + Services, likely an Ingress at the front.
README
• The README simply says “k8s,” implying Kubernetes is the primary deployment target. No additional architecture notes.
Elements
• Labels: e.g., “React SPA Pod,” “Express API Pod,” “PostgreSQL Pod”
• Ports (e.g., 80 for nginx, 3000 for Express, 5432 for Postgres).