- Issued:
- 2025-06-26
- Updated:
- 2025-06-26
RHBA-2025:9757 - external secrets operator for Red Hat OpenShift 0.1.0
Synopsis
external secrets operator for Red Hat OpenShift 0.1.0
Type/Severity
Bug Fix Advisory None
Topic
external secrets operator for Red Hat OpenShift 0.1.0
Description
The External Secrets Operator for Red Hat OpenShift builds on top of Kubernetes, which integrates external secret management systems like AWS Secrets Manager, HashiCorp Vault, Google Secrets Manager, Azure Key Vault, IBM Cloud Secrets Manager, and many more. The operator reads information from external APIs and automatically injects the values into a Kubernetes Secret. The current release of external secrets Operator for Red Hat OpenShift is for Technology Preview.
Solution
Before installing the operator, make sure all previously released errata relevant to your system have been applied. The steps to apply the upgraded images will differ depending on the installation plan approval policy that will be used while installing the external secrets operator for Red Hat OpenShift.
- If the approval policy is set to
Automatic, then the Operator will be upgraded automatically when there is a new version of the Operator. No further action is required to upgrade. This is the default setting. - If you changed the approval policy to
Manual, then you must manually approve the upgrade to the Operator.
Affected Products
| Product | Version | Arch |
|---|---|---|
| External Secrets Operator for Red Hat OpenShift | 0.1 | aarch64 |
Fixes
(none)
CVEs
(none)
References
- https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/security_and_compliance/external-secrets-operator-for-red-hat-openshift
Additional information
- The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.