The Oracle Database Operator for Kubernetes (a.k.a. OraOperator) helps developers, DBAs, DevOps and GitOps teams reduce the time and complexity of deploying and managing Oracle Databases. It eliminates the dependency on a human operator or administrator for the majority of database operations.
active 2023-08-18 → 2026-08-18 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 1097 days from 2023-08-18 to 2026-08-18. Pushes: 44 total, peak 2 in a day. Pull requests: 94 total, peak 17 in a day. Issues: 127 total, peak 5 in a day. Comments: 290 total, peak 14 in a day. Stars: 58 total, peak 2 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| psaini79 | 89 | 18 | 22 | 24 |
| mmalvezz | 78 | 7 | 8 | 48 |
| IshaanDesai45 | 43 | 0 | 2 | 31 |
| rbaumgar | 41 | 0 | 0 | 31 |
| yunus-qureshi | 34 | 4 | 4 | 16 |
| ilfur | 27 | 0 | 0 | 17 |
| andbos | 25 | 0 | 0 | 17 |
| oracle-contributor-agreement[bot] | 23 | 0 | 4 | 19 |
| ting-lan-wang | 23 | 2 | 5 | 9 |
| marcstef-oracle | 23 | 11 | 0 | 5 |
| saurabhuja | 19 | 0 | 19 | 0 |
| tenstad | 15 | 0 | 3 | 9 |
| ca2510fl | 13 | 0 | 0 | 11 |
| jpverma85 | 12 | 0 | 11 | 0 |
| gotsysdba | 7 | 0 | 0 | 4 |
| Kuassim | 7 | 1 | 2 | 4 |
| spavlusieva | 7 | 1 | 4 | 0 |
| erikgb | 6 | 0 | 0 | 5 |
| s1saurabh | 5 | 0 | 3 | 2 |
| laguvard | 5 | 0 | 0 | 3 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#83psaini792026-05-11 19:21Feature to provide startup/setup scripts to SIDB
- Issue#237thomas-vt2026-05-01 20:13How to Increase query timeout
- Issue comment#233alinaqvion-hash2026-04-10 09:32Oracle Pod not coming UP after restart in active/standby deployment
- Issue#232alinaqvion-hash2026-04-08 09:33Oracle DB Pod not coming UP after restart or patch with new image for active/standby or cloned cases.
- Issue#223marcstef-oracle2026-03-19 21:11Cannot create PVC for ORDS access logs and missing retention policy support
- Issue#218ethenius2026-02-20 12:31Oracle Database Operator is not available on the Openshift 4.16 OperatorHub
- Issue#95ting-lan-wang2026-02-19 14:12Support ADB on Azure
- Pull request#217jpverma852026-02-18 02:41
- Issue comment#123marcstef-oracle2026-02-16 08:19DatabaseObserver: two config problems
- Pull request#215s1saurabh2026-02-12 05:37
- Pull request#215oracle-contributor-agreement[bot]2026-02-12 05:37
- Pull request#213s1saurabh2026-02-11 16:28
- Issue comment#213s1saurabh2026-02-06 11:47release 2.1
- Pull request#212oracle-contributor-agreement[bot]2026-02-06 10:29
- Issue#210jphalip2026-01-21 04:57Clarify whether primary and standby must be in the same namespace
- Issue comment#189parveen-verma-20252026-01-21 04:56Multisite Deployment with OraOperator
- Issue#208parveen-verma-20252026-01-21 04:42Memory Target - Parameter in singleinstancedatabase.yaml
- Issue comment#206andbos2026-01-09 14:04SIDB primary unhealthy and refuses to start properly after worker node poweroff/on
- Pull request#205oracle-contributor-agreement[bot]2025-12-15 10:28
- Pull request#204jpverma852025-12-09 18:04
- Pull request#204jpverma852025-12-09 05:26
- Pull request#204oracle-contributor-agreement[bot]2025-12-09 05:26
- Issue#203SyNuOra2025-12-05 08:41Typo: SIDB/REAMDME.md incorrect filename supplied for oc apply command for OpenShift RBAC
- Issue comment#202psaini792025-11-26 23:58Error deploying operator
- Issue#202psaini792025-11-26 23:48Error deploying operator
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 58 stars here means stars gained during the window, not the repo's star count.