Replacing Kubernetes
Trying to replace Kubernetes with FlowLayer is a category error.
FlowLayer is for development runtime orchestration on a machine or controlled dev session.
Kubernetes is for production-grade cluster scheduling and operations.
Why this is a bad idea
- FlowLayer does not provide cluster scheduling.
- FlowLayer does not provide Kubernetes networking model.
- FlowLayer does not provide production self-healing primitives.
- Session token auth is not a production security model.
Better approach
- Use FlowLayer for fast local/distributed development feedback.
- Validate service interaction and startup behavior early.
- Hand off production concerns to Kubernetes (or another production platform) where they belong.
If you need production control-plane guarantees, do not try to stretch FlowLayer into that role.