October 26, 2026 Release Notes - 2.3.0

Breaking changes

Upgrading from Orchestrator v2.2.0 changes two legacy Autonomous Database alarm presets through Observability v0.3.0. adb-cpu-alarm changes from CpuUtilization[1m].mean() > 80 to CpuUtilization[5m].mean() > 85; adb-storage-alarm changes from StorageUtilization[1m].mean() > 80 to StorageUtilization[30m].mean() > 85. Both presets also add the provider = DBM freeform tag. These changes affect existing alarms even when no new alarm settings are supplied. Review the longer evaluation windows and higher thresholds before applying.
To preserve the previous queries, keep each existing alarm key and its destinations, remove preconfigured_alarm_type, and configure supplied_alarm with namespace = "oci_autonomous_database", severity = "CRITICAL", and the corresponding original query above. Retain the alarm's other configured settings and review the plan before applying; no resource-key or state migration is required for this configuration change.

Flow-log entries in logging_configuration.service_logs can reference configured VCN and subnet keys in resource_id, allowing compartments, network targets, log groups and explicit flow logs to be created in one apply. Existing literal OCIDs and other service-log inputs are preserved. Compartment-wide flow_logs discovery is unchanged; it does not provide same-apply discovery of newly created targets.
All Observability modules now use the published v0.3.0 release. This adds alarm settings, Streaming-to-Logging-Analytics connector fixes, and optional Logging Analytics custom-content imports.
Networking updated to the published v0.9.1 release, including DNS steering-policy and private-view RRset fixes, same-module remote-peering region inference, DNS resolver tag inheritance, reserved-public-IP NLB fixes, and optional private NLB IPv4 selection.
IAM source URLs now use oci-landing-zones/terraform-oci-modules-iam, retaining v0.3.5. Security, Governance, OCVS, Workloads (v0.2.9), and Exadata references are unchanged. See Modules Versions.

Review DNS resolver replacement actions before applying. Networking version-tag updates can defer resolver discovery until apply; provider replacement clears attached views, forwarding rules, and tags before restoring them. An interrupted apply can leave these properties cleared. Resolver tag inheritance can also change policies that use those tags for access control.
Setting or changing assigned_private_ipv4 on an existing NLB requires replacement; review the traffic impact before applying.
Streaming-to-Logging-Analytics connectors require target.log_source_identifier. For external streams in another compartment whose dependency lacks compartment metadata, set source.compartment_id. Imported Logging Analytics custom content survives Terraform destroy; remove unused content through Logging Analytics.