search

Azure / application-gateway-kubernetes-ingress

This is an ingress controller that can be run on Azure Kubernetes Service (AKS) to allow an Azure Application Gateway to act as the ingress for an AKS cluster.
https://azure.github.io/application-gateway-kubernetes-ingress
MIT License
677 stars 420 forks source link

Removal of HTTPS Listener when there is an intermittent issue in secret retrieval #1568

Closed akshaysngupta closed 10 months ago

akshaysngupta commented 1 year ago

Describe the bug Creating this to track fix for https listener removal when there is an intermittent issue in secret retrieval.

I0708 14:17:14.664140       1 backendaddresspools.go:47] Created backend pool <redacted> for service <redacted>
I0708 14:17:14.664152       1 backendaddresspools.go:47] Created backend pool <redacted> for service <redacted>
I0708 14:17:14.664160       1 backendaddresspools.go:47] Created backend pool <redacted> for service <redacted>
'Warning' reason: 'SecretNotFound' Unable to find the secret associated to secretId: [<redacted>]
I0708 14:17:14.664557       1 event.go:282] Event(v1.ObjectReference{Kind:'Ingress', Namespace:'<redacted>', Name:'<redacted>', UID:'<redacted>', APIVersion:'networking.k8s.io/v1', ResourceVersion:'<redacted>', FieldPath:''}): type: 'Warning' reason: 'SecretNotFound' Unable to find the secret associated to secretId: [<redacted>]
I0708 14:17:14.664575       1 event.go:282] Event(v1.ObjectReference{Kind:'Ingress', Namespace:'reportportal', Name:'<redacted>', UID:'<redacted>', APIVersion:'networking.k8s.io/v1', ResourceVersion:'<redacted>', FieldPath:''}): type: 'Warning' reason: 'SecretNotFound' Unable to find the secret associated to secretId: [<redacted>]

Further down in the logs:

I0708 14:17:25.472863       1 reflector.go:530] pkg/mod/k8s.io/client-go@v0.21.2/tools/cache/reflector.go:167: Watch close - *v1.Secret total 0 items received
egallis31 commented 1 year ago

Any updates on this issue assignment? This has been an intermittent issue during cluster upgrade events.

The initial issue comment is the exact description of the symptoms and has occurred multiple times since the start of the year.

If not, is there guidance to prevent this from occurring in a proactive rather than reactive manner of forcefully restarting the deployment?

akshaysngupta commented 1 year ago

@egallis31 does your AGIC log has the same messages as in the issue description ?

egallis31 commented 1 year ago

any updates on when this fix will be released?

tracking this public issue as follow-up for my support case requests for this specific issue fix.