Create subscriptions
Now that the Configuration and Versions have been created, the next step is to create subscriptions for the Food Delivery application. In total, six subscriptions will be created:
| Subscription name | Version | Cluster group(s) |
|---|---|---|
| kafka-mongo-redis-on-all-clusters | kafka-mongo-redis | food-delivery-production-clusters food-delivery-development-clusters |
| backend-on-all-clusters | food-delivery-backend | food-delivery-production-clusters food-delivery-development-clusters |
| frontend-on-dev-clusters | food-delivery-frontend-v1 | food-delivery-development-clusters |
| frontend-on-prod-clusters | food-delivery-frontend-v1 | food-delivery-production-clusters |
| route-dev | development-route | food-delivery-development-clusters |
| route-prod | production-route | food-delivery-production-clusters |
These subscriptions will use the versions you created to deploy the code to the selected OpenShift clusters.
-
If you closed the IBM Cloud portal after the previous step, open the IBM Cloud portal to the Satellite Configurations page: https://cloud.ibm.com/satellite/configuration.
-
Click the the configuration based upon your Demo-UUID
- Click the Create subscription + button on the Overview page under Subscriptions.
Danger
Do NOT delete any existing subscriptions! These are used to create the OpenShift namespace you will be using in this demonstration. Deleting them will break the demonstration.
- Create the kafka-mongo-redis-on-all-clusters subscription.
Use the following values for the Create a subscription dialog:
Subscription name
Version Cluster groups
-
Click Create for the kafka-mongo-redis-on-all-clusters subscription.
-
Verify the kafka-mongo-redis-on-all-clusters subscription is created and deployed.
Immediately after clicking create, notice the new Subscription appears in the Subscriptions table. Initially, the Rollout status shows "---". After a few seconds, this should change to 2 deployed.
Note
If the status doesn't update automatically, click the page refresh button of your browser.
- Click the kafka-mongo-redis-on-all-clusters entry in the table and view the Subscription details.
Do you see errors?
If you see an "Unable to fetch header secret data." error for the aws_os_cluster cluster like shown below, you need to re-run the command to synchronize the Role-based access controls for the IBM Cloud Satellite Location that you executed in Part 1: Using the IBM Cloud command line interfaces (CLIs), steps 1 and 2.
Occasionally, you may see a deployment fail for other reasons. Satellite config will continue to try to fulfill the subscription. If you see a failure, wait a few minutes and then refresh your browser page to get the latest status. If you continue to see failures, you need to verify the versions created in the previous step are correct. Make sure you successfully replaced all instances of #######abc-ns with your Demo-UUID. If the failures continue, please report the issue using the slack channel specified in TechZone.
Note
In some circumstances, you may see more than 2 entries in the details section. As long as you have a successful deployment to the specified cluster groups, you can continue.
- Click your configuration link to return to the configuration page.
- Repeat the above process (steps 3 through 8) for each of the remaining subscriptions.
| Subscription Name | Version | Cluster group(s) |
|---|---|---|
| backend-on-all-clusters | food-delivery-backend | food-delivery-production-clusters food-delivery-development-clusters |
| frontend-on-dev-clusters | food-delivery-frontend-v1 | food-delivery-development-clusters |
| frontend-on-prod-clusters | food-delivery-frontend-v1 | food-delivery-production-clusters |
| route-dev | development-route | food-delivery-development-clusters |
| route-prod | production-route | food-delivery-production-clusters |
To avoid typographical errors, use the 
to copy the values below and paste into the Subscription name field.
Note
Pay special attention to the cluster group(s) that need to be specified for each subscription as shown in the table above! Specifying the wrong group(s) will cause problems with the demonstration.
- Verify all Subscriptions are created and deployed.
Info
In the next step you will access the Red Hat OpenShift portal to further verify the application has been deployed. You will also access the application and make updates to it using the food-delivery-frontend-v2 version.