Igor Shishkin

Swagger Avocado failed: > The swagger JSON file is not referenced from the readme file. readme: [specification/maps/data-plane/readme.md](https://github.com/Azure/azure-rest-api-specs/blob/2b888c4908999f86856446dee444b60fb4677c5a/specification/maps/data-plane/readme.md) json: [Common/preview/2022-09-01-preview/common.json](https://github.com/Azure/azure-rest-api-specs/blob/2b888c4908999f86856446dee444b60fb4677c5a/specification/maps/data-plane/Common/preview/2022-09-01-preview/common.json) This is expected because common.json is only referenced from other Swagger...

This is blocked by https://github.com/Azure/azure-rest-api-specs/pull/20244

Another issue I noticed here with WorkQueue. After the exception reconciler stops doing anything despite changes to K8 resources.

NullReferenceException is caused by ports mismatch in service and ingress specs which makes servicePort variable to be null. E.g. Service spec has: ```yaml ports: - name: https port: 10000 protocol:...

> Exception handling in Reconciler.cs makes me think that single bad ingress prevents others from working. Shall it be moved inside the loop? (https://github.com/microsoft/reverse-proxy/blob/7dbcd58ce86241eec5e9998607f3c805c95c437c/src/Kubernetes.Controller/Services/Reconciler.cs#L57 ) This parts still stands out.

@MihaZupan could you reopen this?

I've published a fix for the issue. What's missing from the fix is the following case: 1. An Ingress is added and successfully applied to YARP configuration. 2. The Ingress...

Also need `get` on `ingresses/status`. Samples don't have it.

Could you please update the title to make the bug searchable? Nevertheless, reposting error stack trace: ``` warn: Yarp.Kubernetes.Controller.Services.Reconciler[0]       Uncaught exception occured while reconciling       System.ArgumentNullException: Value cannot be null. (Parameter...

Also it updates the status of all ingresses in the cluster without `IsYarpIngress` check :(