RHUI 5 Technology Preview Release Notes

Updated

Red Hat Update Infrastructure (RHUI) 5.2 Technology Preview: CDS on Kubernetes

Technology Preview Notice: RHUI 5.2 support for CDS on Kubernetes is released as a Technology Preview. While we encourage testing and feedback, please be advised that this feature is not supported for production use and is subject to change based on user feedback and technical requirements.

This Technology Preview (TP) introduces support for deploying Content Delivery Servers (CDS) on Kubernetes. The preview is delivered via specific container images identified by a unique suffix.

Available Images

The following images are provided for this Technology Preview:

  • Installer: rhui5/installer-tp-rhel9
  • RHUA: rhui5/rhua-tp-rhel9
  • CDS (Kubernetes): rhui5/cds-kubernetes-tp-rhel9 (Utilized by default during the TP installation process).

Installation Procedure

The installation workflow remains consistent with standard RHUI 5 procedures. To deploy the Technology Preview, execute the installer using the TP image names. Providing these specific image names will override the default production image versions.

Prerequisites

Before proceeding, ensure you have reviewed the RHUI 5 Installation and Management Guide. You must be authenticated to the Red Hat Container Registry (registry.redhat.io) to pull the required images.

Deployment Command

Modify your standard podman run installer command to include the TP images as shown below:

$ podman run ... registry.redhat.io/rhui5/installer-tp-rhel9 \
  rhui-installer ... --rhua-container-image rhui5/rhua-tp-rhel9 ...

All other arguments remain identical to a standard production deployment.

Generating Kubernetes Configuration

Once the RHUA is successfully deployed, use the updated rhui-manager utility to generate the necessary Kubernetes configuration (YAML).

Command Usage

Access the new k8s subcommand within the cds context:

# rhui-manager cds k8s --help
usage: rhui-manager cds k8s [-h] [--user_supplied_ssl_key] [--user_supplied_ssl_crt] [--inject]

optional arguments:
  -h, --help                Show this help message and exit
  --user_supplied_ssl_key   Optional absolute path to a user-supplied SSL key file.
  --user_supplied_ssl_crt   Optional absolute path to a user-supplied SSL certificate file.
  --inject                  Format: /local/file:/path/in/container[:mode]
                            Injects local files into the CDS container runtime.

Note: The SSL arguments are required only if you are utilizing custom certificates instead of RHUI-generated defaults. All the files must reside within the RHUA container.

Managing Output

The rhui-manager command triggers an internal Ansible playbook to generate the configuration. The playbook's execution logs are directed to stderr, while the resulting Kubernetes YAML is written to stdout.

To capture the configuration from a workstation via SSH and save the configuration on the workstation:

$ ssh RHUA_HOSTNAME sudo -i rhua rhui-manager cds k8s > /tmp/RHUI-K8s.yaml

Alternatively, you may execute the command directly on the RHUA. If using the rhua function to enter the container environment, ensure you are aware of the container’s localized file system paths when saving the output.

Caveats

  1. Files larger than 1 MB can be injected but the resulting YAML file will likely be impossible to apply. Do not attempt to inject such large files.

Known Issues

Updated 2026-04-29

At present, there are no known issues.

The following, previously identified issues have already been addressed:

  1. Files with no trailing newline could not be correctly injected into the YAML configuration. The configuration would have been broken (created, but impossible to apply).
  2. Empty files (0 bytes, not even an empty line) could not be correctly injected.
  3. JSON files were impossible to inject into the YAML configuration. Attempts to inject them would have lead to an exception, and no configuration would have been created.
  4. CRLF line terminators—typically used in text files edited in Microsoft Windows—were replaced with LF line terminators. Consequently, while the textual content was kept intact, the checksum of the original file and the injected file differed.
Product(s)
Category
Article Type