-
Notifications
You must be signed in to change notification settings - Fork 560
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: "Ingress uses the secret radio/ as a TLS certificate which does not exist." #1075
Open
3 of 4 tasks
Labels
bug
Something isn't working
Comments
This code assumes there is a tls.SecretName, my individual ingresses don't have a SecretName because they use the default TLS secret provided by ingress-nginx. I think there should be a NULL pointer check and break statement here, but I'm not proficient in Go.
|
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Affected Components
K8sGPT Version
0.1.3
Kubernetes Version
v1.29.2
Host OS and its Version
CentOS / upstream K8S
Steps to reproduce
K8sGPT Operator, LocalAI backend.
Expected behaviour
No reported issues with Ingresses.
Actual behaviour
Failures with most, if not all, ingresses.
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.
In my ingress-nginx definition.
and
kubectl -n radio edit ingress snapserver
Additional Information
As far as I can tell there is no spec.tls.secretName, for my ingresses, so the failure is a false positive.
The text was updated successfully, but these errors were encountered: