bug: the secret controller cannot handle secret update events in sometime

nic-6443 commented 2 years ago

Issue description

In our environment, there is a bug that the certificate in secret is updated, but the ingress controller does not update the new certificate to APISIX. The reason for this is not known yet. Since the environment where the bug occurred is no longer present, we cannot provide more information for now. If we reproduce it later, we will provide further information.

Environment

your apisix-ingress-controller version (output of apisix-ingress-controller version --long):
your Kubernetes cluster version (output of kubectl version):
if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):

Minimal test code / Steps to reproduce

/

Actual result

/

Error log

/

Expected result

No response

tao12345666333 commented 2 years ago

Thanks! What's your APISIX Ingress version? And did you use the ApisixTls resource?

tokers commented 2 years ago

@nic-6443 .

nic-6443 commented 2 years ago

What's your APISIX Ingress version?

It's a bit complicated, because the version we use is a branch we maintain for special reasons, using code from: https://github.com/nic-6443/apisix-ingress-controller/tree/patch-1 to support upstream mtls, but the code has been merged to upstream.

And did you use the ApisixTls resource?

Yes

tao12345666333 commented 2 years ago

If you're not using this repository but a fork version, I can't easily provide support.

tao12345666333 commented 2 years ago

And it's not easy to reproduce.

tokers commented 2 years ago

Yes

We may try to reproduce this problem with the standard version. @nic-6443

nic-6443 commented 2 years ago

Okay, we will try to test with the latest version of the ingress controller and sync up if we get any new clues

apache / apisix-ingress-controller