Bug 1719965 - TLS Keys Not Added to Registry Routes
Summary: TLS Keys Not Added to Registry Routes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.2.0
Assignee: Oleg Bulatov
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks: 1720270 1730407
TreeView+ depends on / blocked
 
Reported: 2019-06-12 20:25 UTC by Adam Kaplan
Modified: 2019-10-16 06:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: the operator uses Secret.StringData that are write-only field to get data Consequence: the operator doesn't see the real data in the secret Fix: use Secret.Data instead Result: the operator sees the values
Clone Of:
: 1720270 (view as bug list)
Environment:
Last Closed: 2019-10-16 06:31:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:32:10 UTC

Description Adam Kaplan 2019-06-12 20:25:23 UTC
Description of problem: TLS keys and certificates not added to image registry routes.


Version-Release number of selected component (if applicable): v4.1.0


How reproducible: Always


Steps to Reproduce:
1. Create a TLS keypair via openssl
2. Using the keypair, create a TLS secret in the image-registry namespace:
```
$ oc create secret tls my-tls -n image-registry --cert my-tls.crt --key my-tls.key1
```
3. Instruct the registry operator to create a route with the provided tls secret
```
$ oc edit config.imageregistry.operator.openshift/io/cluster
...
spec:
  routes:
  - name: registry-url
    hostname: registry.apps.mycluster.myorg.net
    secretName: my-tls
```

Actual results: 
Route `registry-url` is created without TLS certificates added.


Expected results:
Route `registry-url` should have the TLS key and certificate defined.


Additional info:

Comment 3 Wenjing Zheng 2019-06-26 07:04:02 UTC
Verified on 4.2.0-0.nightly-2019-06-25-222454 with below steps:
1. $openssl req -nodes -newkey rsa:2048 -keyout myregistry.key -out myregistry.crt -x509
2. $ oc create secret tls my-tls -n openshift-image-registry --cert myregistry.crt --key myregistry.key
3. $ oc edit config.imageregistry.operator.openshift.io/cluster
spec:
  routes:
  - name: myregistry
    hostname: wzheng-route-openshift-image-registry.apps.qe-wewang-42.qe.devcluster.openshift.com
    secretName: my-tls
4. TLS can be seen as below:
spec:
  host: wzheng-route-openshift-image-registry.apps.qe-wewang-42.qe.devcluster.openshift.com
  subdomain: ""
  tls:
    certificate: |
      -----BEGIN CERTIFICATE-----
      xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
            -----END CERTIFICATE-----
    key: |
      -----BEGIN PRIVATE KEY-----
      -----END PRIVATE KEY-----
    termination: reencrypt

Comment 5 errata-xmlrpc 2019-10-16 06:31: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-2019:2922


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