Use the Calabash GUI click on the “Infrastructure” on the top of the window. The Infrastructure page becomes current. Select “lake_finance” as the data system. And click on the green “Create Infrastructure Object” button.
Fill in the form as follows.
The “Kubernetes application name” is
- the namespace in the Kubernetes cluster,
- the consumer group id of the deployed app consuming data from “topic1,”
- the transactional id of the deployed app producing data to “topic2.”
Select “Microservice on Kubernetes” as the infrastructure object type.
Next, we define some deployment properties for the Kubernetes.
Next, you need to define the container image. If you have gone through the previous topic successfully, you must have a container image built. So we directly use the image in the cloud container registry.
In the above, we enter the specification of the existing container image. Note that the “dlb-internal” is the project used by the tutorial tester. In your practice, change it to your project that contains this image.
There will be an “init.properties” file stored in a Kubernetes secrets object. This object will be mounted to a “/secret” directory within the container. Therefore, Calabash GUI automatically defines these for us. See below.
Different from the “Microservice on VM,” the host volume is optional. There is also no need to define a service for our replicator example.
The post-design steps are the same as those in the previous tutorial topic. Please go back there for deployment and testing.