# Your connection is not private(Kubernetes Ingress Controller Fake Certificate)

**URL:** <https://discuss.kubernetes.io/t/your-connection-is-not-private-kubernetes-ingress-controller-fake-certificate/27330>\
**Category:** General Discussions\
**Tags:** development, network, kubernetes-custom-resources\
**Created:** [March 5, 2024, 3:07am UTC](https://discuss.kubernetes.io/t/your-connection-is-not-private-kubernetes-ingress-controller-fake-certificate/27330 "2024-03-05T03:07:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![eu7863](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/eu7863/32/14449_2.png) [@eu7863](https://discuss.kubernetes.io/u/eu7863)\
**Post date:** [March 5, 2024, 3:07am UTC](https://discuss.kubernetes.io/t/your-connection-is-not-private-kubernetes-ingress-controller-fake-certificate/27330/1 "2024-03-05T03:07:46Z")

</div>

Hello everyone, I"m trying to understand a strange issue with my site being loading on the initial deployment or any update service type LB or ingress controller and then throwing a SSL error after a minute or so due to a `Kubernetes Ingress Controller Fake Certificate`  
I have service Type LB pointing to ingress controller and ingress to service, actually my backed only accepts HTTP connections

### Cluster information:

Kubernetes version: v1.24.9+rke2r2  
Cloud being used: Rancher  
Installation method: Helm

You can format your yaml by highlighting it and pressing Ctrl-Shift-C, it will make your output easier to read.