Coverage Matrix
| Chkk Curated Release Notes | v1.0.1 to latest |
| Private Registry | Supported |
| Custom Built Images | Supported |
| Safety, Health, and Readiness Checks | v1.0.4 to latest |
| Supported Packages | Helm, Kustomize, Kube |
| EOL Information | Available |
| Version Incompatibility Information | Available |
| Upgrade Templates | In-Place, Blue-Green |
| Preverification | Available |
Bitbucket Overview
Bitbucket Cloud is Atlassian’s managed Git-based source control and CI/CD service, providing seamless integration with tools like Jira and Trello. It supports pull requests, code reviews, branch permissions, and integrated CI/CD pipelines, streamlining development workflows without additional infrastructure management. Bitbucket Data Center is Atlassian’s self-hosted edition that runs natively on Kubernetes, providing clustered high-availability, smart-mirror geo-caching, zero-downtime rolling upgrades, and full control over data residency, encryption, and custom plugins.Chkk Coverage
Curated Release Notes
Chkk monitors Bitbucket release notes, highlighting critical updates, API changes, and deprecations affecting your workflows. It proactively identifies impacts such as changes to API rate limits or discontinued features, providing clear, actionable alerts. For self-hosted instances, Chkk flags essential upgrade considerations and configuration changes, ensuring platform teams avoid unexpected operational disruptions.Preflight & Postflight Checks
Before upgrades, Chkk performs preflight checks to confirm compatibility, including supported Java/database versions, plugin statuses, and Kubernetes configurations. It ensures that upgrades do not skip required intermediate versions, helping avoid failures due to incompatible jumps. Post-upgrade checks verify cluster health, application functionality, and integration stability, promptly highlighting issues like plugin failures or repository indexing errors.Version Recommendations
Chkk actively tracks Atlassian’s support timelines, alerting you when Bitbucket versions approach end-of-life or face critical vulnerabilities. It recommends stable upgrade targets, often prioritizing Long Term Support (LTS) releases, balancing new features with proven stability. For Bitbucket Cloud, Chkk advises on critical upcoming changes, ensuring API migrations and security adjustments are handled smoothly and proactively.Upgrade Templates
Chkk provides detailed templates for in-place and blue-green Bitbucket upgrades, incorporating Atlassian’s best practices. Rolling upgrades maintain zero downtime by sequentially updating nodes in clusters, while blue-green strategies involve parallel environments and gradual traffic migration. These templates integrate seamlessly into GitOps and CI/CD workflows, significantly reducing the risk of errors during upgrade procedures.Preverification
Chkk’s preverification process simulates upgrades in isolated staging environments, identifying issues like database migration problems, plugin incompatibilities, or performance bottlenecks. It validates the entire upgrade path, including integrations and pipeline runners, allowing adjustments before production deployments. For Bitbucket Cloud, Chkk utilizes available Atlassian preview environments to preemptively address impacts from upcoming cloud-side updates.Supported Packages
Chkk fully supports various deployment approaches, including Helm, Kustomize, and direct Kubernetes YAML, ensuring compatibility with your existing infrastructure management tools. It respects custom images, private registries, and specialized configurations, seamlessly adapting to hybrid or traditional VM-based deployments. This comprehensive package support ensures smooth transitions and consistent management across different deployment scenarios.Common Operational Considerations
- Self-Hosted Runner Connectivity: Ensure Bitbucket Pipelines runners behind firewalls or proxies have proper egress to Atlassian endpoints. Misconfigurations cause pipeline connection failures, impacting continuous integration workflows.
- API Rate Limits: Bitbucket Cloud’s API limits (default 1,000 requests/hour) require careful integration design with caching and batching. Monitor usage closely and prefer Workspace Access Tokens to mitigate throttling issues.
- Large Repositories & Git LFS: Large repositories (>1 GB) degrade performance; adopt Git LFS for large binaries and regularly prune obsolete data. Monitor storage closely, especially in Data Center, to maintain efficiency.
- Search Service and Indexing: Data Center requires dedicated search (Elasticsearch/OpenSearch); ensure resilience and exclude unnecessary repositories from indexing. Regularly verify indexing health to maintain reliable code search.
- Access Tokens and Security: Regularly rotate and scope workspace/repo tokens tightly, utilizing expiration and IP allowlisting. Audit permissions frequently to minimize security risks from unauthorized code access.
- Cloud vs. Data Center Considerations: Cloud offers convenience and managed updates; Data Center provides control but requires significant infrastructure maintenance. Assess feature gaps, cost implications, and operational overhead carefully before migrations.