Orchestration Engine implements the platform API, authorization, metadata, scheduling, storage, networking, and resource lifecycle.
PastureStack is an independent community effort to preserve and modernize the
Rancher 1.6 ecosystem. It is not affiliated with Rancher Labs or SUSE.
This fork of rancher/cattle preserves
upstream history, authorship, licenses, and dependency notices.
Engine 0.183.340 is the published component for native environment creation with legacy/full API Keys. A new environment establishes its actual type before the first lifecycle job. Initial owner/network work is bound to that manager-created resource, while live Key, schema and ownership checks remain in force. Dedicated registration-token Basic authentication and restricted registration schemas are preserved; invalid tokens never fall back to a browser session. Assembled Server onboarding and active-agent acceptance remain separate gates.
API Key policies support full, closed and custom access, optional expiry and per-Key audit on both API roots. Grants remain bounded by the owner's live RBAC; explicit denies take precedence. Expanding access uses an actor-bound, single-use MFA confirmation. Secrets are creation-only and are never recorded in audit. See the API Key policy and audit contract for ancestry, revision, error and delegated-stream details.
The component artifact alone is not proof of complete platform acceptance. Use the current Server release for the published platform version. Source identities, checksums and acceptance evidence are recorded in the 0.183.340 release note, not installation commands.
Use the Server image to deploy the complete platform; cattle.jar is a component
artifact, not a replacement for its database, authentication, agent, or proxy.
Historical changes are in release notes.
The supported baseline uses JDK 25 and Maven, with MariaDB/MySQL and Liquibase for platform data. Exact toolchain/dependency versions and compatibility limits are documented in COMPATIBILITY.md. The build verifies the pinned embedded Cache artifact before installation in its build-local Maven repository.
Before publishing an Engine artifact, run the complete package gate:
bash scripts/check-cattle-jdk25-full-package
ENGINE_VERSION=0.183.340 bash scripts/build --release
bash scripts/check-release-artifact dist/artifacts/cattle.jarThe gate builds the Maven modules, checks dependency hygiene and packaged classes, and starts the application against isolated H2. Full database/platform lifecycle validation requires isolated MariaDB/MySQL and companion services. Component build/startup results do not establish every resource/role combination.
Frozen v1 schemas and v2 overlays are compatibility contracts. A deliberate frozen-schema migration must use the reviewed source generator and regression tests documented in COMPATIBILITY.md; never modify deployed schemas or infer permissions solely in the browser.
See SECURITY.md for reporting and security boundaries and ORIGIN.md for provenance.
The Web Console supplies user-facing translations. API fields, persisted values, event names, identifiers, and remote protocol errors are compatibility data and are not translated.
The inherited project uses Apache License 2.0. Bundled dependencies retain their own licenses and attribution.