Moby Now represents a new era of container orchestration designed for teams that need simplicity without sacrificing power. This platform streamlines deployment workflows and improves the reliability of distributed applications across hybrid environments.
Engineers and platform teams use Moby Now to standardize runtime configurations and accelerate release cycles. The following sections outline its core capabilities, integration options, and practical guidance for everyday operations.
| Component | Description | Default | Configurable |
|---|---|---|---|
| Runtime Engine | Lightweight container runtime optimized for quick startup | auto-detect | yes |
| Orchestrator | Built-in scheduler with rolling update support | enabled | yes |
| Networking Stack | CNI-based network model with service discovery | calico | yes |
| Storage Plugins | CSI drivers for cloud and on-prem storage | none | yes |
| Security Profiles | Pod security policies and role-based access controls | baseline | strict |
Getting Started with Moby Now
Getting started with Moby Now involves installing the CLI, configuring a cluster profile, and launching your first workload. The modular design lets you enable only the features you actually need, which keeps resource usage predictable.
Quick start guides include step-by-step commands for provisioning nodes, attaching storage, and exposing services. Automation hooks are provided so you can integrate the platform into existing CI pipelines with minimal changes.
Cluster Management and Scaling
Cluster management in Moby Now focuses on declarative configuration and self-healing behavior. Admins can define node groups, update strategies, and backup schedules through a unified control plane.
Autoscaling Options
Horizontal pod autoscalers respond to CPU, memory, and custom metrics. Cluster autoscalers add or remove nodes based on pending workload demand, helping to control costs during traffic spikes.
Upgrade Workflow
Rolling updates are performed safely using controlled drain and cordon operations. Version compatibility checks ensure that node images and add-ons remain in sync during transitions.
Security and Compliance
Security and compliance capabilities are central to Moby Now, with support for encrypted secrets, network policies, and image scanning. Role-based access controls limit what teams can deploy and where they can deploy it.
Image Validation
Images pulled from registries are checked against allowlists and vulnerability databases before they are scheduled. Failed checks block deployments and generate audit logs for review.
Audit and Reporting
Detailed audit trails record configuration changes, user actions, and runtime anomalies. Reports can be exported to meet internal governance requirements and external standards.
Integration and Extensibility
Moby Now integrates with popular monitoring, logging, and service mesh tools out of the box. You can extend the platform using plugins, webhooks, and custom controllers to fit existing workflows.
API and CLI
A consistent REST API and powerful CLI enable scripted operations and third-party integrations. Both interfaces support the same feature set, so you can choose the right tool for each task.
Ecosystem Connectors
Pre-built connectors support cloud load balancers, DNS providers, and secret managers. This reduces manual setup and helps teams maintain a uniform environment across providers.
Operational Best Practices and Recommendations
- Define node selectors and taints to control which workloads run on specific hardware.
- Enable image scanning and enforce pod security policies before promoting to production.
- Use namespaces to separate environments and teams within the same cluster.
- Schedule regular backups of cluster state and etcd data to protect against accidental loss.
- Monitor resource usage and set appropriate requests and limits for every workload.
FAQ
Reader questions
How does Moby Now handle node failure and rescheduling?
When a node becomes unreachable, the orchestrator automatically reschedules pods onto healthy nodes based on declared affinity and resource requirements.
Can I use my own continuous delivery pipelines with Moby Now?
Yes, the platform exposes webhook endpoints and CLI hooks that let you connect existing pipelines while preserving policy enforcement and audit controls.
What networking options are supported in a Moby Now cluster?
You can choose between Calico, Cilium, or custom CNI configurations, with support for network policies, service load balancing, and secure ingress paths.
Is there a vendor lock-in risk when using managed services for Moby Now?
Because the platform is built on open standards, you can move clusters and workloads across on-prem and multiple cloud providers without major refactoring.