Bug 1782819 - cloud provider could not be initialized behind mitm proxy which is using some self-signed certificates
Summary: cloud provider could not be initialized behind mitm proxy which is using some...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-controller-manager
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3.0
Assignee: Maciej Szulik
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On: 1772756
Blocks: 1802297
TreeView+ depends on / blocked
 
Reported: 2019-12-12 12:24 UTC by Maciej Szulik
Modified: 2020-02-20 14:17 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1772756
Environment:
Last Closed: 2020-01-23 11:18:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-controller-manager-operator pull 328 0 None closed [release-4.3] Bug 1782819: Inject kube-controller-manager pods trust stores with trusted ca bundle 2021-02-18 14:19:18 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:19:14 UTC

Comment 2 Gaoyun Pei 2019-12-16 08:52:19 UTC
Verify this bug with payload 4.3.0-0.nightly-2019-12-13-180405

# oc get cm trusted-ca-bundle -n openshift-kube-controller-manager -o yaml
apiVersion: v1
data:
  ca-bundle.crt: |
...
kind: ConfigMap
metadata:
  creationTimestamp: "2019-12-16T08:01:56Z"
  labels:
    config.openshift.io/inject-trusted-cabundle: "true"
  name: trusted-ca-bundle
  namespace: openshift-kube-controller-manager


# oc get pod -n openshift-kube-controller-manager
NAME                                                                      READY   STATUS      RESTARTS   AGE
installer-2-qe-gpei-43-12160737-m-1.c.openshift-qe.internal               0/1     Completed   0          32m
installer-3-qe-gpei-43-12160737-m-0.c.openshift-qe.internal               0/1     Completed   0          32m
installer-3-qe-gpei-43-12160737-m-1.c.openshift-qe.internal               0/1     Completed   0          29m
installer-3-qe-gpei-43-12160737-m-2.c.openshift-qe.internal               0/1     Completed   0          30m
installer-4-qe-gpei-43-12160737-m-0.c.openshift-qe.internal               0/1     Completed   0          23m
installer-4-qe-gpei-43-12160737-m-1.c.openshift-qe.internal               0/1     Completed   0          25m
installer-4-qe-gpei-43-12160737-m-2.c.openshift-qe.internal               0/1     Completed   0          22m
kube-controller-manager-qe-gpei-43-12160737-m-0.c.openshift-qe.internal   3/3     Running     0          23m
kube-controller-manager-qe-gpei-43-12160737-m-1.c.openshift-qe.internal   3/3     Running     0          24m
kube-controller-manager-qe-gpei-43-12160737-m-2.c.openshift-qe.internal   3/3     Running     0          22m
revision-pruner-2-qe-gpei-43-12160737-m-1.c.openshift-qe.internal         0/1     Completed   0          32m
revision-pruner-3-qe-gpei-43-12160737-m-0.c.openshift-qe.internal         0/1     Completed   0          30m
revision-pruner-3-qe-gpei-43-12160737-m-1.c.openshift-qe.internal         0/1     Completed   0          28m
revision-pruner-3-qe-gpei-43-12160737-m-2.c.openshift-qe.internal         0/1     Completed   0          29m
revision-pruner-4-qe-gpei-43-12160737-m-0.c.openshift-qe.internal         0/1     Completed   0          22m
revision-pruner-4-qe-gpei-43-12160737-m-1.c.openshift-qe.internal         0/1     Completed   0          23m
revision-pruner-4-qe-gpei-43-12160737-m-2.c.openshift-qe.internal         0/1     Completed   0          21m

Inside the kcm pod, CA cert for proxy could be found in /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem

Comment 4 errata-xmlrpc 2020-01-23 11:18:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0062


Note You need to log in before you can comment on or make changes to this bug.