Debugging HTTPS Support related Issues

UDR supports HTTPS and its validations are done at Ingress Gateway of UDR. You may encounter issues related to HTTPS when:

• HTTPS port is not exposed: Execute the following command to figure out whether HTTPS port is exposed or not:

  kubectl get svc --n <ocudr-namespace>

  Figure 5-16 HTTPS Port Exposed

  

  Note:

  In the above screen, the secure port is 443.
  If the HTTPS port is not exposed, then enable the configuration information highlighted in the following screen under the ingressgateway section of the values.yaml file.

  Figure 5-17 Configuration Info under Ingressgateway

  
• IngressGateway Container is stuck in Init State/Failed:The IngressGateway Container can stuck due to any one of the following reasons:
  • When config initssl is enabled under ingressgateway section of the values.yaml file.

    Figure 5-18 config initssl

    
  • If config initssl is enabled, then you need to check whether secrets are created with all required certificates. The following screenshot shows the commands that you need to execute to check whether secrets are present and have all the required data.

    Figure 5-19 Commands to check Secrets

    
• Config-Server Container Stuck in Hooks Init State: The UDR installation stucks in Hooks Init state when there is database connection failure.

  Figure 5-20 Config Server Container Status