Home Explore Blog CI



kubernetes

4th chunk of `content/en/blog/_posts/2017-07-00-How-Watson-Health-Cloud-Deploys.md`
9c868cd006f695cf72d467ebadc5f4d1f47dfe76e754537e00000001000005c2
![](https://lh4.googleusercontent.com/laBRZK_ifwLXGkLL8fl0fZbUmm-HI4nC-tUNIFAy2wg4UHQT97reKyNOrNydYS8PmnhgqsBQctYCLTjJF12KR_uuVUdqiNx-B1OP1YrBwL2vi5SlEO9RSFQEbs-X6FoMHw0QK53A)



Deploying the application in IBM Cloud Kubernetes Service:



Provision a cluster in IBM Cloud Kubernetes Service with \<x\> worker nodes. Create Kubernetes controllers for deploying the containers in worker nodes, the IBM Cloud Kubernetes Service infrastructure pulls the Docker images from IBM Cloud Container Registry to create containers. We tried deploying an application container and running a logmet agent (see Reading and displaying logs using logmet container, below) inside the containers that forwards the application logs to an IBM Cloud logging service. As part of the process, YAML files are used to create a controller resource for the UrbanCode Deploy (UCD). UCD agent is deployed as a [DaemonSet](/docs/concepts/workloads/controllers/daemonset/) controller, which is used to connect to the UCD server. The whole process of deployment of application happens in UCD. To support the application for public access, we created a service resource to interact between pods and access container services. For storage support, we created persistent volume claims and mounted the volume for the containers.



| ![](https://lh6.googleusercontent.com/iFKlbBX8rjWTuygIfjImdxP8R7xXuvaaoDwldEIC3VRL03XIehxagz8uePpXllYMSxoyai5a6N-0NB4aTGK9fwwd8leFyfypxtbmaWBK-b2Kh9awcA76-_82F7ZZl7lgbf0gyFN7)

Title: Application Deployment in IBM Cloud Kubernetes Service
Summary
This section describes deploying an application within the IBM Cloud Kubernetes Service. It involves provisioning a cluster, creating Kubernetes controllers, pulling Docker images from the IBM Cloud Container Registry, and deploying a logmet agent. YAML files are used to create controller resources for UrbanCode Deploy (UCD), with the UCD agent deployed as a DaemonSet. Public access is enabled through a service resource, and persistent volume claims are created for storage support.