apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T05:52:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.ec2.internal uid: 6a534a93-118c-43d3-97cb-26d491c165c8 resourceVersion: "55285" uid: fcaa5d65-5a90-4e16-a3a8-d03ba178f469 spec: sourcePod: network-check-source-685456655f-4wv9c targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T05:59:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.017869ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:20:37Z" - latency: 942.821µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:19:37Z" - latency: 1.334997ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:18:37Z" - latency: 929.052µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:17:37Z" - latency: 1.223167ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:16:37Z" - latency: 1.16232ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:15:37Z" - latency: 1.250925ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:14:37Z" - latency: 975.746µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:13:37Z" - latency: 1.472724ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:12:37Z" - latency: 1.225845ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:11:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T05:52:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.ec2.internal uid: 6a534a93-118c-43d3-97cb-26d491c165c8 resourceVersion: "57075" uid: 4120123c-effc-4df5-a984-cd927e79ecba spec: sourcePod: network-check-source-685456655f-4wv9c targetEndpoint: ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T05:58:37Z" message: 'load-balancer-api-external: tcp connection to ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.680365ms message: 'load-balancer-api-external: tcp connection to ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:22:37Z" - latency: 7.712426ms message: 'load-balancer-api-external: resolved host name ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T06:22:37Z" - latency: 5.430835ms message: 'load-balancer-api-external: tcp connection to ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:21:37Z" - latency: 10.282218ms message: 'load-balancer-api-external: resolved host name ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T06:21:37Z" - latency: 4.220638ms message: 'load-balancer-api-external: tcp connection to ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:20:37Z" - latency: 7.408613ms message: 'load-balancer-api-external: resolved host name ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T06:20:37Z" - latency: 5.170046ms message: 'load-balancer-api-external: tcp connection to ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:19:37Z" - latency: 7.32614ms message: 'load-balancer-api-external: resolved host name ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T06:19:37Z" - latency: 4.443506ms message: 'load-balancer-api-external: tcp connection to ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:18:37Z" - latency: 6.506103ms message: 'load-balancer-api-external: resolved host name ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T06:18:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T05:52:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.ec2.internal uid: 6a534a93-118c-43d3-97cb-26d491c165c8 resourceVersion: "57076" uid: 0ce64407-f859-4afb-9632-a2cb08d882a5 spec: sourcePod: network-check-source-685456655f-4wv9c targetEndpoint: ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T05:58:37Z" message: 'load-balancer-api-internal: tcp connection to ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.723627ms message: 'load-balancer-api-internal: tcp connection to ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:22:37Z" - latency: 7.744536ms message: 'load-balancer-api-internal: resolved host name ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T06:22:37Z" - latency: 5.35479ms message: 'load-balancer-api-internal: tcp connection to ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:21:37Z" - latency: 10.306433ms message: 'load-balancer-api-internal: resolved host name ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T06:21:37Z" - latency: 5.091353ms message: 'load-balancer-api-internal: tcp connection to ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:20:37Z" - latency: 7.431179ms message: 'load-balancer-api-internal: resolved host name ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T06:20:37Z" - latency: 5.192713ms message: 'load-balancer-api-internal: tcp connection to ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:19:37Z" - latency: 7.230331ms message: 'load-balancer-api-internal: resolved host name ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T06:19:37Z" - latency: 5.105637ms message: 'load-balancer-api-internal: tcp connection to ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:18:37Z" - latency: 6.551527ms message: 'load-balancer-api-internal: resolved host name ac161ca73b37444d080108f699b15958-2c177744b362dbfb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T06:18:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T05:52:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-network-check-target-ip-10-0-131-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.ec2.internal uid: 6a534a93-118c-43d3-97cb-26d491c165c8 resourceVersion: "55284" uid: f25da361-4118-4448-a15b-20c8a3cd2f5b spec: sourcePod: network-check-source-685456655f-4wv9c targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T05:59:37Z" message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.258572ms message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:20:37Z" - latency: 2.256625ms message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:19:37Z" - latency: 2.306042ms message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:18:37Z" - latency: 2.357887ms message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:17:37Z" - latency: 2.162934ms message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:16:37Z" - latency: 2.367443ms message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:15:37Z" - latency: 2.603746ms message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:14:37Z" - latency: 2.026769ms message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:13:37Z" - latency: 3.14696ms message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:12:37Z" - latency: 2.187592ms message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:11:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T05:52:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-network-check-target-ip-10-0-131-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.ec2.internal uid: 6a534a93-118c-43d3-97cb-26d491c165c8 resourceVersion: "55282" uid: ed9ba873-f1c9-4816-a560-e6bfeac07598 spec: sourcePod: network-check-source-685456655f-4wv9c targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T05:59:37Z" message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.006455ms message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:20:37Z" - latency: 1.028278ms message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:19:37Z" - latency: 1.089651ms message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:18:37Z" - latency: 1.053965ms message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:17:37Z" - latency: 903.668µs message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:16:37Z" - latency: 888.062µs message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:15:37Z" - latency: 1.782355ms message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:14:37Z" - latency: 971.298µs message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:13:37Z" - latency: 1.001842ms message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:12:37Z" - latency: 1.029833ms message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:11:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T05:52:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-network-check-target-ip-10-0-138-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.ec2.internal uid: 6a534a93-118c-43d3-97cb-26d491c165c8 resourceVersion: "55283" uid: 0227f716-3540-41e5-bfd2-172f9c79d7db spec: sourcePod: network-check-source-685456655f-4wv9c targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T05:59:37Z" message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.998773ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:20:37Z" - latency: 2.119616ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:19:37Z" - latency: 2.47831ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:18:37Z" - latency: 2.015308ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:17:37Z" - latency: 1.940549ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:16:37Z" - latency: 2.128676ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:15:37Z" - latency: 2.21561ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:14:37Z" - latency: 1.998535ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:13:37Z" - latency: 3.054809ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:12:37Z" - latency: 2.563685ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:11:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T05:52:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.ec2.internal uid: 6a534a93-118c-43d3-97cb-26d491c165c8 resourceVersion: "57074" uid: 1e4b2875-d71e-410f-ba08-71479154f481 spec: sourcePod: network-check-source-685456655f-4wv9c targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T05:58:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 886.419µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:22:37Z" - latency: 2.067228ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T06:22:37Z" - latency: 1.331647ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:21:37Z" - latency: 1.931491ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T06:21:37Z" - latency: 1.337864ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:20:37Z" - latency: 1.89466ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T06:20:37Z" - latency: 1.273115ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:19:37Z" - latency: 1.689591ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T06:19:37Z" - latency: 1.428161ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T06:18:37Z" - latency: 1.891511ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T06:18:37Z" kind: List metadata: resourceVersion: ""