Page Comparison

You can set up Nginx Ingress Controller as a front-end for the communication between external users and the application. 

...

Configuring SSL in Kubernetes Ingress

An important prerequisites for a secure communication between the web browser (end user) and the web server is to use Secure Sockets Layer (SSL) certificate. Adeptia Connect microservices also adheres to this requirement. To achieve this, after you've deployed Adeptia Connect, you need to configure SSL in the Kubernetes Ingress Controller. If you're using any Kubernetes ingress controller as a front-end for Webapp Gateway microservicecommunication, you need to configure SSL through Kubernetes ingress object. 

...

Referencing this secret in an Ingress tells the Ingress controller to secure the channel from the client to the load balancer using TLS. You need to make sure the TLS secret you created came from a certificate that contains a Common Name (CN), also known as a Fully Qualified Domain Name (FQDN), for example, dummy.adeptia.com.

Note: There is a gap between TLS features supported by various Ingress controllers. Please refer to documentation on nginx, GCE, or any other platform specific Ingress controller to understand how TLS works in your environment.

...

Anchor
Exporting the public key Exporting the public key

Exporting Exporting the public key of Webapp Gateway/Ingress controller 

The steps for exporting the public key of the Webapp Gateway/Ingress controller external URL (external FQDN, for example, dummy dummy.adeptia.com) vary from browser to browser. It is recommended that you export the key using DER encoded binary format X.509 (.CER). Following are the steps to export the public key in Google Chrome browser.

...

1. Run the following Kubectl command to copy the certificate to the PVC or shared storage volume for the Webapp Gateway pod.

   Code Block
   language css theme Midnight
   Kubectl --namespace <namepace_name> cp <local_path_for_SSL_certificate> <pod_name>:shared/truststore/<SSL_certificate_name>

   
   

2. Navigate to the Microservice pod (Eg. Webrunner) by running the following command.

   Code Block
   language css theme Midnight
   Kubectl --namespace <namespace_name> exec -it <pod_name> -- sh

   
   

3. Run the following Keytool command to import the certificate.

   Code Block
   language css theme Midnight
   keytool -import -trustcacerts -file <Path_of_SSL_Certificate> -alias <alias_name> -keystore <Path of cacerts file>

   Where,

             <Path_of_SSL_Certificate> is the path of SSL certificate.

             <Path of cacerts file> is the path of Truststore.

   For example,

   Code Block
   language css theme Midnight
   keytool -import -trustcacerts -file shared/truststore/ssl-certs.cer -alias adeptia -keystore shared/truststore/cacerts

   You'll be prompted to enter a password. Enter the default password changeit.

4. Run the exit command to exit from the pod shell.
5. Restart all the Microservices to bring the changes into effect.