Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"CREATE" ingress events added, when any of the worker node is recycled. #6279

Closed
vijay-veeranki opened this issue Oct 5, 2020 · 3 comments · Fixed by #6375
Closed

"CREATE" ingress events added, when any of the worker node is recycled. #6279

vijay-veeranki opened this issue Oct 5, 2020 · 3 comments · Fixed by #6375
Labels
kind/support Categorizes issue or PR as a support question.

Comments

@vijay-veeranki
Copy link

vijay-veeranki commented Oct 5, 2020

We noticed there are CREATE ingress showing in the namespace events.

Investigated further and identified that these events are added when we recycle any node(terminate a worker node) in our cluster.

Example events:

monitoring              0s          Normal    CREATE                   ingress/alertmanager-proxy-oauth2-proxy                       Ingress monitoring/alertmanager-proxy-oauth2-proxy
kuberos                 0s          Normal    CREATE                   ingress/kuberos                                               Ingress kuberos/kuberos
monitoring              0s          Normal    CREATE                   ingress/prometheus-operator-grafana                           Ingress monitoring/prometheus-operator-grafana
starter-pack            0s          Normal    CREATE                   ingress/helloworld                                            Ingress starter-pack/helloworld
monitoring              0s          Normal    CREATE                   ingress/prometheus-proxy-oauth2-proxy                         Ingress monitoring/prometheus-proxy-oauth2-proxy

This is causing confusion as the actual ingress is not created but this event is created.

@vijay-veeranki vijay-veeranki added the kind/support Categorizes issue or PR as a support question. label Oct 5, 2020
@vijay-veeranki vijay-veeranki changed the title CREATE ingress events far all the ingress in the cluster, when any of the worker node is recycled. CREATE ingress events for all the ingress in the cluster, when any of the worker node is recycled. Oct 5, 2020
@vijay-veeranki vijay-veeranki changed the title CREATE ingress events for all the ingress in the cluster, when any of the worker node is recycled. "CREATE" ingress events added, when any of the worker node is recycled. Oct 5, 2020
@aledbf
Copy link
Member

aledbf commented Oct 5, 2020

This is causing confusion as the actual ingress is not created, but this event is created.

The CREATE is related to the ingress controller, not the ingress definition. That said, I see this could be confusing because of the lack of context.

@vijay-veeranki
Copy link
Author

vijay-veeranki commented Oct 5, 2020

Hi Manuel,

Thanks for your reply, yes it is confusing because that event is showing in the namespace where the ingress is created. Not in the ingress-controller namespace.

Do you know "The CREATE is related to the ingress controller" what does this ingress-controller CREATE process involve?

@aledbf
Copy link
Member

aledbf commented Oct 5, 2020

Do you know "The CREATE is related to the ingress controller" what does this ingress-controller CREATE process involve?

This is related to the client-go informer when an ingress is reported

recorder.Eventf(ing, corev1.EventTypeNormal, "CREATE", fmt.Sprintf("Ingress %s/%s", ing.Namespace, ing.Name))

@aledbf aledbf mentioned this issue Oct 26, 2020
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants