MintPress v4 Platform Updates
MintPress v4 uses a completely new stack built from the ground up using a container platform.
- Built on Kubernetes; can run on any flavor of K8s, or even a single VM via k3s.
- No reliance on CINC server, but can still be used for Virutal Machine (VM) configuration management; all Oracle Fusion Middleware (FMW) configurations are now independent of CINC and management with MintPress controllers.
- Full integration with CINC for VM configuration management is still available, and is recommended by LimePoint.
- Uses the OpsChain Orchestration Engine underneath, developed by LimePoint from scratch, with no reliance on third-party tooling (e.g., Bamboo is deprecated as the Run-time engine in MintPress v4).
- All MintPress v3 SDK, configurations, and asset templates are compatible with MintPress v4.
- MintPress v4 is based on Git-ops. Therefore, if configurations or scripts are not stored in a Git Repository, MintPress v4 cannot use them.
- MintPress v4 is an API first platform, every functionality is accessible via an API and can be easily integrated with.
About MintPress & CINC Integration
- CINC integration in MintPress v4 is optional, not deprecated. MintPress v3 had a technical dependency on CINC which meant that it could not function overall if CINC was unavailable, that has changed in MintPress v4.
- CINC remains fully supported within the MintPress ecosystem, and LimePoint recommends its continued use for all Infrastructure Configuration Management.
- We continue to enhance MintPress v4 with native configuration-management capabilities.
- Over future releases, the MintPress v4 platform aims to gradually incorporate more of the capabilities currently delivered through CINC.
- At this stage, there is no plan to retire or discontinue support for CINC, and customers can continue using it confidently as part of their configuration-management workflow.
Technology Stack Changes
MintPress v4 architecture is significantly different to MintPress v3. The following table provides a high-level comparison:
| Aspect | MintPress v3 | MintPress v4 |
|---|---|---|
| Technology Stack | Groovy on Apache Tomcat | Containerized Platform (defaults to k3s) |
| CINC Server | Mandatory | Optional |
| Web Server | Caddy | Nginx |
| Database | MySQL | PostgreSQL |
| Feature Set | Local agents, dependent on VM resources (CPU/memory) | Agents are containerized; scalable as required |
| UI | Multiple UIs (RT, Console) | Unified UI (API-backed + CLI) |
| Libraries | Shared server for all libraries (e.g., jq available for all users) | Choose your tools via Dockerfile; install only what you need |
| Local Development | Not available | Local development mode (runs on laptops) |
| Multi-tenancy | Not native; only possible via security rules | Multi-tenancy out-of-the-box |
| High Availability | Not available OOB (only via processes) | HA OOB (can be deployed A/A), Rolling Upgrades without downtime (unless DB changes) |