Configuring hostnames and certificates
IBM Cloud Pak® for Integration instances automatically generate a set of hostnames and certificates that are used during the initial installation. You can replace these defaults with custom hostnames and certificates.
Routes for instances in Cloud Pak for Integration use the Red Hat OpenShift ingress certificates by default. There are two options for configuring certificates for instances:
Configure the Red Hat OpenShift ingress certificates. To get the available methods for updating these certificates, see Red Hat OpenShift certificates.
If supported by an instance, configure an instance to use certificates that are specific to its host.
Red Hat OpenShift certificates
Configuring Red Hat OpenShift certificates
Routes for instances in Cloud Pak for Integration use the Red Hat OpenShift ingress certificates by default. To update the keys and certificates that are used by these routes, admin users can either replace the OpenShift default ingress certificates or reconfigure the instance to use keys and certificates that are specific to the instance.
For information on configuring the Red Hat OpenShift certificates, see 3.1. Replacing the default ingress certificate in the OpenShift documentation.
Configuring the hostname and certificates for the Platform UI
For information about configuring (and reverting) custom certificates and the hostname for the Platform UI, see Configuring the Platform UI.
Configuring the hostname and certificates for Keycloak
To configure the hostname and certificates for Keycloak, see "Customizing the default hostname and TLS configuration" in Keycloak configuration.
Configuring the hostname for instances
For information on configuring the custom hostname for instances, see the following documentation:
Automation assets, see Using Automation assets
Integration dashboard, see Custom resource values,
spec.routes.api.hostparameter.