From 0e7edea7ef28ea6ed6edddfb4715dfcc25e492a1 Mon Sep 17 00:00:00 2001
From: Ismael Juma <ismael@juma.me.uk>
Date: Tue, 13 Sep 2022 12:02:54 -0700
Subject: [PATCH] MINOR: Mention that kraft is production ready in upgrade
 notes

---
 docs/upgrade.html | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/upgrade.html b/docs/upgrade.html
index 9ac1eccdb2cc6..6b6744788f1da 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -81,6 +81,8 @@ <h4><a id="upgrade_3_3_0" href="#upgrade_3_3_0">Upgrading a KRaft-based cluster
 
 <h5><a id="upgrade_330_notable" href="#upgrade_330_notable">Notable changes in 3.3.0</a></h5>
     <ul>
+        <li>KRaft mode is production ready for new clusters. See <a href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-833%3A+Mark+KRaft+as+Production+Ready">KIP-833</a>
+	    for more details (including limitations).
         <li>The partitioner used by default for records with no keys has been improved to avoid pathological behavior when one or more brokers are slow.
             The new logic may affect the batching behavior, which can be tuned using the <code>batch.size</code> and/or <code>linger.ms</code> configuration settings.
             The previous behavior can be restored by setting <code>partitioner.class=org.apache.kafka.clients.producer.internals.DefaultPartitioner</code>.