Migrating from Bitnami Charts and Images
Important: If you're using or considering the enterprise version of Opik or Comet, reach out to Sales@comet.com to access the enterprise deployment documentation.
Migrating from Bitnami Charts and Images
Section titled “Migrating from Bitnami Charts and Images”Opik's Helm chart has migrated from Bitnami charts and images to official Docker images and alternative Helm charts. This migration provides better compatibility, security, and maintainability.
Why Migrate from Bitnami?
Section titled “Why Migrate from Bitnami?”Bitnami changed its distribution model in 2025:
- Free old public images deprecated: Versioned images were moved to a "legacy" unmaintained repository with no security updates
- Hardened images now subscription-based: Access to maintained, secure images requires a paid subscription
- Bitnami charts tightly depend on Bitnami images: Bitnami charts cannot switch to official images, creating a dependency on the subscription model
By migrating to official Docker images and alternative Helm charts, we ensure:
- Continued Free Access: Official images from upstream projects (e.g.,
mysql,redis,zookeeper,minio) remain freely available with full version support - Security Updates: Direct access to security patches and updates from the official maintainers
- Production Stability: Ability to pin specific versions for production deployments
- Long-term Sustainability: Reduced dependency on third-party commercial services
- Community Standards: Official images follow industry best practices and are widely adopted, making it easier to find documentation and community support
Upgrade Instructions
Section titled “Upgrade Instructions”If you're upgrading the Opik Helm chart from version 1.9.39 or older, you need to enable the chart migration:
chartMigration:
enabled: trueHow the Migration Works
Section titled “How the Migration Works”The migration is seamless and data-preserving:
- Automatic Resource Recreation: The migration job automatically deletes and recreates StatefulSets and Deployments that are relevant for your installation
- Data Preservation: All PersistentVolumeClaims (PVCs) are preserved, ensuring no data loss
- Zero Downtime: The migration happens as a pre-upgrade hook, and new resources are created immediately after
Data Directory Configuration
Section titled “Data Directory Configuration”MySQL, MinIO, and Zookeeper are configured to use Bitnami data paths by default to ensure seamless migration:
- MySQL: Uses
/bitnami/mysql/datadata directory - MinIO: Uses Bitnami-compatible paths
- Zookeeper: Uses
/bitnami/zookeeper/datadata directory
What Changed
Section titled “What Changed”The following components have been migrated to use official Docker images:
- Zookeeper: Migrated from
bitnami/zookeeperto officialzookeeper:3.9.4image using the CloudPirates Zookeeper chart - MySQL: Migrated from Bitnami MySQL chart to comet-mysql-helm chart using the official
mysql:8.4.2image - Redis: Migrated from Bitnami Redis chart to CloudPirates Redis chart using the official
redis/redis-stack-server:7.2.0-v10image - MinIO: Migrated from Bitnami MinIO chart to CloudPirates MinIO chart using the official
minio/minioimage
Benefits of Migration
Section titled “Benefits of Migration”- Official Images: Using official Docker images provides better security updates and community support
- Simplified Configuration: Reduced complexity in chart dependencies
- Better Compatibility: Improved compatibility with modern Kubernetes versions
- Maintained Charts: Active maintenance and updates from the community
Need Help?
Section titled “Need Help?”If you encounter issues during migration, please check the troubleshooting guide or reach out for support.