mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 209. Kubernetes Service Account Component Available as of Camel version 2.17 The Kubernetes Service Account component is one of Kubernetes Components which provides a producer to execute kubernetes Service Account operations. 209.1. Component Options The Kubernetes Service Account component has no options. 209.2. Endpoint Options The Kubernetes Service Account endpoint is configured using URI syntax: with the following path and query parameters: 209.2.1. Path Parameters (1 parameters): Name Description Default Type masterUrl Required Kubernetes API server URL String 209.2.2. Query Parameters (20 parameters): Name Description Default Type apiVersion (producer) The Kubernetes API Version to use String dnsDomain (producer) The dns domain, used for ServiceCall EIP String kubernetesClient (producer) Default KubernetesClient to use if provided KubernetesClient operation (producer) Producer operation to do on Kubernetes String portName (producer) The port name, used for ServiceCall EIP String portProtocol (producer) The port protocol, used for ServiceCall EIP tcp String connectionTimeout (advanced) Connection timeout in milliseconds to use when making requests to the Kubernetes API server. Integer synchronous (advanced) Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). false boolean caCertData (security) The CA Cert Data String caCertFile (security) The CA Cert File String clientCertData (security) The Client Cert Data String clientCertFile (security) The Client Cert File String clientKeyAlgo (security) The Key Algorithm used by the client String clientKeyData (security) The Client Key data String clientKeyFile (security) The Client Key file String clientKeyPassphrase (security) The Client Key Passphrase String oauthToken (security) The Auth Token String password (security) Password to connect to Kubernetes String trustCerts (security) Define if the certs we used are trusted anyway or not Boolean username (security) Username to connect to Kubernetes String 209.3. Spring Boot Auto-Configuration The component supports 2 options, which are listed below. Name Description Default Type camel.component.kubernetes-service-accounts.enabled Whether to enable auto configuration of the kubernetes-service-accounts component. This is enabled by default. Boolean camel.component.kubernetes-service-accounts.resolve-property-placeholders Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. true Boolean

Commands:
kubernetes-service-accounts:masterUrl
5.5. Adding and Removing Tags to and from Objects You can assign tags to and remove tags from hosts, virtual machines, and users. Adding and Removing Tags to and from Objects Select the object(s) you want to tag or untag. Click More Actions ( ), then click Assign Tags . Select the check box to assign a tag to the object, or clear the check box to detach the tag from the object. Click OK . The specified tag is now added or removed as a custom property of the selected object(s).

Commands:
Chapter 56. Guided rule templates Guided rule templates are business rule structures with placeholder values (template keys) that are interchanged with actual values defined in separate data tables. Each row of values defined in the corresponding data table for that template results in a rule. Guided rule templates are ideal when many rules have the same conditions, actions, and other attributes but differ in values of facts or constraints. In such cases, instead of creating many similar guided rules and defining values in each rule, you can create a guided rule template with the rule structure that applies to each rule and then define only the differing values in the data table. The guided rule templates designer provides fields and options for acceptable template input based on the data objects for the rule template being defined, and a corresponding data table where you add template key values. After you create your guided rule template and add values in the corresponding data table, the rules you defined are compiled into Drools Rule Language (DRL) rules as with all other rule assets. All data objects related to a guided rule template must be in the same project package as the guided rule template. Assets in the same package are imported by default. After you create the necessary data objects and the guided rule template, you can use the Data Objects tab of the guided rule templates designer to verify that all required data objects are listed or to import other existing data objects by adding a New item .

Commands:
5.128. kabi-whitelists 5.128.1. RHEA-2012:0918 - kabi-whitelists enhancement update An updated kabi-whitelists package that adds various enhancements is now available for Red Hat Enterprise Linux 6. The kabi-whitelists package contains reference files documenting interfaces provided by the Red Hat Enterprise Linux 6 kernel that are considered to be stable by Red Hat engineering, and safe for longer term use by third-party loadable device drivers, as well as for other purposes. Enhancements BZ# 722619 Multiple symbols have been added to the Red Hat Enterprise Linux 6.3 kernel application binary interface (ABI) whitelists. BZ# 737276 Multiple symbols for Hitachi loadable device drivers have been added to the kernel ABI whitelists. BZ# 753771 This update modifies the structure of the kabi-whitelists package: whitelists are now ordered according to various Red Hat Enterprise Linux releases, and a symbolic link that points to the latest release has been added. BZ# 803885 The "__dec_zone_page_state" and "dec_zone_page_state" symbols have been added to the kernel ABI whitelists. BZ# 810456 The "blk_queue_rq_timed_out", "fc_attach_transport", "fc_release_transport", "fc_remote_port_add", "fc_remote_port_delete", "fc_remote_port_rolechg", "fc_remove_host", and "touch_nmi_watchdog" symbols have been added to the kernel ABI whitelists. BZ# 812463 Multiple symbols for Oracle Cloud File System have been added to the kernel ABI whitelists. BZ# 816533 The "get_fs_type" and "vscnprintf" have been added to the kernel ABI whitelists. All users of kabi-whitelists are advised to upgrade to this updated package, which adds these enhancements.

Commands:
Chapter 71. KafkaClientAuthenticationTls schema reference Used in: KafkaBridgeSpec , KafkaConnectSpec , KafkaMirrorMaker2ClusterSpec , KafkaMirrorMakerConsumerSpec , KafkaMirrorMakerProducerSpec Full list of KafkaClientAuthenticationTls schema properties To configure mTLS authentication, set the type property to the value tls . mTLS uses a TLS certificate to authenticate. 71.1. certificateAndKey The certificate is specified in the certificateAndKey property and is always loaded from an OpenShift secret. In the secret, the certificate must be stored in X509 format under two different keys: public and private. You can use the secrets created by the User Operator, or you can create your own TLS certificate file, with the keys used for authentication, then create a Secret from the file: oc create secret generic MY-SECRET \ --from-file= MY-PUBLIC-TLS-CERTIFICATE-FILE.crt \ --from-file= MY-PRIVATE.key Note mTLS authentication can only be used with TLS connections. Example mTLS configuration authentication: type: tls certificateAndKey: secretName: my-secret certificate: my-public-tls-certificate-file.crt key: private.key 71.2. KafkaClientAuthenticationTls schema properties The type property is a discriminator that distinguishes use of the KafkaClientAuthenticationTls type from KafkaClientAuthenticationScramSha256 , KafkaClientAuthenticationScramSha512 , KafkaClientAuthenticationPlain , KafkaClientAuthenticationOAuth . It must have the value tls for the type KafkaClientAuthenticationTls . Property Description certificateAndKey Reference to the Secret which holds the certificate and private key pair. CertAndKeySecretSource type Must be tls . string

Commands:
create secret generic MY-SECRET --from-file= MY-PUBLIC-TLS-CERTIFICATE-FILE.crt --from-file= MY-PRIVATE.key
authentication: type: tls certificateAndKey: secretName: my-secret certificate: my-public-tls-certificate-file.crt key: private.key
7.86. infinipath-psm 7.86.1. RHBA-2013:0536 - infinipath-psm bug fix update Updated infinipath-psm packages that fix one bug are now available for Red Hat Enterprise Linux 6. The PSM Messaging API, or PSM API, is Intel's (formerly QLogic's) low-level, user-level communication interface for the Truescale family of products. PSM users can use mechanisms necessary to implement higher-level communication interfaces in parallel environments. Bug Fix BZ# 907361 Due to a packaging error, not all object files required for the infinipath-psm library were built into the library, rendering it non-functional. This update fixes the infinipath-psm Makefile, which now properly includes all required object files, and the library works as expected. All users of infinipath-psm are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Logging 1.1. Viewing Argo CD logs You can view the Argo CD logs with the logging subsystem for Red Hat OpenShift. The logging subsystem visualizes the logs on a Kibana dashboard. The OpenShift Logging Operator enables logging with Argo CD by default. 1.1.1. Storing and retrieving Argo CD logs You can use the Kibana dashboard to store and retrieve Argo CD logs. Prerequisites The Red Hat OpenShift GitOps Operator is installed in your cluster. The logging subsystem for Red Hat OpenShift is installed with default configuration in your cluster. Procedure In the OpenShift Container Platform web console, go to the menu Observability Logging to view the Kibana dashboard. Create an index pattern. To display all the indices, define the index pattern as * , and click step . Select @timestamp for Time Filter field name . Click Create index pattern . In the navigation panel of the Kibana dashboard, click the Discover tab. Create a filter to retrieve logs for Argo CD. The following steps create a filter that retrieves logs for all the pods in the openshift-gitops namespace: Click Add a filter + . Select the kubernetes.namespace_name field. Select the is operator. Select the openshift-gitops value. Click Save . Optional: Add additional filters to narrow the search. For example, to retrieve logs for a particular pod, you can create another filter with kubernetes.pod_name as the field. View the filtered Argo CD logs in the Kibana dashboard. 1.1.2. Additional resources Installing the logging subsystem for Red Hat OpenShift using the web console

Commands:
Chapter 37. Networking Timeout policy not enabled in Red Hat Enterprise Linux 7.2 kernel The nfct timeout command is not supported in Red Hat Enterprise Linux 7.2. As a workaround, use the global timeout values available at /proc/sys/net/netfilter/nf_conntrack_*_timeout_* to set the timeout value. Verification of signatures using the MD5 hash algorithm is disabled in Red Hat Enterprise Linux 7 It is not possible to connect to any Wi-Fi Protected Access (WPA) Enterprise Access Point (AP) that requires MD5-signed certificates. To work around this problem, copy the wpa_supplicant.service file from the /usr/lib/systemd/system/ directory to the /etc/systemd/system/ directory and add the following line to the Service section of the file: Then run the systemctl daemon-reload command as root to reload the service file. Important Note that MD5 certificates are highly insecure and Red Hat does not recommend using them.

Commands:
Environment=OPENSSL_ENABLE_MD5_VERIFY=1
7.3. Using the Red Hat Support Tool in Interactive Shell Mode To start the tool in interactive mode, enter the following command: The tool can be run as an unprivileged user, with a consequently reduced set of commands, or as root . The commands can be listed by entering the ? character. The program or menu selection can be exited by entering the q or e character. You will be prompted for your Red Hat Customer Portal user name and password when you first search the Knowledgebase or support cases. Alternately, set the user name and password for your Red Hat Customer Portal account using interactive mode, and optionally save it to the configuration file.

Commands:
~]USD redhat-support-tool Welcome to the Red Hat Support Tool. Command (? for help):
Chapter 9. Red Hat Developer Hub data telemetry capturing Red Hat Developer Hub (RHDH) sends telemetry data to Red Hat using the backstage-plugin-analytics-provider-segment plug-in, which is enabled by default. This includes telemetry data from the Ansible plug-ins. Red Hat collects and analyzes the following data to improve your experience with Red Hat Developer Hub: Events of page visits and clicks on links or buttons. System-related information, for example, locale, timezone, user agent including browser and OS details. Page-related information, for example, title, category, extension name, URL, path, referrer, and search parameters. Anonymized IP addresses, recorded as 0.0.0.0. Anonymized username hashes, which are unique identifiers used solely to identify the number of unique users of the RHDH application. Feedback and sentiment provided in the Ansible plug-ins feedback form. With Red Hat Developer Hub, you can disable or customize the telemetry data collection feature. For more information, refer to the Telemetry data collection section of the Administration guide for Red Hat Developer Hub .

Commands:
2.11. Post-Installation Script Figure 2.16. Post-Installation Script You can also add commands to execute on the system after the installation is completed. If the network is properly configured in the kickstart file, the network is enabled, and the script can include commands to access resources on the network. To include a post-installation script, type it in the text area. Warning Do not include the %post command. It is added for you. For example, to change the message of the day for the newly installed system, add the following command to the %post section: Note More examples can be found in Section 1.7.1, "Examples" . 2.11.1. Chroot Environment To run the post-installation script outside of the chroot environment, click the checkbox to this option on the top of the Post-Installation window. This is equivalent to using the --nochroot option in the %post section. To make changes to the newly installed file system, within the post-installation section, but outside of the chroot environment, you must prepend the directory name with /mnt/sysimage/ . For example, if you select Run outside of the chroot environment , the example must be changed to the following:

Commands:
echo "Hackers will be punished!" > /etc/motd
echo "Hackers will be punished!" > /mnt/sysimage/etc/motd
5.5. Backend Settings The backend settings specify the real server IP addresses as well as the load balancer scheduling algorithm. The following example shows a typical backend section: The back-end server is named app . The balance specifies the load balancer scheduling algorithm to be used, which in this case is Round Robin ( roundrobin ), but can be any scheduler supported by HAProxy. For more information configuring schedulers in HAProxy, see Section 5.1, "HAProxy Scheduling Algorithms" . The server lines specify the servers available in the back end. app1 to app4 are the names assigned internally to each real server. Log files will specify server messages by name. The address is the assigned IP address. The value after the colon in the IP address is the port number to which the connection occurs on the particular server. The check option flags a server for periodic healthchecks to ensure that it is available and able receive and send data and take session requests. Server app3 also configures the healthcheck interval to two seconds ( inter 2s ), the amount of checks app3 has to pass to determine if the server is considered healthy ( rise 4 ), and the number of times a server consecutively fails a check before it is considered failed ( fall 3 ).

Commands:
backend app balance roundrobin server app1 192.168.1.1:80 check server app2 192.168.1.2:80 check server app3 192.168.1.3:80 check inter 2s rise 4 fall 3 server app4 192.168.1.4:80 backup
Preface Red Hat Quay is an enterprise-quality container registry. Use Red Hat Quay to build and store container images, then make them available to deploy across your enterprise. The Red Hat Quay Operator provides a simple method to deploy and manage Red Hat Quay on an OpenShift cluster. With the release of Red Hat Quay 3.4.0, the Red Hat Quay Operator was re-written to offer an enhanced experience and to add more support for Day 2 operations. As a result, the Red Hat Quay Operator is now simpler to use and is more opinionated. The key difference from versions prior to Red Hat Quay 3.4.0 include the following: The QuayEcosystem custom resource has been replaced with the QuayRegistry custom resource. The default installation options produces a fully supported Red Hat Quay environment, with all managed dependencies (database, caches, object storage, and so on) supported for production use. Note Some components might not be highly available. A new validation library for Red Hat Quay's configuration, which is shared by the Red Hat Quay application and config tool for consistency. Object storage can now be managed by the Red Hat Quay Operator using the ObjectBucketClaim Kubernetes API Note Red Hat OpenShift Data Foundation can be used to provide a supported implementation of this API on OpenShift Container Platform. Customization of the container images used by deployed pods for testing and development scenarios.

Commands:
7.2. Displaying Information on Failed Devices You can use the -P argument of the lvs or vgs command to display information about a failed volume that would otherwise not appear in the output. This argument permits some operations even though the metadata is not completely consistent internally. For example, if one of the devices that made up the volume group vg failed, the vgs command might show the following output. If you specify the -P argument of the vgs command, the volume group is still unusable but you can see more information about the failed device. In this example, the failed device caused both a linear and a striped logical volume in the volume group to fail. The lvs command without the -P argument shows the following output. Using the -P argument shows the logical volumes that have failed. The following examples show the output of the pvs and lvs commands with the -P argument specified when a leg of a mirrored logical volume has failed.

Commands:
vgs -o +devices Volume group "vg" not found
vgs -P -o +devices Partial mode. Incomplete volume groups will be activated read-only. VG #PV #LV #SN Attr VSize VFree Devices vg 9 2 0 rz-pn- 2.11T 2.07T unknown device(0) vg 9 2 0 rz-pn- 2.11T 2.07T unknown device(5120),/dev/sda1(0)
lvs -a -o +devices Volume group "vg" not found
lvs -P -a -o +devices Partial mode. Incomplete volume groups will be activated read-only. LV VG Attr LSize Origin Snap% Move Log Copy% Devices linear vg -wi-a- 20.00G unknown device(0) stripe vg -wi-a- 20.00G unknown device(5120),/dev/sda1(0)
vgs -a -o +devices -P Partial mode. Incomplete volume groups will be activated read-only. VG #PV #LV #SN Attr VSize VFree Devices corey 4 4 0 rz-pnc 1.58T 1.34T my_mirror_mimage_0(0),my_mirror_mimage_1(0) corey 4 4 0 rz-pnc 1.58T 1.34T /dev/sdd1(0) corey 4 4 0 rz-pnc 1.58T 1.34T unknown device(0) corey 4 4 0 rz-pnc 1.58T 1.34T /dev/sdb1(0)
lvs -a -o +devices -P Partial mode. Incomplete volume groups will be activated read-only. LV VG Attr LSize Origin Snap% Move Log Copy% Devices my_mirror corey mwi-a- 120.00G my_mirror_mlog 1.95 my_mirror_mimage_0(0),my_mirror_mimage_1(0) [my_mirror_mimage_0] corey iwi-ao 120.00G unknown device(0) [my_mirror_mimage_1] corey iwi-ao 120.00G /dev/sdb1(0) [my_mirror_mlog] corey lwi-ao 4.00M /dev/sdd1(0)
Chapter 3. Configuring Red Hat build of OpenJDK to run with customized heap size Red Hat build of OpenJDK 11 for Microsoft Windows can be configured to use a customized heap size. Prequisites Installed Java Runtime Procedure Run the application by adding maximum heap size option to your java command line. For example to set the maximum heap size to 100 megabytes use the -Xmx100m option. Additional resources For reference see https://docs.oracle.com/javase/8/docs/technotes/tools/windows/java.html#BABDJJFI Revised on 2024-05-09 16:46:07 UTC

Commands:
java -Xmx100m <your-main-class>
5.4. Specifying Transaction Batching To improve the update performance when a full transaction durability is not required, use the following command: The --txn-batch-val specifies how many transactions be batched before Directory Server commits them to the transaction log. Setting this value to a value greater than 0 causes the server to delay committing transactions until the number of queued transactions is equal to this value.

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com backend config set --txn-batch-val= value
14.4. Adding Caching to Application Code Caching can be added to each application by utilizing the Spring annotations found in the Spring Cache Abstraction . Adding a Cache Entry To add entries to the cache add the @Cacheable annotation to select methods. This annotation will add any returned values to the indicated cache. For instance, consider a method that returns a Book based on a particular key. By annotating this method with @Cacheable : Any Book instances returned from findBook(Integer bookId) will be placed in a named cache books , using the bookId as the value's key. Important If the key attribute is not specified then Spring will generate a hash from the supplied arguments and use this generated value as the cache key. If your application needs to reference the entries directly it is recommended to include the key attribute so that entries may be easily obtained. Deleting a Cache Entry To remove entries from the cache annotate the desired methods with @CacheEvict . This annotation can be configured to evict all entries in a cache, or to only affect entries with the indicated key. Consider the following examples: Report a bug

Commands:
@Cacheable(value = "books", key = "#bookId") public Book findBook(Integer bookId) {...}
// Evict all entries in the "books" cache @CacheEvict (value="books", key = "#bookId", allEntries = true) public void deleteBookAllEntries() {...} // Evict any entries in the "books" cache that match the passed in bookId @CacheEvict (value="books", key = "#bookId") public void deleteBook(Integer bookId) {...]}
15.6. Additional Resources For more information about vsftpd , refer to the following resources. 15.6.1. Installed Documentation The /usr/share/doc/vsftpd- <version-number> / directory - Replace <version-number> with the installed version of the vsftpd package. This directory contains a README with basic information about the software. The TUNING file contains basic performance tuning tips and the SECURITY/ directory contains information about the security model employed by vsftpd . vsftpd related man pages - There are a number of man pages for the daemon and configuration files. The following lists some of the more important man pages. Server Applications man vsftpd - Describes available command line options for vsftpd . Configuration Files man vsftpd.conf - Contains a detailed list of options available within the configuration file for vsftpd . man 5 hosts_access - Describes the format and options available within the TCP wrappers configuration files: hosts.allow and hosts.deny .

Commands: