Bug 1599227 - re-encrypt route type for registry console
Summary: re-encrypt route type for registry console
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Registry Console
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 3.11.z
Assignee: Martin Pitt
QA Contact: Yanping Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-09 09:12 UTC by Rajnikant
Modified: 2023-09-07 19:13 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-13 17:46:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 10 Martin Pitt 2018-09-12 12:38:10 UTC
So now you replaced "--service=frontend" with "--service=registry-console". You described very well (and multiple times) how to create the *route*. But what I asked above is what that *service* is -- i. e. what are "frontend" or "registry-console" in the above? Please try something like

   oc get -o yaml service registry-console

This should have something like

  selector:
    somelabel: somevalue

Then run

  oc get pods -o yaml --selector='somelabel=somevalue'

and put the result here.

Perhaps this is somehow obvious to you, but it's not to me. Caveat: We don't currently have anyone in the cockpit team who is at all familiar with OCP, so if someone from the OCP team can jump in here, that would be much appreciated.

Comment 15 Niket Chavan 2019-06-17 10:30:27 UTC
Hello Team,

There has been no update on this bugzilla for a long time. As we need to update the status to the customer, share further findings OR let us know if any details are required for troubleshooting.

-Niket

Comment 18 Ben Parees 2020-05-12 21:13:11 UTC
customer cases are closed, can we close this bug?  is there still a plan to address it?

Comment 20 Ben Parees 2020-05-13 17:46:08 UTC
closing based on customer case being closed, please reopen if this is still an issue for your customer.


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