Releases: oracle/oracle-database-operator
1.2.0
This release includes the following features
New Lifecycle Features in V1.2.0 Release (Controllers Enhancements)
-
ORDSSERVICES
Install on SIDB and ADB
Provision and Delete ORDS instances -
SIDB
Oracle Database 23ai Free support
Oracle Database 23ai Free-lite support
SIDB resource management
True Cache support for Free SIDB databases (Preview)
Observer for FastStartFailover with Data Guard
Snapshot Standby support in Data Guard setup -
Globally Distributed Database : Support for Oracle Database 23ai Raft replication
-
Autonomous Database: support for Database cloning
-
Multitenant DB:
ORDS-based Controller: assertive deletion policy.
New LRES based Controller (ARM & AM)
PDBs settings with init parameters config map
Assertive deletion policy. -
Database Observability (preview)
Support for Database Logs (in addition to Metrics)
Support for the latest Exporter container images
Bug Fix: Prometheus label config -
Oracle Base Database Service: support for Oracle Database 23ai Cloning, using KMS Vaults, PDB creation.
The Operator itself, as a product, brings the following new features:
- Upgraded Kubernetes API version to V4
- Published on operatorhub.io
- Operator Lifecycle Manager (OLM) support (i.e., install from operatorhub.io)
- Validated on Google Kubernetes Engine
Changes
- Update README.md by @ting-lan-wang in #107
- Doc and comments enhancement by @IshaanDesai45 in #114
- Squashed commit with all contents from new_stuff branch by @s1saurabh in #141
- Update README.md by @s1saurabh in #144
- Update README.md by @spavlusieva in #143
- gdd-changes by @jpverma85 in #146
- Known issues changed by @jpverma85 in #147
- doc_change by @jpverma85 in #151
- added known issues by @jpverma85 in #152
- Uds doc change by @jpverma85 in #153
- Added Features of Oracle DB Operator Release 1.2.0 by @psaini79 in #163
- Upgrade support from v1alpha1 to v4 APIs by @s1saurabh in #173
New Contributors
- @s1saurabh made their first contribution in #141
- @jpverma85 made their first contribution in #146
Full Changelog: 1.1.0...1.2.0
Full Changelog: 1.1.0...1.2.0
Contributors
Assets 2
1.1.0
This release includes the following features
- Enhanced security with scoped deployment to namespace
- Support for the new Oracle Database 23ai Free with the Single Instance DB (SIDB)
- Automatic deployment from the Oracle Kubernetes Engine (OKE) Console (Phase One)
- Automatic Storage Expansion for SIDB and Sharded DB
- User-Defined Sharding
- TCPS support customer provided certs
- Execute custom scripts during DB setup/startup
- Patching for SIDB Primary/Standby in Data Guard
- Long-term backup for Autonomous Databases (ADB): Moves to long-term backup and removes the deprecated mandatory backup
- Wallet expiry date for ADB: A user-friendly enhancement to display the wallet expiry date in the status of associated ADB
- Wait-for-Completion option for ADB: Supports kubectl wait command that allows user to wait for a specific condition on ADB
- New Database Observability controller (Preview - Metrics only)
- OKE workload Identify: Supports OKE workload identity authentication method. For more details, refer to Oracle Autonomous Database (ADB) Prerequisites
1.0.0
This release furnishes the following features
Single Instance Databases (a.k.a. SIDB)
The Single Instance DB controller supports the following Oracle database editions: Standard Edition (SE), Enterprise Edition (EE), eXpress Edition (XE), and DB23c Free.
The supported lifecycle operations include:
- provisioning a new database instance
- provisioning a new pre-built database instance
- cloning a database
- patching a database (in-place/out-of-place)
- deleting a database
- updating the database init parameters.
The SIDB controller furnishes additional features such as REST enabling a database, running multiple replicas of a database, setting up a database with LoadBalancer, installing APEX, enabling TCPS connections, and getting the connect string to the CDB.
Globally Distributed Database: made of Shards, containerized Shards are deployed over several Kubernetes pods
The Sharding Database controller supports the following lifecycle operations:
- deploy the Shard topology (i.e., the Sharding infrastructure) using various options (check out the …/doc/sharding/Readme.md for more details)
- Add a Shard
- Delete a Shard
- Clone a Shard
DataGuard (Preview)
This controller allows:
- creating a Standby Database for a Single Instance database (see the prerequisites in …/doc/sidb)
- adding databases in the Data Guard configuration
- deleting a database configured for Data Guard.
Additional operations include connecting to the Primary, performing a Switchover, and patching the Primary and the Standby databases.
Autonomous Database
The Autonomous Database controller supports the following lifecycle operations
- provisioning an Autonomous Database (ADB)
- binding the operator to an existing ADB
- scaling Up/Down the OCPU core count or the storage
- managing the database ADMIN password
- downloading ADB instance credentials (i.e., wallets)
- Starting/Stopping/Terminating an ADB
- deleting an ADB from the resources (CRDs) known by the operator.
Base DB (formerly DBCS)
The BaseDB controller supports the following lifecycle operations
- provisioning a BaseDB
- binding to an existing BaseDB
- scaling UP/DOWN the shape of an existing BaseDB
- scaling UP the storage of an existing Base DB
- deploying a two-nodes RAC
- updating the license type
- terminating an existing BaseDB
Multitenant Databases (Exadata, PDB/CDB)
The controller supports:
- creating a new PDB
- cloning a PDB
- modifying the state of a PDB
- unplugging a PDB from a CDB
- plugging an unplugged PDB into a CDB
- deleting a PDB.
v0.2.1
v0.2.0
Oracle Database Operator for Kubernetes v0.1.0
This first release of the Oracle Database Operator for Kubernetes (a.k.a. OraOperator) supports Oracle Database deployed in and off Kubernetes clusters, more specifically:
- Autonomous Databases in OCI (Shared infrastructure), these do not run in Kubernetes;
- Containerized Single Instance Databases in the OCI Kubernetes Engine (OKE), and the Oracle Linux Cloud Native Environment (OLCNE);
- Containerized Oracle Sharded Databases in OKE and OLCNE.