I have several questions about service catalog that I’m trying to work through. I’ve upgraded from 3.6 to 3.7 using the 3.7 upgrade playbook. This has worked well. I then am able to finally successfully run the service-catalog playbook with TSB and ASB. I have had some issues with the install, primarily the api-server pod not starting because of problems with the extension-apiserver-authentication configmap and not getting the right ca file.
I’ve got this to work now but in my testing I have noticed some changes. For example, should the service-catalog deployment use daemonsets or deployment configs? If I create with the playbook, from 3.7 it creates daemonsets for the kube-service-catalog project for controller manager and api server. If I manually create the namespace and process the service-catalog ‘template’ from git hub, it creates deployment configs. Which is correct? Most docs I see say edit the dc when talking about service-catalog. Thanks, Todd ######################################################################## The information contained in this message, and any attachments thereto, is intended solely for the use of the addressee(s) and may contain confidential and/or privileged material. Any review, retransmission, dissemination, copying, or other use of the transmitted information is prohibited. If you received this in error, please contact the sender and delete the material from any computer. UNIGROUP.COM ######################################################################## _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
