[BUG] Rancher Serves Fake Cert, Even After Following Rancher Docs To Update Private CA and Cert

[umpaduncdude]

Rancher Server Setup

• Rancher version: 2.8.2 (helm ls -n cattle-system)
• Installation option (Docker install/Helm Chart): Helm Chart
  • If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE2
• Proxy/Cert Details: Private CA, Self-Signed Cert, Installed using steps outlined here: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/resources/update-rancher-certificate

Information about the Cluster

• Kubernetes version: v1.27.12+rke2r1
• Cluster Type (Local/Downstream): Local
  • If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

User Information

• What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)
  • If custom, define the set of permissions: Admin

Describe the bug
We initially installed Rancher 90 days ago with Rancher's self signed certs. We started getting reports that kubectl commands with Rancher generated kubeconfigs were getting x509 errors. They expired, and we tried following the steps outlined in the docs to update the certs and the CA:
https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/resources/update-rancher-certificate
However, Rancher serves a fake cert even after following steps to update the CA and cert outlined above:
We thought step 3b would work but it just doesn't work. We still get "Kubernetes Ingress Controller Fake Certificate"

To Reproduce
Follow the steps outlined in https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/resources/update-rancher-certificate.
Once you complete step 3b, it didn't work. We even changed every secret manually inside of Rancher that we possibly could and it still didn't work.

Result
Fake Cert: "Kubernetes Ingress Controller Fake Certificate." Downstream clusters report x509 errors ("cert is for ingress.local not rancher.blah.blah").

Expected Result
The real cert installed in tls-rancher-ingress is served.

Screenshots
Fake cert:

Downstream cluster:

Cert Secrets:

[umpaduncdude]

Issue was with ingress config, not rancher