Validating the Installation
After the deployment procedure is complete, you should validate the deployment to ensure that everything is working according to your needs. The deployment may take approximately 4-5 minutes to complete.
-
Check the Helm chart release status by invoking the following command and verify that the
STATUS
isDEPLOYED
:helm status my-release
- Wait for the pod to be ready. To verify the pods status (READY) use the dashboard or through the
command line interface by invoking the following
command:
kubectl get pods -l release my-release -n my-namespace -o wide
- To view the service and ports exposed to enable communication in a pod invoke the following
command:
kubectl get svc -l release= my-release -n my-namespace -o wide
The screen output displays the external IP and exposed ports under EXTERNAL-IP and PORT(S) column respectively. If external LoadBalancer is not present, refer Master node IP as external IP.
Exposed Services
If required, this chart can create a service of ClusterIP for communication within the cluster. This type can be changed while installing chart using service.type key defined in values.yaml. There are two ports where IBM Connect:Direct processes run. API port (1363) and FT port (1364), whose values can be updated during chart installation using service.apiport.port or service.ftport.port.
DIME and DARE Security Considerations
This topic provides security recommendations for setting up Data In Motion Encryption (DIME) and Data At Rest Encryption (DARE). It is intended to help you create a secure implementation of the application.
- All sensitive application data at rest is stored in binary format so user cannot decrypt it. This chart does not support encryption of user data at rest by default. Administrator can configure storage encryption to encrypt all data at rest.
- Data in motion is encrypted using transport layer security (TLS 1.3). For more information see, Secure Plus.