Releases

This document outlines the Krkn Operator release strategy, Open Cluster Management (OCM) compatibility goals, and how the community prioritizes features, bug fixes, and security updates.

Release Cadence

Krkn Operator aims to deliver feature releases every 6–8 weeks. These releases may include new features, enhancements, usability improvements, and other roadmap items driven by community feedback and contributor activity.

The release cadence is intended to balance rapid delivery of value to users while maintaining stability and quality across supported environments.

Feature Requests and Roadmap

Community feedback plays a key role in shaping the future of Krkn Operator.

Feature requests submitted through GitHub issues, enhancement proposals, community discussions, and feedback forms are reviewed regularly and considered as part of the project roadmap.

Features are prioritized based on:

• Community interest
• User impact
• Project goals
• Contributor capacity

Planned enhancements and major initiatives will be communicated through project documentation, GitHub, community meetings, and release notes.

Bug Fixes and Security Updates

Bug fixes and security updates are prioritized independently of the feature release cadence.

Critical security vulnerabilities and high-impact issues may be addressed through patch or minor releases outside the normal release cycle when necessary.

Community contributions for bug fixes, testing, and validation are always welcome.

Open Cluster Management (OCM) Compatibility

Krkn Operator can be deployed and used independently or integrated with Open Cluster Management (OCM) for multi-cluster management and orchestration use cases.

For OCM-integrated deployments, the Krkn community aims to test and validate Krkn Operator against the latest two supported OCM releases. While compatibility with older OCM releases may work, it is not actively tested or guaranteed.

As Krkn Operator and OCM evolve, we will continue to collaborate on maintaining compatibility and ensure users can take advantage of new capabilities while minimizing upgrade challenges.

Reference Documentation

• OCM Releases: https://open-cluster-management.io/docs/release/
• OCM Project: https://open-cluster-management.io/

Release Notes

Each release includes documentation for:

• New features and enhancements
• Bug fixes
• Security updates
• Compatibility updates
• Breaking changes and deprecations
• Upgrade or migration guidance, when applicable

Any compatibility changes, breaking changes, or upgrade considerations will be documented as part of the release notes to help users plan upgrades and understand changes between releases.

Getting Involved

The Krkn community welcomes feedback, feature requests, bug reports, testing, and code contributions. Community participation helps shape the roadmap and improve the overall user experience.

For feature requests or bug reports, please open an issue in the Krkn-operator GitHub repository or participate in community discussions.