Release Notes 2.4.1

[Trink0]

Krateo 2.4.1: Focused Improvements for CRDGen and Core Provider

Krateo 2.4.1 is a minor but important upgrade that introduces targeted enhancements to the CRDGen and Core Provider components.

We chose not to rush these updates into the 2.4 release, preferring instead to give them the attention they deserve in a dedicated follow-up. Let’s dive into what’s new.

📦 CRDGen: Better Handling of JSON Schemas

This update addresses several edge cases in the generation of Custom Resource Definitions (CRDs), improving the tool’s reliability and correctness.

Fixes include:
• Proper handling of enum types where values are numeric strings.
• Correct rendering of CRDs from JSON Schemas with duplicate struct definitions.
• Fix for failed CRD generation when values.schema.json includes a root-level $ref.

🔁 Core Provider: Smarter Resource Management with Cumulative Hashes

This release introduces a cumulative hash mechanism to improve the tracking and consistency of deployed resources. It also includes a broader refactor of deployment and RBAC handling.

✅ Key Changes:
• Legacy cleanup: Removed deprecated ClusterRole functions and related tests, replaced by a streamlined Apply/Uninstall workflow.
• FNV-based hashing: Added cumulative hash computation using the FNV algorithm for resource tracking.
• Smarter RBAC and Deployment:
• Improved support for DryRun mode.
• Introduced digest verification to ensure deployment integrity.

🔁 Auto-Sync for Composition Dynamic Controller

From version 2.4.1 onwards:
• Changes to any composition-dynamic-controller-related resources (deployments or RBAC) will automatically propagate to all active instances.
• Manual changes to these resources will be automatically reverted to the expected state, ensuring consistent environments across the board.

🆙 How to upgrade

helm upgrade installer installer \ --repo https://charts.krateo.io \ --namespace krateo-system \ --create-namespace \ --install \ --version 2.4.1 \ --wait

🎯 Final Thoughts

While 2.4.1 may be a minor release number-wise, its impact on stability, consistency, and developer confidence is significant. These improvements lay a stronger foundation for the next wave of features arriving in Krateo 2.5.

Here’s a preview of what’s coming:
• Composable Portal v2 – A major upgrade to our YAML-based frontend framework, making it more readable, modular, and truly composable.
• Multitenancy in action – Built into Krateo from day one, multitenancy will now come to life with real-world examples, practical use cases, and fine-tuning options.
• FinOps 1.0 – A new FinOps tab inside compositions will display cost and resource usage data. We’re also introducing Open Policy Agent (OPA) to let you define custom rules and optimization strategies.

As always, we welcome your feedback and contributions. 🙌