Skip to content

Latest commit

 

History

History
97 lines (66 loc) · 3.09 KB

README-kubernetes.md

File metadata and controls

97 lines (66 loc) · 3.09 KB
Raw

Deploy to IBM Cloud Kubernetes Service

Follow these instructions to deploy this application to a Kubernetes cluster and connect it with a Cloudant database.

Download

git clone https://github.com/IBM-Cloud/get-started-node
cd get-started-node

Build Docker Image

  1. Find your container registry namespace by running ibmcloud cr namespaces. If you don't have any, create one using ibmcloud cr namespace-add <name>

  2. Identify your Container Registry by running ibmcloud cr info (Ex: registry.ng.bluemix.net)

  3. Build and tag (-t)the docker image by running the command below replacing REGISTRY and NAMESPACE with he appropriate values.

    docker build . -t <REGISTRY>/<NAMESPACE>/myapp:v1.1.0

    Example: docker build . -t registry.ng.bluemix.net/mynamespace/myapp:v1.1.0

  4. Push the docker image to your Container Registry on IBM Cloud

    docker push <REGISTRY>/<NAMESPACE>/myapp:v1.1.0

Deploy

Create a Kubernetes cluster

  1. Creating a Kubernetes cluster in IBM Cloud.
  2. Follow the instructions in the Access tab to set up your kubectl cli.

Create a Cloudant Database

  1. Go to the Catalog and create a new Cloudant database instance.

  2. Choose IAM for Authentication.

  3. Create new credentials under Service Credentials and copy value of the url field.

  4. Create a Kubernetes secret with your Cloudant credentials.

kubectl create secret generic cloudant --from-literal=url=<URL> --from-literal=iamApiKey=<IAM_API_KEY>

Example:

kubectl create secret generic cloudant --from-literal=url=https://xxxxx-yyyy-zzz-eeeee-ddddddd-bluemix.cloudantnosqldb.appdomain.cloud --from-literal=iamApiKey=xxxxxx-ddd-ppppppppppp

Create the deployment

  1. Replace <REGISTRY> and <NAMESPACE> with the appropriate values in kubernetes/deployment.yaml
  2. Create a deployment:
kubectl create -f kubernetes/deployment.yaml

  • Paid Cluster: Expose the service using an External IP and Loadbalancer

    kubectl expose deployment get-started-node --type LoadBalancer --port 8080 --target-port 8080

  • Free Cluster: Use the Worker IP and NodePort

    kubectl expose deployment get-started-node --type NodePort --port 8080 --target-port 8080

Access the application

Verify STATUS of pod is RUNNING

kubectl get pods -l app=get-started-node

Standard (Paid) Cluster:

  1. Identify your LoadBalancer Ingress IP using kubectl get service get-started-node
  2. Access your application at t http://<EXTERNAL-IP>:8080/

Free Cluster:

  1. Identify your Worker Public IP using ibmcloud cs workers YOUR_CLUSTER_NAME
  2. Identify the Node Port using kubectl describe service get-started-node
  3. Access your application at http://<WORKER-PUBLIC-IP>:<NODE-PORT>/

Clean Up

kubectl delete deployment,service -l app=get-started-node
kubectl delete secret cloudant