acuteaura opened a new issue, #2083:
URL: https://github.com/apache/apisix-ingress-controller/issues/2083
### Current Behavior
We have found a broken SSLs from an ingress object (not
ApisixTls+ApisixRoute) that a developer misconfigured. The update time is about
a month in the past, and as far as I can tell, the namespace hasn't existed in
several weeks.
```
{
"createdIndex": 90460,
"modifiedIndex": 90460,
"value": {
"type": "server",
"labels": {
"meta_secret_namespace": "fun--f-feature-fte-b43a",
"meta_secret_name": "environment-cert",
"managed-by": "apisix-ingress-controller"
},
"snis": [
"sni-that-collides-with-different-cert"
],
"id": "14abff72",
"create_time": 1699527199,
"update_time": 1699527199,
"status": 1,
"key": "/apisix/ssls/14abff72"
}
```
### Expected Behavior
The ApisixTls is found as orphaned when evaluating Ingresses and delted.
### Error Logs
N/A
### Steps to Reproduce
#1985 fixing multiple generated ApisixTls objects from Ingress might be
related, we're running the fix from the associated PR.
### Environment
- APISIX Ingress controller version (run `apisix-ingress-controller version
--long`) 1.7.0
([this](https://github.com/handelsblattgroup/apisix-ingress-controller/commits/hmg)
tree specifically)
- Kubernetes cluster version (run `kubectl version`) 1.26
- OS version if running APISIX Ingress controller in a bare-metal
environment (run `uname -a`) N/A
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
