Pelorus Upstream Support Statement
The Pelorus engineering team will provide best-effort level support for it on the currently latest released stable minor version of the OpenShift 4.
NOTE: Pelorus is currently automated tested against version 4.13 of OpenShift.
-
To file a bug, please create a Bug issue
-
To file a feature request, please create a Request a new feature issue
-
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 | Known issues | CI status |
|---|---|---|
| GitHub | status link | Integration CI present |
| GitHub Enterprise | status link | todo |
| Bitbucket | status link | Integration CI present |
| Gitlab | status link | Integration CI present |
| Gitea | status link | Integration CI present |
| Azure DevOps | status link | Integration CI present |
Failure Exporter
| Backend | Known issues | CI status |
|---|---|---|
| Jira | status link | Integration CI present |
| GitHub | status link | Integration CI present |
| Service Now | status link | todo |
| PagerDuty | status link | Integration CI present |
| Azure DevOps | status link | Integration CI present |
Deploytime Exporter
| Backend | Known issues | CI status |
|---|---|---|
| OpenShift | status link | Integration CI present |
Integration in CI
Pelorus is being tested and it's parts such as container images or documentation are being created by various Continuous Integration systems.
Most of the CI runs are invoked using Makefile allowing developer to replicate those runs on the local computer. Please refer to the Dev Guide for more information.
GitHub Actions
Each Pull Request is being tested by various GitHub Actions corresponding to the files being modified or triggers such as new release. List of all GitHub Actions enabled for Pelorus can be found in the .github folder of the project.
Prow OpenShift CI
Number of Pelorus jobs are running in dedicated Prow OpenShift CI, which is integrated with GitHub project. Triggers for those jobs are either new GitHub Pull Requests or periodic events.
Similarly to the GitHub Actions those jobs uses Makefile as the entry point for execution.
E2E Pull Request jobs consumes Pelorus deployment files, which are defined in the mig-demo-apps values.yaml project and requires secrets that are configured using vault.ci.openshift.org. Those secrets are then mounted by the Prow job definition and used by the Pelorus E2E script.
E2E periodic jobs uses deployment files defined in the mig-demo-apps periodic folder. Secrets and invocation script are identical to the Pull Request jobs differing in the Makefile targets, which uses different arguments passed to the Pelorus E2E script.
Exporters list covered by the Prow CI is available in the Backend Exporters section.
Thank you!
Thank you very much for your participation in the Pelorus community, your time and effort is very much appreciated!