From 5a5b8813b44a728ff1aba517ca05c2e544e36af8 Mon Sep 17 00:00:00 2001 From: stianst Date: Wed, 29 Jan 2025 02:24:22 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20main=20from=20=20@=2049bdd293e?= =?UTF-8?q?f918c3b0ef651a3db2fbb63ff4f0eea=20=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 2024/01/keycloak-2305-released.html | 3 + nightly/guides.html | 15 ---- nightly/operator/advanced-configuration.html | 90 ++++++++++++++++++++ nightly/securing-apps/overview.html | 2 +- nightly/server/importExport.html | 10 +++ 5 files changed, 104 insertions(+), 16 deletions(-) diff --git a/2024/01/keycloak-2305-released.html b/2024/01/keycloak-2305-released.html index 0785033b828..93f92bb6685 100644 --- a/2024/01/keycloak-2305-released.html +++ b/2024/01/keycloak-2305-released.html @@ -62,6 +62,9 @@

Keycloak 23.0.5 released

January 29 2024

+

To download the release go to Keycloak downloads.

diff --git a/nightly/guides.html b/nightly/guides.html index d31cc70be47..d27f2d8fae5 100644 --- a/nightly/guides.html +++ b/nightly/guides.html @@ -786,21 +786,6 @@
Keycloak Node.js adapter -
- Node.js adapter to protect server-side JavaScript apps -
-
- - - - -
-
-
-
- Keycloak Node.js adapter - -
Node.js adapter to protect server-side JavaScript apps
diff --git a/nightly/operator/advanced-configuration.html b/nightly/operator/advanced-configuration.html index 45dd3affdd2..8460533ffdf 100644 --- a/nightly/operator/advanced-configuration.html +++ b/nightly/operator/advanced-configuration.html @@ -639,6 +639,96 @@

Example with OpenShift

+
+

Managing Keycloak Operator Updates (Preview)

+
+

The Keycloak Operator offers updates strategies to control how the Operator handles changes to the Keycloak CR.

+
+
+

Supported Updates Types:

+
+
+
+
Rolling Updates
+
+

Update the StatefulSet in a rolling fashion, minimizing downtime (requires multiple replicas).

+
+
Recreate Updates
+
+

Scale down the StatefulSet before applying updates, causing temporary downtime.

+
+
+
+
+

Configuring the Update Strategy

+
+

The update strategy is specified within the spec section of the Keycloak CR YAML definition.

+
+
+ + + + + +
+ + +
+

During this preview stage, the update strategy defaults to mimicking Keycloak 26.1 or older behavior: +When the Keycloak CR’s image field changes, the Operator scales down the StatefulSet before applying the new image, resulting in downtime. +Any configuration change will be a rolling update.

+
+
+
+
+
+
apiVersion: k8s.keycloak.org/v2alpha1
+kind: Keycloak
+metadata:
+  name: example-kc
+spec:
+  update:
+    strategy: Recreate|<not set> (1)
+
+
+
+ + + + + +
1Set the desired update strategy here (Recreate in this example).
+
+ + +++++ + + + + + + + + + + + + + + + + + + + +
Table 1. Possible field values
ValueDowntime?Description

<not set> (default)

On image name or tag change

Mimics Keycloak 26.1 or older behavior. +When the image field changes, the StatefulSet is scaled down before applying the new image.

Recreate

On any configuration or image change

The StatefulSet is scaled down before applying the new configuration or image.

+
+
diff --git a/nightly/securing-apps/overview.html b/nightly/securing-apps/overview.html index d2a42058f63..0cf21f84826 100644 --- a/nightly/securing-apps/overview.html +++ b/nightly/securing-apps/overview.html @@ -191,7 +191,7 @@

Node.js (server-side)

diff --git a/nightly/server/importExport.html b/nightly/server/importExport.html index 1030ebca30b..33d72dd3f40 100644 --- a/nightly/server/importExport.html +++ b/nightly/server/importExport.html @@ -230,6 +230,16 @@

Exporting a specific realm

+

Import File Naming Conventions

+
+
+

When you export a realm specific file name conventions are used, which must also be used for importing from a directory or import at startup. The realm file to be imported must be named <realm name>-realm.json. +Regular and federated user files associated with a realm must be named <realm-name>-users-<file number>.json and <realm-name>-federated-users-<file number>.json. Failure to use this convention will result in errors or +user files not being imported.

+
+
+
+

Importing a Realm from a Directory