diff --git a/release_notes/index.adoc b/release_notes/index.adoc
index 2bef850955..4e03511aad 100644
--- a/release_notes/index.adoc
+++ b/release_notes/index.adoc
@@ -14,6 +14,9 @@ include::topics/templates/document-attributes-community.adoc[]
 include::topics/templates/release-header.adoc[]
 
 
+== {project_name_full} 19.0.0
+include::topics/19_0_0.adoc[leveloffset=2]
+
 == {project_name_full} 18.0.0
 include::topics/18_0_0.adoc[leveloffset=2]
 
diff --git a/release_notes/topics/19_0_0.adoc b/release_notes/topics/19_0_0.adoc
index e9f8714d3d..f1a0270881 100644
--- a/release_notes/topics/19_0_0.adoc
+++ b/release_notes/topics/19_0_0.adoc
@@ -44,3 +44,24 @@ Specifically, the services will not be able to differentiate cached and non-cach
 Hence, custom extensions that access objects in local storage or cache through `KeycloakSession`
 methods must be reviewed.
 See link:{upgradingguide_link}[{upgradingguide_name}] for details.
+
+= Deprecated `podDisruptionBudget` in the legacy {project_operator}
+
+With this release, we have deprecated `podDisruptionBudget` field in the Keycloak CR of the https://github.com/keycloak/keycloak-operator[legacy {project_operator}].
+This optional field will be ignored when the Operator is deployed on Kubernetes version 1.25 and higher.
+
+As a workaround, you can manually create the Pod Disruption Budget in your cluster, for example:
+```yaml
+apiVersion: policy/v1
+kind: PodDisruptionBudget
+metadata:
+  labels:
+    app: keycloak
+  name: keycloak
+spec:
+  maxUnavailable: 1
+  selector:
+    matchLabels:
+      component: keycloak
+```
+See also the https://kubernetes.io/docs/tasks/run-application/configure-pdb/[Kubernetes Documentation].
\ No newline at end of file
diff --git a/server_installation/topics/operator/installation.adoc b/server_installation/topics/operator/installation.adoc
index 03ba9d6287..61cbf6f7c6 100644
--- a/server_installation/topics/operator/installation.adoc
+++ b/server_installation/topics/operator/installation.adoc
@@ -158,5 +158,6 @@ endif::[]
 
 * The usage of embedded DB is not supported in a production environment.
 * Backup CRD is deprecated and not supported in a production environment.
+* The `podDisruptionBudget` field in the Keycloak CR is deprecated and will be ignored when the Operator is deployed on Kubernetes version 1.25 and higher.
 * We fully support using the rest of the CRDs in production, despite the `v1alpha1` version. We do not plan to make any breaking changes in this CRDs version.
 
diff --git a/upgrading/topics/keycloak/changes-19_0_0.adoc b/upgrading/topics/keycloak/changes-19_0_0.adoc
index 9b7ceade88..ddf272dd03 100644
--- a/upgrading/topics/keycloak/changes-19_0_0.adoc
+++ b/upgrading/topics/keycloak/changes-19_0_0.adoc
@@ -214,3 +214,24 @@ public class MyUserStorageProvider implements UserLookupProvider, ... {
 }
 ----
 
+
+= Deprecated `podDisruptionBudget` in the legacy {project_operator}
+
+With this release, we have deprecated `podDisruptionBudget` field in the Keycloak CR of the https://github.com/keycloak/keycloak-operator[legacy {project_operator}].
+This optional field will be ignored when the Operator is deployed on Kubernetes version 1.25 and higher.
+
+As a workaround, you can manually create the Pod Disruption Budget in your cluster, for example:
+```yaml
+apiVersion: policy/v1
+kind: PodDisruptionBudget
+metadata:
+  labels:
+    app: keycloak
+  name: keycloak
+spec:
+  maxUnavailable: 1
+  selector:
+    matchLabels:
+      component: keycloak
+```
+See also the https://kubernetes.io/docs/tasks/run-application/configure-pdb/[Kubernetes Documentation].
\ No newline at end of file