You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
Event(v1.ObjectReference, wrap.go:42] PATCH Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
NGINX Ingress controller version:
0.11.0
Kubernetes version (use kubectl version):
1.8.5
Environment:
Production
Cloud provider or hardware configuration: AWS
OS (e.g. from /etc/os-release): CoreOS
Kernel (e.g. uname -a):
What happened:
We noticed an outage in our beta production environment. Basically, there was a helm based deployment that happened around 12:34:34, that seemed to have triggered the ingress watch & reloads, which then triggered delete on few of the ingresses of certain services. What we see from the logs is an objectrefence error, and this seems to occur constantly. It feels as if ingress-controller is constantly trying to delete these ingresses and failing due to object reference error. This happened for a few hours, during that time there were multiple ingress reloads triggered and the apps stopped responding/ were timing out.
This was resolved by deleting some of the ingresses and redeploying an app, but we want to see why this could have happened in the first place.
What we see from the logs is an objectrefence error, and this seems to occur constantly
This is received by the ingress informer and it's just an event. This only triggers an update.
If you see this it basically means "something" is calling kubectl delete .... on an Ingress
Can you post the log from the pod (feel free to replace any private informations)
@aledbf thanks for getting back. Yes there was a helm delete that triggered multiple deletes, however this was done for a specific webapplication in a namespace, and it seemed to have triggered updates/changes to the unrelated apps running in other namespaces.
Assuming you want logs from the ingress controller, ive attached more logs. logs.txt
ss controller pods.
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
Event(v1.ObjectReference, wrap.go:42] PATCH
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
NGINX Ingress controller version:
0.11.0
Kubernetes version (use
kubectl version
):1.8.5
Environment:
Production
uname -a
):What happened:
We noticed an outage in our beta production environment. Basically, there was a helm based deployment that happened around 12:34:34, that seemed to have triggered the ingress watch & reloads, which then triggered delete on few of the ingresses of certain services. What we see from the logs is an objectrefence error, and this seems to occur constantly. It feels as if ingress-controller is constantly trying to delete these ingresses and failing due to object reference error. This happened for a few hours, during that time there were multiple ingress reloads triggered and the apps stopped responding/ were timing out.
This was resolved by deleting some of the ingresses and redeploying an app, but we want to see why this could have happened in the first place.
What you expected to happen:
Expect the ingress deletion to have completed and proceeded with the next updates
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
The text was updated successfully, but these errors were encountered: