Panu Bloigu

I'm getting the exact same exception with a simple Nginx deployment like the following: ``` apiVersion: apps/v1 kind: Deployment metadata: name: nginx-deployment spec: selector: matchLabels: app: nginx-deployment replicas: 2 #...

Alright, I did some more digging into this, and I think there is a bug here: https://github.com/spring-cloud/spring-cloud-kubernetes/blob/ff50c9c2dcfab281bd6c3df8cdd978299e73d165/spring-cloud-kubernetes-client-discovery/src/main/java/org/springframework/cloud/kubernetes/client/discovery/KubernetesInformerDiscoveryClient.java#L151 It seems to assume a service port has a name defined like so...

> @pbloigu thank you! your workaround worked for me, regarding permanent fix we can probably use "default" if `name` does not exist Yeah, well, I really don't have enough insight...

Okay, now this is starting to unfold. The AGIC controller had crashed just prior to the above issue, apparently due to not being able to connect to the K8s API:...

The same error occurs when building image of 23.05.2 for DIR-825-B1. It seems ASU is unusable for this device.

Still the same error when building 23.05.3.

> Hi @pbloigu , are all of your 3 clusters are AKS clusters? Yes they are. Do you have a better approach in mind to achieve what I described that...

Yeah, that would incur additional costs which I'm unable to accept at this time. However, the host names are stable and once defined there won't be any new ones, so...

Or maybe you could prefix the pool and rule names with some cluster specific identifier?