Design a Container Orchestration System

Functional Requirements:

• Deploy and manage containers across a cluster of machines (nodes).
• Support basic container lifecycle operations: start, stop, restart, delete.
• Schedule containers onto nodes based on available resources (CPU, memory).
• Monitor container and node health, and restart failed containers automatically.
• Expose containerized services to internal and external clients (basic service discovery and load balancing).
• Allow users to define resource limits and requests for containers.
• Support rolling updates and rollbacks for containerized applications.

Non-Functional Requirements:

• Scalability: System should support scaling to hundreds of nodes and thousands of containers.
• Reliability: Automatically recover from node or container failures to minimize downtime.
• Security: Basic authentication for API access and isolation between containers.
• Usability: Provide a simple REST API for users to interact with the system.
• Performance: Scheduling and container operations should complete within a few seconds.
• Maintainability: System components should be modular and easy to update or replace.