[ https://issues.jboss.org/browse/JBIDE-25046?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25046: --------------------------------------- I would like someone to verify my verification steps: This is because I took steps to reproduce/verify that everything is working as [~jeffmaury] wrote in description, except I am having a little difference here. I will include also another step necessary (ie. cdk being started via cli beforehand). 1. EXEC: CDK 3 started in cli (to get url) 2. EXEC: Add OS 3 connection for admin (no registry url is set) 3. EXEC: Add OS 3 connection for developer (no registry url is set) 4. EXEC: Define CDK 3 (not 3.2+!) server adapter. 5. EXEC: Stop running CDK3 server adapter in cli 5. EXEC: Start CDK 3 via server adapter 6. ASSERT: CDK3 is started - PASS 7. ASSERT: OS 3 developer connection is updated (image registry url is set) - PASS 8. ASSERT: OS 3 admin connection is not updated (no image registry url) - PASS 9. EXEC: OS 3 admin connection discovery button is pressed 10. ASSERT: OS 3 admin connection image registry url is updated - PASS You can see the difference here, as it is developer's connection that is updated with proper image registry url when cdk 3 is started in IDE, not admin's connection. I do not think this is a problem at all, or I am mistaken? Another question is if it should be also verified on new CDK server adapter (3.2+)? WDYT [~jeffmaury], [~adietish], [~rob.stryker]? Devstudio: 11.1.0.AM3-v20171005-1232-B1225 CDK3: minishift v1.3.1+a2d3799, CDK v3.1.1-1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)