Skip to main content
Solved

Kubernetes Ingress Controller Fake Certificate

  • October 2, 2025
  • 3 replies
  • 49 views

AshenR
Hero (Partner)
Forum|alt.badge.img+11

Hi All,

 

Currently, we are trying to enable public access to the application. However, when accessing it from a local machine, the URL is showing as unsecure, and the certificate CN is different—the one listed belongs to the ingress.

 

 

When accessing the application via the Management server or through the private network (by routing directly to the Middle Tier private IP), the application works fine.

Has anyone experienced this kind of issue previously?

Best answer by AshenR

Note: The issue was caused by a NAT rule configured on the firewall. When accessing the application, the traffic was not being forwarded to the correct Application server.

3 replies

Forum|alt.badge.img+11
  • Hero (Employee)
  • October 2, 2025

If the IFS Cloud namespace is ever deleted, the ifs-monitoring need to be deleted and re-applied. Otherwise the ingress certificates will be set to a "Fake self-signed certificate"

https://docs.ifs.com/techdocs/25r1/070_remote_deploy/010_installing_fresh_system/030_preparing_server/50_management_server/010_Setting_up_An_Environment/?h=main.ps1#6_install_ifs-monitoring_helm_chart_command

 


AshenR
Hero (Partner)
Forum|alt.badge.img+11
  • Author
  • Hero (Partner)
  • October 2, 2025

AshenR
Hero (Partner)
Forum|alt.badge.img+11
  • Author
  • Hero (Partner)
  • Answer
  • October 6, 2025

Note: The issue was caused by a NAT rule configured on the firewall. When accessing the application, the traffic was not being forwarded to the correct Application server.