From 675eae558f249df33e8db65fbd65f3ffd6b30c10 Mon Sep 17 00:00:00 2001 From: Pravar Agrawal Date: Wed, 17 Apr 2024 14:49:20 +0530 Subject: [PATCH] update implement-extensions guidelines for runtime hook --- .../experimental-features/runtime-sdk/implement-extensions.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/book/src/tasks/experimental-features/runtime-sdk/implement-extensions.md b/docs/book/src/tasks/experimental-features/runtime-sdk/implement-extensions.md index 275ed022a6d1..f51beed74622 100644 --- a/docs/book/src/tasks/experimental-features/runtime-sdk/implement-extensions.md +++ b/docs/book/src/tasks/experimental-features/runtime-sdk/implement-extensions.md @@ -358,6 +358,8 @@ implementation documentation. ## Tips & tricks +Make sure to add the ExtensionConfig object to the YAML manifest used to deploy the runtime extensions (see [Extensionsconfig](#extensionconfig) for more details). + After you implemented and deployed a Runtime Extension you can manually test it by sending HTTP requests. This can be for example done via kubectl: