papdaniel opened a new issue, #2082:
URL: https://github.com/apache/apisix-ingress-controller/issues/2082
### Current Behavior
I created an ApisixTls resource, but the secret (with tls keys) didn't exist
at that time.
Then ~2 minutes later the secret has been created, but the ApisixTls 20
minutes later still says that the secret not found. It seems the controller
checked the secret 2 times in 20 minutes.
```
Status:
Conditions:
Last Transition Time: 2023-12-04T14:17:47Z
Message: secret "c-deps-common" not found
Observed Generation: 1
Reason: ResourceSyncAborted
Status: False
Type: ResourcesAvailable
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning ResourceSyncAborted 22m (x2 over 22m) ApisixIngress
ApisixIngress synced failed, with error: secret "c-deps-common" not found
```
After ~30 minutes it finally synced successfully, and everything works.
### Expected Behavior
If I'm correct, it should retry at least every minute:
https://apisix.apache.org/docs/ingress-controller/FAQ/#how-does-apisix-ingress-controller-retry
### Error Logs
_No response_
### Steps to Reproduce
1. Create an ApisixTls resources (with non-existent tls secret)
2. Wait 2 minutes
3. Create the tls secret
### Environment
- APISIX Ingress controller version (run `apisix-ingress-controller version
--long`)
```
Version: 1.6.0
Git SHA: no-git-module
Go Version: go1.19.4
Building OS/Arch: linux/amd64
Running OS/Arch: linux/amd64
```
- Kubernetes cluster version (run `kubectl version`)
```
Client Version: v1.28.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.3-eks-4f4795d
```
- OS version if running APISIX Ingress controller in a bare-metal
environment (run `uname -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]
