From: Ben Scott <bscott@isc.org>
Date: Wed, 21 May 2025 21:58:30 +0000 (-0400)
Subject: [#3881] Note Stork+Kea+CB issues
X-Git-Tag: Kea-3.0.0~40
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e3cee3954a53d8ef7473a3b63bfb78272e29bf26;p=thirdparty%2Fkea.git

[#3881] Note Stork+Kea+CB issues
---

diff --git a/doc/sphinx/arm/stork.rst b/doc/sphinx/arm/stork.rst
index bfa4a06a2d..0602f2e07f 100644
--- a/doc/sphinx/arm/stork.rst
+++ b/doc/sphinx/arm/stork.rst
@@ -32,6 +32,16 @@ The ARM has a nice collection of screenshots that is frequently updated, to give
 an idea of what is currently available. Stork is in the midst of full development with
 monthly releases, so please check back frequently.
 
+.. note::
+
+   Stork uses Kea API calls from the :ischooklib:`libdhcp_host_cmds.so` and
+   :ischooklib:`libdhcp_subnet_cmds.so` hooks to make changes to Kea's
+   configuration.  Such usage is incompatible with the :ref:`_config-backend`
+   (CB).  Stork does not currently implement support for the
+   :ischooklib:`libdhcp_cb_cmds.so` needed to make changes to CB
+   configuration.  If using the Kea CB, Stork can only be safely used in a
+   "read-only" fashion.  Future versions of Stork will add CB support.
+
 .. _grafana:
 .. _prometheus: