Encrypting microservices traffic

An administrator can configure the microservice framework to encrypt data traffic based on an SSL certificate. Note For a Kubernetes container manager, encryption can be configured for the ingress controller and service mesh. Refer to the documentation for the specific ingress controller or service mesh. Example service mesh implementations are Istio and Linkerd. Configuring the microservice framework and microservices for encrypted communication requires the following: Obtain an SSL certificate and keys for the server that will host the service dispatcher. A server certificate signed by a certificate authority (CA) can be purchased from a CA, and is recommended. Alternatively, cryptographic tools such as OpenSSL can be used to create a self-signed certificate and its keys. In the case of a self-signed certificate, the certificate issuer must be added to the client machine's trust store. When configuring a microservice node, for the Service Dispatcher Setting, choose the HTTPS protocol and complete the configuration parameters in the . When configuring the web client gateway, if you choose to override the default service dispatcher URL, ensure that you enter the HTTPS protocol for the Service Dispatcher URL. When deploying the container registry, for example, Docker Registry, ensure that the container registry uses the HTTPS encryption protocol.