[Question/Bug?]: False positive? "Ingress uses the secret radio/ as a TLS certificate which does not exist."

[rwlove]

Checklist

• I've searched for similar issues and couldn't find anything matching
• I've included steps to reproduce the behavior

Affected Components

• K8sGPT (CLI)
• K8sGPT Operator

K8sGPT Version

0.1.3

Kubernetes Version

v1.29.2

Host OS and its Version

No response

Steps to reproduce

K8sGPT Operator, LocalAI backend.

---
apiVersion: core.k8sgpt.ai/v1alpha1
kind: K8sGPT
metadata:
  name: k8sgpt-local-ai
  namespace: ai
spec:
  ai:
    backend: localai
    baseUrl: http://localai-local-ai.ai.svc.cluster.local:80/v1                                                                                                                                               
    model: ggml-gpt4all-j
    secret:
      name: localai-api-key-secret
      key: localai-api-key
  noCache: false
  version: v0.3.29

➜  home-ops git:(main) ✗ kubectl -n ai get results -o json | jq . | grep "uses the secret"
            "text": "Ingress uses the secret ai/ as a TLS certificate which does not exist."
            "text": "Ingress uses the secret ai/ as a TLS certificate which does not exist."
            "text": "Ingress uses the secret ai/ as a TLS certificate which does not exist."
            "text": "Ingress uses the secret auth/ as a TLS certificate which does not exist."
            "text": "Ingress uses the secret auth/ as a TLS certificate which does not exist."
            "text": "Ingress uses the secret collab/ as a TLS certificate which does not exist."

Expected behaviour

I'm unclear why K8sGPT is stating that my Ingresses are using an invalid TLS certificate. As far as I can tell, I don't see anything wrong. See additional information below.

Actual behaviour

False positives.

Additional Information

K8sGPT tells me that many of my ingresses are using an invalid TLS. Everything is working and I can access my services through the ingress without any problems, but I'm trying to cleanup these errors - everything looks fine to me.

      main:
        className: internal
        hosts:
          - host: &host "{{ .Release.Name }}.${SECRET_DOMAIN}"
        paths:
              - path: /
                service:
                  identifier: main
                  port: *httpPort
        tls:
          - hosts:
              - *host

In my ingress-nginx definition.

      extraArgs:
        default-ssl-certificate: |-
          network/${SECRET_DOMAIN/./-}-tls

and

➜  home-ops git:(main) ✗ kubectl -n radio describe ingress snapserver
Name:             snapserver
Namespace:        radio
Address:          10.45.0.1
Ingress Class:    internal
Default backend:  <default>
TLS:
  SNI routes snapserver.foo.com
Rules:
  Host                           Path  Backends
  ----                           ----  --------
  snapserver.foo.com  
                                 /   snapserver:80 (10.42.6.65:1780)
Annotations:                     hajimari.io/appName: Speaker Selection
                                 hajimari.io/enable: true
                                 hajimari.io/group: Radio
                                 hajimari.io/icon: mdi:radio
                                 hajimari.io/instance: user,admin
                                 meta.helm.sh/release-name: snapserver
                                 meta.helm.sh/release-namespace: radio
Events:                          <none>

[rwlove]

This is really an issue for k8SGPT, not the operator. Closing this in favor of a k8sGPT defect: k8sgpt-ai/k8sgpt#1075