Update Community Modules ​
IMPORTANT
Key Distinction: Community modules differ fundamentally from managed SAP BTP, Kyma runtime modules:
- Community modules are NOT handled in the Kyma CR - They are managed independently and are not part of the Kyma resource specification
- Community modules are NOT managed by Kyma Control Plane - The control plane does not automatically manage their lifecycle, update them, or monitor their health
- You must perform all the necessary actions - Installation, updates, and removal require manual intervention
Unlike managed modules, community modules aren't automatically updated or maintained. You are fully responsible for managing community modules, including keeping them updated, monitoring their health, and handling any issues that arise.
Prerequisites ​
Check the available versions for your community module. Run kyma module catalog to list all available modules and their versions in the community modules catalog. Alternatively, you can check the community modules catalog directly.
WARNING
Before updating a module, review the release notes and changelog for breaking changes or migration requirements. Some updates may require additional configuration or manual migration steps.
Context ​
Unlike managed modules in SAP BTP, Kyma runtime, community modules are not automatically updated. Regularly update your community modules to:
- Security: Receive security patches and vulnerability fixes that protect your cluster and applications
- New Features: Access the latest functionality, improvements, and capabilities added by the community
- Bug Fixes: Benefit from bug fixes and stability improvements
- Compatibility: Ensure compatibility with newer versions of Kyma modules and other dependencies
- Performance: Take advantage of performance optimizations and efficiency improvements
Procedure ​
You can update community modules using Kyma dashboard, Kyma CLI, or kubectl.