Thank you Jeff. I’ve been able to get it to install and include the tsb and asb. I’ve noticed though that I had to run installer (config.yml) to generate the cert and key/values for the config-map ‘extension-apiserver-authentication<https://master.apps.shared.openshift.local/console/project/kube-system/browse/config-maps/extension-apiserver-authentication>’ because just run of service-catalog.yml fails because the requestheader-client-ca-file Is not created. After running the installer, then the service catlog playbook, it succeeds and the api server can start properliy.
Thanks, Todd From: Jeff Peeler <[email protected]> Date: Thursday, April 5, 2018 at 3:03 PM To: "Walters, Todd" <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: 3.7 Service Catalog Questions On Tue, Mar 27, 2018 at 11:54 AM, Walters, Todd <[email protected]<mailto:[email protected]>> wrote: 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. These installer issues have been fixed and to the best of my knowledge released now. 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. I assume by processing the template from github, you're referring to this template? https://github.com/openshift/origin/blob/ce742c8267add01a63cbdc6402c9287978ce9024/examples/service-catalog/service-catalog.yaml<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenshift%2Forigin%2Fblob%2Fce742c8267add01a63cbdc6402c9287978ce9024%2Fexamples%2Fservice-catalog%2Fservice-catalog.yaml&data=01%7C01%7CTodd_Walters%40unigroup.com%7C090f7aaaf7b44d4a13ba08d59b304126%7C259bdc2f86d3477b8cb34eee64289142%7C1&sdata=lm5so9jkfQ3v5m0BKxO9%2FL4v2NAAs%2BndH2AGjbOilm8%3D&reserved=0> The ansible installer is for production deployments, while the above template is used for a developer environment. The usage of a DaemonSet for catalog running in production is intentional. The main difference between the two is that daemon sets ensure pods are running per node (based on label selector) versus deploymentconfigs which are concerned with the pod count. These links should help explain further: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#what-is-a-daemonset<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkubernetes.io%2Fdocs%2Fconcepts%2Fworkloads%2Fcontrollers%2Fdaemonset%2F%23what-is-a-daemonset&data=01%7C01%7CTodd_Walters%40unigroup.com%7C090f7aaaf7b44d4a13ba08d59b304126%7C259bdc2f86d3477b8cb34eee64289142%7C1&sdata=V3zDeFUsvm3RyCcB0gwGHUqlBzaEm8rtqpKrENZ4wpo%3D&reserved=0> https://docs.openshift.org/latest/architecture/core_concepts/deployments.html#deployments-and-deployment-configurations<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.openshift.org%2Flatest%2Farchitecture%2Fcore_concepts%2Fdeployments.html%23deployments-and-deployment-configurations&data=01%7C01%7CTodd_Walters%40unigroup.com%7C090f7aaaf7b44d4a13ba08d59b304126%7C259bdc2f86d3477b8cb34eee64289142%7C1&sdata=YssB0EKilFq2UaxPBfiXA7P0GjsMv%2BbRgPS%2B4r317Yc%3D&reserved=0> https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkubernetes.io%2Fdocs%2Fconcepts%2Fworkloads%2Fcontrollers%2Freplicationcontroller%2F&data=01%7C01%7CTodd_Walters%40unigroup.com%7C090f7aaaf7b44d4a13ba08d59b304126%7C259bdc2f86d3477b8cb34eee64289142%7C1&sdata=d4RzG1vDi2z0jvQWkmp5Asq1cR9QT%2FjPc5EuuLUQuvU%3D&reserved=0> ######################################################################## 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
