v2.0.0 🎉
We are very pleased to announce the release of Pelorus 2.0.0!
This is the minimum viable release for Pelorus that brings the stability, features and the documentation required for our upstream community.
New & Notable
Generic Commit Time: Tekton, Binary Builds, and External Images
Support for commit time from Tekton was highly requested. Because everyone's workflow is highly customizable, we resisted the temptation to guess. Users can run a new image exporter, and can configure it to look for commit information in whatever image annotation they use.
Because they have full control over git information while building, it doesn't even need to reach out to a git forge (GitHub, BitBucket, etc.)!
As a consequence, this now supports:
- Tekton
- Binary Builds
- Images put into openshift by other means
Day 2 Prometheus: Data Storage & Backup
- Expose PV configuration for Prometheus
- S3 Prometheus / Thanos data storage
GitHub Failure Exporter
- Pelorus support for Github issues using issue labels
Jira Exporter Improvements
- Expanded support for number of issues
- ConfigMap support
Custom Certificates
You can now use custom certificates for most exporters.
Supported are:
| Exporter Type | Exporter Backend |
|---|---|
| Commit Time | BitBucket |
| Commit Time | Gitea |
| Commit Time | GitHub |
| Commit Time | GitLab |
| Failure | GitHub |
Usability Improvements (UX)
- Pelorus exporters are now, by default, run from published images. Previously, every user was building their own image with an S2I workflow.
- Configuration item names have been made more consistent and simpler.
- Each exporter can now be configured from ConfigMaps, making maintenance easier.
- Pelorus's overall configuration has been simplified.
- A troubleshooting script has been added that will help solve the question of "why isn't my data showing up in pelorus?"
- We now have a unified configuration system, which will log everything the exporter was configured with at startup. This will help with debugging client deployments.
Documentation
- Configuration documentation has been completely overhauled.
- Developer docs have been improved overall.
Demo
We have a new demo that:
- Shows more of the pelorus workflow
- Shows users how to use binary and 3rd party application builds with Pelorus
- Shows off Tekton support
- Serves as a bit of QA
Quality & Bug Fixes
- Now documented: our openshift version support, and exporter testing strategy.
- Fixed: time zones were incorrectly handled in some cases
- Prow CI integration jobs on OpenShift 4.9 - 4.11 executing 70+ tests each
- Fixed: certain metrics now report their time as the collection timestamp, making some queries / dashboards more correct.
- We now have a unified configuration system, which will log everything the exporter was configured with at startup. This will help with debugging client deployments. This also supports falling back to older configuration item names in a cleaner manner.
- Errors are reported in a more detailed manner when examining deeply-nested data, which is useful when inspecting openshift objects.
- The GitLab committime collector's performance has been improved.
Developer Experience
- We now have a way to set up a consistent developer environment with a single command, including other commandline tools (such as the openshift client).
- We now consistently format the code automatically.
Miscellaneous
- The GitHub committime exporter can now run without authentication, which is useful for public repositories.
- We now eat our own dogfood by tracking our own development with pelorus.
Release notes between 2.0.0 and 1.8.2
🎉 Release
- major release of the Pelorus project - MVR (#667)
🔡 Other changes
- update tekton to use epoch @weshayutin (#666)
- Allow to use EPOCH timestamp in the image annotation @mpryc (#665)
- timestamp timezone fix @KevinMGranger (#664)
Full Changelog: v1.8.2...v2.0.0
