Orchestration Engine coordinates metadata, API, scheduling, storage, networking, and resource lifecycle for the preserved control platform. PastureStack is an independent community effort to preserve, audit, and modernize the Rancher 1.6 ecosystem. It is not affiliated with or endorsed by Rancher Labs or SUSE.
Upstream: rancher/cattle. This fork
preserves upstream history, authorship, dates, tags, licenses, and bundled
dependency notices. PastureStack maintenance is consolidated after the
preserved upstream boundary.
The latest public Engine release is
v0.183.326.
It restores read-only projectTemplate.isPublic in both v1 and v2-beta
responses for non-admin readers and omits unavailable remove actions on
non-owned templates. See the
release note for behavior,
tests, and compatibility details. Previous release notes remain in
docs/releases, and the
GitHub release history
records published artifacts.
The v0.183.324 tag is source-only and has no published release artifact.
The build retains Java 25, Ubuntu 26.04, Maven, Liquibase, MariaDB/MySQL,
WebSocket, concurrency, and runtime maintenance. It consumes the exact
5.7.4 JAR from
distributed-cache-runtime
and verifies its pinned digest and dependency metadata before installing it
into the build-local Maven repository. See
third-party/HAZELCAST.md for provenance.
Before publishing an Engine artifact or a Server image, run the complete JDK 25 package gate:
bash scripts/check-cattle-jdk25-full-packageAfter the gate passes, package and check the release artifact:
ENGINE_VERSION=0.183.326 bash scripts/build --release
bash scripts/check-release-artifact dist/artifacts/cattle.jarThe gate builds every Maven module, checks dependency hygiene and packaged classes, and starts the standalone application against isolated H2. Full database and platform checks require isolated MariaDB/MySQL and companion services. See COMPATIBILITY.md, SECURITY.md, and ORIGIN.md for those boundaries and source provenance.
The web console supplies user-facing translations. API fields, persisted values, event names, identifiers, and remote error payloads remain compatibility data and are not translated.
The inherited project remains under the Apache License 2.0. Inherited work and bundled dependencies retain their own attribution and licenses.