Pelorus Upstream Support Statement
The Pelorus engineering team will provide best-effort level support for Pelorus on the currently latest and the latest previous released versions of Openshift. More specifically if the latest released version of Openshift is 4.10, the engineering team will accept issues written for OpenShift 4.10 and 4.9.
-
To file a bug please create a Github issue with the label "kind/bug"
-
To file a feature request create a Github issue with the label "feature"
-
You may also consider opening a discussion thread to discuss any feature, bug, or enhancement prior to opening a Github issue.
Backend Exporters
Pelorus's exporters support various backends or services. The Pelorus team is working to ensure an optimal experience for each backend integrated with Pelorus. Our goal is for each backend to be checked by OpenShift's Prow Continuous Integration system, to ensure the quality of each service's integration with Pelorus.
Below is a list of the status of each backend per Pelorus exporter. Any backend with out CI integration will have an associated Github issue in CI status and Status. To get the latest known status please refer to the issue.
Committime Exporter
| Backend | Status | CI status |
|---|---|---|
| GitHub | status link | Integration CI present |
| GitHub Enterprise | status link | todo |
| Bitbucket | status link | todo |
| Gitlab | status link | todo |
| Gitea | status link | todo |
| Azure DevOps | status link | todo |
Failure Exporter
| Backend | Status | CI status |
|---|---|---|
| Jira | status link | todo |
| GitHub | status link | Integration CI present |
| Service Now | status link | todo |
Deploytime Exporter
| Backend | Status | CI status |
|---|---|---|
| OpenShift | status link | Integration CI present |
Thank you!
Thank you very much for your participation in the Pelorus community, your time and effort is very much appreciated!