mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Red Hat build of Keycloak Operator installation Use this procedure to install the Red Hat build of Keycloak Operator in an OpenShift cluster. Open the OpenShift Container Platform web console. In the left column, click Home , Operators , OperatorHub . Search for "Keycloak" on the search input box. Select the Operator from the list of results. Follow the instructions on the screen. For general instructions on installing Operators by using either the CLI or web console, see Installing Operators in your namespace . In the default Catalog, the Operator is named rhbk-operator . Make sure to use the channel corresponding with your desired Red Hat build of Keycloak version. 1.1. Installing Multiple Operators It is not fully supported for the operator to watch multiple or all namespaces. To watch multiple namespaces, you install multiple operators. In this situation, consider the following: All Operators share the Custom Resource Definitions (CRDs) as they are installed cluster wide. CRD revisions from newer Operator versions will not introduce breaking changes except for the eventual removal of fields that have been deprecated for some time. Thus newer CRDs are generally backward compatible. The last installed CRDs become the ones that are used. This rule also applies to OLM installations; the last installed Operator version also installs and overrides the CRDs if they already exist in the cluster. Older CRDs may not be forward compatible with new fields used by newer operators. When using OLM it will check if your custom resources are compatible with the CRDs being installed, so the usage of new fields can prevent the simultaneous installation of older operator versions. Fields introduced by newer CRDs are not supported by older Operators. Older Operators fail to handle CRs that use such new fields with a deserialization error for an unrecognized field. Therefore, in a multiple Operator installation scenario, the recommended approach is to keep versions aligned as closely as possible to minimize the potential problems with different versions.

Commands:
18. Databases 18.1. PostgreSQL PostgreSQL is an advanced Object-Relational database management system (DBMS). The postgresql packages include the client programs and libraries needed to access a PostgreSQL DBMS server. Red Hat Enterprise Linux 6 features version 8.4 of PostgreSQL 18.2. MySQL MySQL is a multi-user, multi-threaded SQL database server. It consists of the MySQL server daemon (mysqld) and many client programs and libraries. This release features version 5.1 of MySQL. For a list of all enhancements that this version provides, refer to the MySQL Release Notes

Commands:
5.6.3.2. Logical Volume Resizing The feature that most system administrators appreciate about LVM is its ability to easily direct storage where it is needed. In a non-LVM system configuration, running out of space means -- at best -- moving files from the full device to one with available space. Often it can mean actual reconfiguration of your system's mass storage devices; a task that would have to take place after normal business hours. However, LVM makes it possible to easily increase the size of a logical volume. Assume for a moment that our 200GB storage pool was used to create a 150GB logical volume, with the remaining 50GB held in reserve. If the 150GB logical volume became full, LVM makes it possible to increase its size (say, by 10GB) without any physical reconfiguration. Depending on the operating system environment, it may be possible to do this dynamically or it might require a short amount of downtime to actually perform the resizing.

Commands:
Chapter 2. Disaster recovery subscription requirement Disaster Recovery features supported by Red Hat OpenShift Data Foundation require all of the following prerequisites to successfully implement a disaster recovery solution: A valid Red Hat OpenShift Data Foundation Advanced entitlement A valid Red Hat Advanced Cluster Management for Kubernetes subscription Any Red Hat OpenShift Data Foundation Cluster containing PVs participating in active replication either as a source or destination requires OpenShift Data Foundation Advanced entitlement. This subscription should be active on both source and destination clusters. To know how subscriptions for OpenShift Data Foundation work, see knowledgebase article on OpenShift Data Foundation subscriptions . Important OpenShift Data Foundation deployed with Multus networking is not supported for Regional Disaster Recovery (Regional-DR) setups.

Commands:
Chapter 8. Configuring authentication Application users need credentials to access Data Grid clusters. You can use default, generated credentials or add your own. 8.1. Default credentials Data Grid Operator generates base64-encoded credentials for the following users: User Secret name Description developer infinispan-generated-secret Credentials for the default application user. operator infinispan-generated-operator-secret Credentials that Data Grid Operator uses to interact with Data Grid resources. 8.2. Retrieving credentials Get credentials from authentication secrets to access Data Grid clusters. Procedure Retrieve credentials from authentication secrets. Base64-decode credentials. 8.3. Adding custom user credentials Configure access to Data Grid cluster endpoints with custom credentials. Note Modifying spec.security.endpointSecretName triggers a cluster restart. Procedure Create an identities.yaml file with the credentials that you want to add. credentials: - username: myfirstusername password: changeme-one - username: mysecondusername password: changeme-two Create an authentication secret from identities.yaml . Specify the authentication secret with spec.security.endpointSecretName in your Infinispan CR and then apply the changes. 8.4. Changing the operator password You can change the password for the operator user if you do not want to use the automatically generated password. Procedure Update the password key in the infinispan-generated-operator-secret secret as follows: Note You should update only the password key in the generated-operator-secret secret. When you update the password, Data Grid Operator automatically refreshes other keys in that secret. 8.5. Disabling user authentication Allow users to access Data Grid clusters and manipulate data without providing credentials. Important Do not disable authentication if endpoints are accessible from outside the OpenShift cluster via spec.expose.type . You should disable authentication for development environments only. Procedure Set false as the value for the spec.security.endpointAuthentication field in your Infinispan CR. Apply the changes.

Commands:
get secret infinispan-generated-secret
get secret infinispan-generated-secret -o jsonpath="{.data.identities\.yaml}" | base64 --decode
credentials: - username: myfirstusername password: changeme-one - username: mysecondusername password: changeme-two
create secret generic --from-file=identities.yaml connect-secret
spec: security: endpointSecretName: connect-secret
patch secret infinispan-generated-operator-secret -p='{"stringData":{"password": "supersecretoperatorpassword"}}'
spec: security: endpointAuthentication: false
Chapter 21. Troubleshooting: Correcting problems with filtering The subscriptions service includes several filters that you can use to sort data by different characteristics. These characteristics include subscription attributes, also known as system purpose or subscription settings, depending on the product. Types of subscription attributes include service level agreement (SLA), usage, and others. Subscription attributes values must be set on systems to enable filtering by those values on the product-level pages in the the subscriptions service interface. There are different methods to set these values, such as directly in the product or in one of the subscription management tools. Subscription attributes values should be set by only one method to avoid the potential for mismatched values. In the older entitlement-based subscription model, the system purpose values are used by the subscription management tools such as Red Hat Satellite or Red Hat Subscription Management to help match subscriptions with systems. If a system is correctly matched with a subscription, the system status value ( System Status Details or System Purpose Status in the various tools) shows as Matched . However, if you are using simple content access with the subscriptions service, that usage of system purpose is obsolete, because subscriptions are not attached to systems. After you enable simple content access, the system status shows as Disabled . Note The Disabled state for the system status means that per-system subscription attachment is not being enforced. It does not mean that system purpose values themselves are unimportant. The subscriptions service filters related to system purpose values will not show reliable data if these values are not set for all systems. Procedure If the filters that relate to subscription attributes (system purpose values) are showing unexpected results, you might be able to improve the accuracy of that data by ensuring that the subscription attributes are set correctly: Review system information in your preferred subscription management tool to detect whether there are systems where the subscription attributes are missing. If there are missing values for subscription attributes, set those values. You might be able to use options to set these values in bulk, depending on the type and version of subscription management tool that you are using. Additional resources For more information about how to set system purpose values in bulk in Red Hat Satellite, see the section about editing system purpose for multiple hosts in the Managing Hosts guide. For more information about how to use Ansible and the subscription-manager command to set system purpose values in bulk for Red Hat Subscription Management, see the redhat-subscription module information.

Commands:
5.12. Troubleshooting with the multipathd Interactive Console The multipathd -k command is an interactive interface to the multipathd daemon. Entering this command brings up an interactive multipath console. After executing this command, you can enter help to get a list of available commands, you can enter a interactive command, or you can enter CTRL-D to quit. The multipathd interactive console can be used to troubleshoot problems you may be having with your system. For example, the following command sequence displays the multipath configuration, including the defaults, before exiting the console. The following command sequence ensures that multipath has picked up any changes to the multipath.conf , Use the following command sequence to ensure that the path checker is working properly.

Commands:
multipathd -k > > show config > > CTRL-D
multipathd -k > > reconfigure > > CTRL-D
multipathd -k > > show paths > > CTRL-D
B.32.3. RHSA-2010:0987 - Critical: java-1.6.0-ibm security and bug fix update Updated java-1.6.0-ibm packages that fix several security issues and two bugs are now available for Red Hat Enterprise Linux 4 Extras, and Red Hat Enterprise Linux 5 and 6 Supplementary. The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The IBM 1.6.0 Java release includes the IBM Java 2 Runtime Environment and the IBM Java 2 Software Development Kit. CVE-2009-3555 , CVE-2010-1321 , CVE-2010-3541 , CVE-2010-3548 , CVE-2010-3549 , CVE-2010-3550 , CVE-2010-3551 , CVE-2010-3553 , CVE-2010-3555 , CVE-2010-3556 , CVE-2010-3557 , CVE-2010-3558 , CVE-2010-3560 , CVE-2010-3562 , CVE-2010-3563 , CVE-2010-3565 , CVE-2010-3566 , CVE-2010-3568 , CVE-2010-3569 , CVE-2010-3571 , CVE-2010-3572 , CVE-2010-3573 , CVE-2010-3574 This update fixes several vulnerabilities in the IBM Java 2 Runtime Environment. Detailed vulnerability descriptions are linked from the IBM "Security alerts" page. Bug Fixes BZ# 659716 An error in the java-1.6.0-ibm RPM spec file caused an incorrect path to be included in HtmlConverter, preventing it from running. BZ# 633341 On AMD64 and Intel 64 systems, if only the 64-bit java-1.6.0-ibm packages were installed, IBM Java 6 Web Start was not available as an application that could open JNLP (Java Network Launching Protocol) files. This affected file management and web browser tools. Users had to manually open them with the "/usr/lib/jvm/jre-1.6.0-ibm.x86_64/bin/javaws" command. This update resolves this issue. All users of java-1.6.0-ibm are advised to upgrade to these updated packages, containing the IBM 1.6.0 SR9 Java release. All running instances of IBM Java must be restarted for the update to take effect.

Commands:
3.2. Feature Compatibility Support Red Hat Gluster Storage supports a number of features. Most features are supported with other features, but there are some exceptions. This section clearly identifies which features are supported and compatible with other features to help you in planning your Red Hat Gluster Storage deployment. Note Internet Protocol Version 6 (IPv6) support is available only for Red Hat Hyperconverged Infrastructure for Virtualization environments and not for Red Hat Gluster Storage standalone environments. Features in the following table are supported from the specified version and later. Table 3.3. Features supported by Red Hat Gluster Storage version Feature Version Arbiter bricks 3.2 Bitrot detection 3.1 Erasure coding 3.1 Google Compute Engine 3.1.3 Metadata caching 3.2 Microsoft Azure 3.1.3 NFS version 4 3.1 SELinux 3.1 Sharding 3.2.0 Snapshots 3.0 Snapshots, cloning 3.1.3 Snapshots, user-serviceable 3.0.3 Tiering (Deprecated) 3.1.2 Volume Shadow Copy (VSS) 3.1.3 Table 3.4. Features supported by volume type Volume Type Sharding Tiering (Deprecated) Quota Snapshots Geo-Rep Bitrot Arbitrated-Replicated Yes No Yes Yes Yes Yes Distributed No Yes Yes Yes Yes Yes Distributed-Dispersed No Yes Yes Yes Yes Yes Distributed-Replicated Yes Yes Yes Yes Yes Yes Replicated Yes Yes Yes Yes Yes Yes Sharded N/A No No No Yes No Tiered (Deprecated) No N/A Limited [a] Limited [a] Limited [a] Limited [a] [a] See Tiering Limitations in the Red Hat Gluster Storage 3.5 Administration Guide for details. Table 3.5. Features supported by client protocol Feature FUSE Gluster-NFS NFS-Ganesha SMB Arbiter Yes Yes Yes Yes Bitrot detection Yes Yes No Yes dm-cache Yes Yes Yes Yes Encryption (TLS-SSL) Yes Yes Yes Yes Erasure coding Yes Yes Yes Yes Export subdirectory Yes Yes Yes N/A Geo-replication Yes Yes Yes Yes Quota (Deprecated) Warning Using QUOTA feature is considered to be deprecated in Red Hat Gluster Storage 3.5.3. Red Hat no longer recommends to use this feature and does not support it on new deployments and existing deployments that upgrade to Red Hat Gluster Storage 3.5.3. See Chapter 9, Managing Directory Quotas for more details. Yes Yes Yes Yes RDMA (Deprecated) Warning Using RDMA as a transport protocol is considered deprecated in Red Hat Gluster Storage 3.5. Red Hat no longer recommends its use, and does not support it on new deployments and existing deployments that upgrade to Red Hat Gluster Storage 3.5.3. Yes No No No Snapshots Yes Yes Yes Yes Snapshot cloning Yes Yes Yes Yes Tiering (Deprecated) Warning Tiering is considered deprecated as of Red Hat Gluster Storage 3.5. Red Hat no longer recommends its use, and does not support tiering in new deployments and existing deployments that upgrade to Red Hat Gluster Storage 3.5.3. Yes Yes N/A N/A

Commands:
Preface Deploying applications to a container orchestration platform such as Red Hat OpenShift Container Platform provides a number of advantages from an operational perspective. For example, an update to the base image of an application can be made through a simple in-place upgrade with little to no disruption. Upgrading the required operating system of an application deployed to traditional virtual machines can be a much more disruptive and risky process. Although application and operator developers can provide many options to OpenShift Container Platform users regarding the deployment of the application, these configurations must be provided by the end user because they are dependent on the configuration of OpenShift Container Platform. For example, use of node labels in the Openshift cluster can help ensure different workloads are run on specific nodes. This type of configuration must be provided by the user as the Ansible Automation Platform Operator has no way of inferring this.

Commands:
Chapter 22. Importing projects from Git repositories Git is a distributed version control system. It implements revisions as commit objects. When you save your changes to a repository, a new commit object in the Git repository is created. Business Central uses Git to store project data, including assets such as rules and processes. When you create a project in Business Central, it is added to a Git repository that is embedded in Business Central. If you have projects in other Git repositories, you can import those projects into the Business Central Git repository through Business Central spaces. Prerequisites Red Hat Process Automation Manager projects exist in an external Git repository. You have the credentials required for read access to that external Git repository. Procedure In Business Central, click Menu Design Projects . Select or create the space into which you want to import the projects. The default space is MySpace . To import a project, do one of the following: Click Import Project . Select Import Project from the drop-down list. In the Import Project window, enter the URL and credentials for the Git repository that contains the projects that you want to import and click Import . The projects are added to the Business Central Git repository and are available from the current space.

Commands:
3.3. Install the Maven Repository There are three ways to install the required repositories: On your local file system ( Section 3.3.1, "Local File System Repository Installation" ). On Apache Web Server. With a Maven repository manager ( Section 3.3.2, "Maven Repository Manager Installation" ). Use the option that best suits your environment. Report a bug 3.3.1. Local File System Repository Installation This option is best suited for initial testing in a small team. Follow the outlined procedure to extract the Red Hat JBoss Data Grid and JBoss Enterprise Application Platform Maven repositories to a directory in your local file system: Procedure 3.1. Local File System Repository Installation (JBoss Data Grid) Log Into the Customer Portal In a browser window, navigate to the Customer Portal page ( https://access.redhat.com/home ) and log in. Download the JBoss Data Grid Repository File Download the jboss-datagrid- {VERSION} -maven-repository.zip file from the Red Hat Customer Portal. Unzip the file to a directory on your local file system (for example USDJDG_HOME/projects/maven-repositories/ ). Report a bug 3.3.2. Maven Repository Manager Installation This option is ideal if you are already using a repository manager. The Red Hat JBoss Data Grid and JBoss Enterprise Application Server repositories are installed using a Maven repository manager using its documentation. Examples of such repository managers are: Apache Archiva: http://archiva.apache.org/ JFrog Artifactory: http://www.jfrog.com/products.php Sonatype Nexus: http://nexus.sonatype.org/ For details, see Section B.1, "Install the JBoss Enterprise Application Platform Repository Using Nexus" . Report a bug

Commands:
B.16. dhcp B.16.1. RHSA-2010:0923 - Moderate: dhcp security update Updated dhcp packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The Dynamic Host Configuration Protocol (DHCP) is a protocol that allows individual devices on an IP network to get their own network configuration information, including an IP address, a subnet mask, and a broadcast address. DHCPv6 is the DHCP protocol version for IPv6 networks. CVE-2010-3611 A NULL pointer dereference flaw was discovered in the way the dhcpd daemon parsed DHCPv6 packets. A remote attacker could use this flaw to crash dhcpd via a specially-crafted DHCPv6 packet, if dhcpd was running as a DHCPv6 server. Users running dhcpd as a DHCPv6 server should upgrade to these updated packages, which contain a backported patch to correct this issue. After installing this update, all DHCP servers will be restarted automatically.

Commands:
Chapter 5. Setting up the test environment To certify your product, you must first set up the environment where you can run the tests. The test environment consists of a host system. A test host is a workstation used as a medium for accessing the OpenShift cluster. Note Red Hat recommends partners to enable FIPS mode on both control plane and data plane nodes. Additional resources For more information about RHOSO deployment, see RHOSO Deployment Guide . For more information about enabling FIPS, see Installing a cluster in FIPS node . 5.1. Setting up the test host You can use the test host to start a test run on the OpenShift cluster, display the progress of the tests, and present the final result file after gathering results. Prerequisites Install or use an existing RHEL 9 system. Have access to an OpenShift cluster hosting a RHOSO control plane. Procedure Use your RHN credentials to register your system by using Red Hat Subscription Management. Display the list of available subscriptions for your system. Search for the subscription that provides the Red Hat Certification (for RHEL Server) repository. Note the subscription and its Pool ID. Attach the subscription to your system. Note You don't have to attach the subscription to your system, if you enable the option Simple content access for Red Hat Subscription Management . Replace the pool_ID with the Pool ID of the subscription. Subscribe to the Red Hat Certification channel. Install the certification RPMs. Additional resources For more information about enabling Simple content access for Red Hat Subscription Management, see How do I enable Simple Content Access for Red Hat Subscription Management?

Commands:
subscription-manager register
subscription-manager list --available*
subscription-manager attach --pool=<pool_ID>
subscription-manager repos --enable=cert-1-for-rhel-9-x86_64-rpms
dnf install redhat-certification dnf install redhat-certification-rhoso
Chapter 12. Converting a connected cluster to a disconnected cluster There might be some scenarios where you need to convert your OpenShift Container Platform cluster from a connected cluster to a disconnected cluster. A disconnected cluster, also known as a restricted cluster, does not have an active connection to the internet. As such, you must mirror the contents of your registries and installation media. You can create this mirror registry on a host that can access both the internet and your closed network, or copy images to a device that you can move across network boundaries. For information on how to convert your cluster, see the Converting a connected cluster to a disconnected cluster procedure in the Disconnected environments section.

Commands: