Merge branch 'main' into HACDOCS-975-jfrog-artifactory-plugin

Author: otikhomi

artifacts/attributes.adoc

@@ -35,6 +35,8 @@
 :openshift-cli: pass:quotes[OpenShift CLI (`oc`)]
 :rhsso-brand-name: Red Hat Single-Sign On
 :rhsso: RHSSO
+:rhbk-brand-name: Red Hat Build of Keycloak
+:rhbk: RHBK
 
 // Partner Platforms
 :aws-brand-name: Amazon Web Services

artifacts/rhdh-plugins-reference/keycloak/keycloak-plugin-admin.adoc

@@ -6,17 +6,22 @@ The Keycloak backend plugin, which integrates Keycloak into {product-short}, has
 * Synchronization of Keycloak users in a realm.
 * Synchronization of Keycloak groups and their users in a realm.
 
+[NOTE]
+====
+The supported Keycloak version is `18.x`.
+====
+
 == Installation
 
 The Keycloak plugin is pre-loaded in {product-short} with basic configuration properties. To enable it, set the `disabled` property to `false` as follows:
 
 [source,yaml]
 ----
-global: 
-  dynamic: 
-    includes: 
+global:
+  dynamic:
+    includes:
       - dynamic-plugins.default.yaml
-    plugins: 
+    plugins:
       - package: ./dynamic-plugins/dist/janus-idp-backstage-plugin-keycloak-backend-dynamic
         disabled: false
 ----
@@ -87,7 +92,7 @@ The following table describes the parameters that you can configure to enable th
 | Name | Description | Default Value | Required
 
 | `baseUrl`
-| Location of the Keycloak server, such as `pass:c[https://localhost:8443/auth]`. Note that the newer versions of Keycloak omit the `/auth` context path.
+| Location of the Keycloak server, such as `pass:c[https://localhost:8443/auth]`.
 | ""
 | Yes
 

assemblies/assembly-audit-log.adoc

@@ -44,5 +44,3 @@ include::modules/observe/ref-audit-log-fields.adoc[leveloffset=+2]
 include::modules/observe/ref-audit-log-scaffolder-events.adoc[leveloffset=+2]
 
 include::modules/observe/ref-audit-log-catalog-events.adoc[leveloffset=+2]
-
-include::modules/observe/ref-audit-log-file-rotation-overview.adoc[]

assemblies/assembly-authenticating-with-rhbk.adoc

@@ -0,0 +1,18 @@
+[id="assembly-authenticating-with-rhbk"]
+= Authenticating with {rhbk-brand-name} ({rhbk})
+
+[NOTE]
+====
+{rhsso} 7.6 is deprecated as an authentication provider. You can continue using {rhsso} until the end of its maintenance support. For more information, see link:https://access.redhat.com/support/policy/updates/jboss_notes#p_sso[{rhsso} lifecycle dates]. As an alternative, consider migrating to {rhbk-brand-name} ({rhbk}).
+====
+
+To authenticate users with {rhbk-brand-name} ({rhbk}):
+
+. xref:enabling-authentication-with-rhbk[Enable the OpenID Connect (OIDC) authentication provider in RHDH].
+. xref:provisioning-users-from-rhbk-to-the-software-catalog[Provision users from {rhbk-brand-name} ({rhbk}) to the software catalog].
+
+include::modules/authentication/proc-enabling-authentication-with-rhbk.adoc[leveloffset=+1]
+
+include::modules/authentication/proc-provisioning-users-from-rhbk-to-the-software-catalog.adoc[leveloffset=+1]
+
+include::modules/authentication/proc-creating-a-custom-transformer-to-provision-users-from-rhbk-to-the-software-catalog.adoc[leveloffset=+1]

assemblies/assembly-authenticating-with-rhsso.adoc

@@ -53,7 +53,7 @@ Therefore, deleting users and groups by using {product-short} Web UI or REST API
 include::assembly-authenticating-with-the-guest-user.adoc[leveloffset=+1]
 
 
-include::assembly-authenticating-with-rhsso.adoc[leveloffset=+1]
+include::assembly-authenticating-with-rhbk.adoc[leveloffset=+1]
 
 
 include::assembly-authenticating-with-github.adoc[leveloffset=+1]

assemblies/assembly-enabling-authentication.adoc

@@ -0,0 +1,15 @@
+[id="assembly-monitoring-and-logging-aks"]
+= Monitoring and logging with Azure Kubernetes Services (AKS) in {product}
+:context: assembly-monitoring-and-logging-aks
+
+Monitoring and logging are integral aspects of managing and maintaining Azure Kubernetes Services (AKS) in {product}. With features like Managed Prometheus Monitoring and Azure Monitor integration, administrators can efficiently monitor resource utilization, diagnose issues, and ensure the reliability of their containerized workloads.
+
+// Azure monitor metrics
+include::modules/observe/proc-enabling-azure-monitor-metrics.adoc[leveloffset=+1]
+
+// configure annotations
+include::modules/observe/proc-configure-annotations-for-aks-monitoring.adoc[leveloffset=+1]
+
+// view logs
+include::modules/observe/proc-view-logs-aks.adoc[leveloffset=+1]
+

assemblies/assembly-monitoring-and-logging-aks.adoc

@@ -0,0 +1,64 @@
+[id="proc-mount-directories-pvcs_{context}"]
+= Mounting directories from pre-created PVCs
+
+Starting from `v1alpha3`, you can mount directories from pre-created PersistentVolumeClaims (PVCs) using the `spec.application.extraFiles.pvcs` field.
+
+.Prerequisites
+* You have understanding of the mounting logic:
+** If `spec.application.extraFiles.pvcs[].mountPath` is defined, the PVC is mounted to the specified path.
+** If `spec.application.extraFiles.pvcs[].mountPath` is not defined, the PVC is mounted under the path specified in `spec.application.extraFiles.mountPath/`.
+** If `mountPath` is not defined, the PVC defaults to `/opt/app-root/src`, or you can use the {product-very-short} container's working directory if it is specified.
+
+.Procedure
+. Define the PVCs using the following YAML example:
++
+--
+.Example YAML file to define PVCs
+[source,yaml]
+----
+apiVersion: v1  
+kind: PersistentVolumeClaim  
+metadata:  
+  name: myclaim1  
+spec:  
+  accessModes:  
+    - ReadWriteOnce  
+  resources:  
+    requests:  
+      storage: 2Gi  
+---  
+apiVersion: v1  
+kind: PersistentVolumeClaim  
+metadata:  
+  name: myclaim2  
+spec:  
+  accessModes:  
+    - ReadWriteOnce  
+  resources:  
+    requests:  
+      storage: 2Gi 
+----
+--
+
+. Use the following configuration to specify how the PVCs are mounted in the container:
++
+--
+.Example configuration for mounting PVCs in a container
+[source,yaml]
+----
+spec:  
+  application:  
+    extraFiles:  
+      mountPath: /my/path  
+      pvcs:  
+        - name: myclaim1  
+        - name: myclaim2  
+          mountPath: /vol/my/claim
+----
+--
+
+.Verification
+Based on the configuration, the following directories are mounted in the container:
+
+* `/my/path/myclaim1`
+* `/vol/my/claim`

modules/admin/proc-mount-directories-pvcs.adoc

@@ -46,8 +46,10 @@ spec:
 ----
 
 `volumes`::
-Add an additional volume named `my-volume` and mount it under `/my/path` in the {product-short} application container.
 +
+--
+Add an additional volume named `my-volume` and mount it under `/my/path` in the {product-short} application container.
+
 .Example additional volume
 [source, yaml]
 ----
@@ -73,9 +75,9 @@ spec:
                       storageClassName: "special"
                 name: my-volume
 ----
-+
+
 Replace the default `dynamic-plugins-root` volume with a persistent volume claim (PVC) named `dynamic-plugins-root`. Note the `$patch: replace` directive, otherwise a new volume will be added.
-+
+
 .Example `dynamic-plugins-root` volume replacement
 [source, yaml]
 ----
@@ -95,6 +97,7 @@ spec:
                 persistentVolumeClaim:
                   claimName: dynamic-plugins-root
 ----
+--
 
 `cpu` request::
 

modules/admin/proc-rhdh-deployment-config.adoc

@@ -1,10 +1,10 @@
-[id="creating-a-custom-transformer-to-provision-users-from-rhsso-to-the-software-catalog"]
-= Creating a custom transformer to provision users from {rhsso-brand-name} ({rhsso}) to the software catalog
+[id="creating-a-custom-transformer-to-provision-users-from-rhbk-to-the-software-catalog"]
+= Creating a custom transformer to provision users from {rhbk-brand-name} ({rhbk}) to the software catalog
 
-To customize how {rhsso} users and groups are mapped to {product} entities, you can create a backend module that uses the `keycloakTransformerExtensionPoint` to provide custom user and group transformers for the Keycloak backend.
+To customize how {rhbk} users and groups are mapped to {product} entities, you can create a backend module that uses the `keycloakTransformerExtensionPoint` to provide custom user and group transformers for the Keycloak backend.
 
 .Prerequisites
-* You have xref:provisioning-users-from-rhsso-to-the-software-catalog[enabled provisioning users from {rhsso-brand-name} ({rhsso}) to the software catalog].
+* You have xref:provisioning-users-from-rhbk-to-the-software-catalog[enabled provisioning users from {rhbk-brand-name} ({rhbk}) to the software catalog].
 
 .Procedure
 . Create a new backend module with the `yarn new` command.
@@ -85,8 +85,8 @@ Check the console logs to verify that the synchronization is completed.
 
 * After the first import is complete, navigate to the *Catalog* page and select **User** to view the list of users.
 
-* When you select a user, you see the information imported from {rhsso}.
+* When you select a user, you see the information imported from {rhbk}.
 
-* You can select a group, view the list, and access or review the information imported from {rhsso}.
+* You can select a group, view the list, and access or review the information imported from {rhbk}.
 
-* You can log in with an {rhsso} account.
+* You can log in with an {rhbk} account.