-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.18.0, 4.19.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
0
-
Critical
-
Yes
-
None
-
Proposed
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
In 4.18 we introduced kube-rbac-proxy into the VPA. We used the upstream image which is not FIPS compliant.
Version-Release number of selected component (if applicable):
4.18
How reproducible:
100%
Steps to Reproduce:
1. Look at https://github.com/openshift/vertical-pod-autoscaler-operator/blob/release-4.18/bundle/manifests/vertical-pod-autoscaler.clusterserviceversion.yaml#L653 2. 3.
Actual results:
gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0
Expected results:
registry.redhat.io/openshift4/ose-kube-rbac-proxy-rhel9:v4.18
Additional info:
- clones
-
OCPBUGS-45127 VPA Operator failing FIPS check due to kube-rbac-proxy image
-
- Closed
-
- is blocked by
-
OCPBUGS-45127 VPA Operator failing FIPS check due to kube-rbac-proxy image
-
- Closed
-
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update