Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 4. Bug fixes


In this release of Red Hat Trusted Artifact Signer (RHTAS), we fixed the following bugs. In addition to these fixes, we also list the descriptions of previously known issues found in earlier versions that we fixed.

Helm chart disables PodDisruptionBudget by default
The Helm chart included a PodDisruptionBudget (PDB) that previously defaulted to minAvailable=1, which coincided with the default replicaCount of 1 for RHTAS components. This arrangement led to deadlocks during node draining, and OpenShift cluster upgrades. With this release, the PDB is disabled by default within the Helm chart, ensuring smooth progression of node draining, and when performing OpenShift cluster upgrades. Users running multiple replicas can re-enable the PDB for added availability guarantees during disruptions.
Cosign does not respect individual TSA certificate chains during rotation

With this release, we updated cosign to version 3. This update fixes the issue where cosign expects only one single Timestamp Authority (TSA) certificate chain. You can rotating the TSA certificate chain by giving the whole TSA certificate chain to The Update Framework (TUF) as an individual target. During the rotation process, setting the new TSA certificate chain as the new TUF target, and expiring the old TSA certificate chain no longer displays the following error message.

main.go:74: error during command execution: unable to load TSA certificates: TSA certificate chain must contain exactly one leaf certificate

For information about rotating the TSA signer key and certificate chain see our procedure for Red Hat OpenShift Container Platform, or Red Hat Enterprise Linux.

Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de la documentation Red Hat

Legal Notice

Theme

© 2026 Red Hat
Retour au début