Repository files navigation

These modules deploy a simple demo app to an IKS Cluster using aCluster Ingress deployment.

1. Setup
2. Deployment
3. Ingress Depolyment Pattern
4. Module Variables

Make sure that the ALBs in your cluster are enabled. If you want the app to be available publicly, make sure the public ALBs are enabled

In order to make sure this architecture deploys correctly, ensure that you have copied any icr image pull secrets into the namespace where the app will be deployed if you're using ICR for the images. You will need to have Docker installed locally. You can find more information on getting started with IBM Container Registryhere.

Both of these deployment patterns use anode demo app. To upload this example application toIBM Cloud Container Registry follow these steps:

1. Log in to IBM Cloud using the CLI

ibmcloud login

2. Log in to the IBM Container Registry

ibmcloud cr login

3. If you do not have a namespace you want to use with your app, create a namespace:

ibmcloud cr namespace-add <my_namespace>

4. In the./node-demo-app directory run this command to build the docker container:

docker build . -t <image_name>:<tag>

5. Next, tag the image to upload to ICR

docker tag <image_name>:<tag> <region>.icr.io/<my_namespace>/<new_image_repo>:<new_tag>

6. Push the image to ICR

docker push <region>.icr.io/<my_namespace>/<new_image_repo>:<new_tag>

This pattern creates an IKS deployment equivalant to this .yaml file:

apiVersion: apps/v1kind: Deploymentmetadata:  name: demo-app  namespace: default  labels:    app: demo-appspec:  selector:    matchLabels:      app: test-app  template:    metadata:      labels:        app: api-service    spec:      containers:      - image: <region>.icr.io/<my_namespace>/<new_image_repo>:<new_tag>        name: test-app        env:            - name: PORT              value: 8080

After the application deployed, the script creates a NodePoet service for the application with the specified service port that points to the application. The terraform script gets a list of enabled ALB IDs from the cluster is deployed and creates a semicolon separated list of them and uses it to create a cluster ingress resource.

Once your application has been deployed, you'll be able to visit it at<app_name>.<your_cluster_ingress>.

The following variables are used for both deployment methods.