Embedded Container Service (ECS) checklist

Use this checklist to ensure that your Embedded Container Service (ECS) is configured and ready for installing CDP Private Cloud Data Services.

Table 1. Embedded Container Service (ECS) checklist to install CDP Private Cloud Data Services
Item Summary Documentation Notes
DNS configuration Ensure that you have set up the DNS and Reverse DNS between OpenShift container hosts and CDP Private Cloud Base. This is required for obtaining Kerberos ticket-granting tickets. Certificate management and DNS A wildcard DNS entry is required for resolving the ingress route for applications. The ingress route is usually behind a load balancer.
Check if you can access the OpenShift hostnames outside the cluster Ensure that OpenShift application hostnames can be accessed from outside the cluster. You can test this by creating an ingress point on the target cluster. A minimal Ingress resource example

Perform a DNS query on the route generated, to check if you can access the hostnames outside the cluster.

Allow WebSocket traffic in addition to HTTPS When a load balancer is used for your OpenShift Container Platform external API, you must allow WebSocket traffic in addition to HTTPS. The load balancer must allow WebSockets on port 80. Also, ensure that you set the load balancer server timeout to 5 minutes. N/A N/A
Clock time from NTP source Ensure that the NTP clock in CDP Private Cloud Base is in sync with the time configured in the OpenShift cluster. This is an important step if your setup does not have access to the Internet. Enable an NTP Service Install CDP Private Cloud Data Services in air gap environment