Configure your own custom domains to publish Sterling Intelligent
Promising container
services by using the customDomains property, for integration or external
access.
Procedure
- Obtain the ingress certificate for the custom domain. You can bring your own ingress
certificate or create the ingress certificate for your custom domain by using the CertificateManager
instance utility. For more information, see CertificateManager custom resource.
- After you obtain the ingress certificate, create a secret out of that certificate. For
more information, see Creating an ingress certificate secret. If you
are using the CertificateManager, then the ingress certificate is auto created with the same name as
the CertificateManager instance.
- Define the
customDomains property within the ingress
section of the common configuration in SIPEnvironment. In the
following example, the identitySecretName is the secret that is created in step
2.
common:
ingress:
customDomains:
- host: <sip-example.com>
ssl:
enabled: true
identitySecretName: <sample-secret>
An ingress resource is created to publish the Sterling Intelligent
Promising
services through the specified custom domain. On Red Hat®
OpenShift® Container
Platform, it results
in a route, while on Kubernetes, it creates an ingress object, both serving the same purpose of
enabling external access.