Bug 1746375

Summary: Use operator to rollout new openshift-apiserver on proxy CA change
Product: OpenShift Container Platform Reporter: Stefan Schimanski <sttts>
Component: openshift-apiserverAssignee: Stefan Schimanski <sttts>
Status: CLOSED ERRATA QA Contact: Xingxing Xia <xxia>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.0CC: aos-bugs, mfojtik
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:38:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stefan Schimanski 2019-08-28 10:01:31 UTC
Rollout new openshift-apiserver through the operator when the proxy CA changes in openshift-apiserver, after reverting https://github.com/openshift/cluster-openshift-apiserver-operator/pull/226.

Comment 2 Xingxing Xia 2019-09-09 10:21:20 UTC
Checked in 4.2.0-0.nightly-2019-09-08-180038, openshift-apiserver pod yaml now does not include watchdog, and given CA configmap is created and proxy/cluster is configured:
...
spec:
  httpProxy: http://proxy-user1:$PASSWORD@10.0.76.148:3128
  httpsProxy: https://proxy-user1:$PASSWORD@10.0.76.148:3130
  noProxy: test.no-proxy.com
  trustedCA:
    name: user-ca-bundle
...

openshift-apiserver pod can rollout and then contain CA mount like
    - mountPath: /var/run/configmaps/trusted-ca-bundle
      name: trusted-ca-bundle

Comment 3 Xingxing Xia 2019-09-09 12:38:37 UTC
(In reply to Xingxing Xia from comment #2)
> Checked in 4.2.0-0.nightly-2019-09-08-180038, openshift-apiserver pod yaml
Hmm, should check operator pod.
> now does not include watchdog

Comment 4 errata-xmlrpc 2019-10-16 06:38:14 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-2019:2922