apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-223-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-223.ec2.internal uid: 82d96af8-7fc5-4387-9ec3-64167c47e974 resourceVersion: "60648" uid: 97fa4b76-ec09-494c-8b8a-113ae92686b3 spec: sourcePod: network-check-source-869dcfcdcd-gdgjm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T17:41:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 883.77µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:16:58Z" - latency: 1.393169ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:15:58Z" - latency: 1.059356ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:14:58Z" - latency: 909.001µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:13:58Z" - latency: 1.272876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:12:58Z" - latency: 1.508726ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:11:58Z" - latency: 1.063148ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:10:58Z" - latency: 1.421069ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:09:58Z" - latency: 1.123228ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:08:58Z" - latency: 1.027456ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:07:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-223-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-223.ec2.internal uid: 82d96af8-7fc5-4387-9ec3-64167c47e974 resourceVersion: "60650" uid: e098c8ee-74ea-49f4-bf04-1bf8b3afefae spec: sourcePod: network-check-source-869dcfcdcd-gdgjm targetEndpoint: a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T17:40:58Z" message: 'load-balancer-api-external: tcp connection to a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.497385ms message: 'load-balancer-api-external: tcp connection to a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:16:58Z" - latency: 8.231416ms message: 'load-balancer-api-external: resolved host name a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:16:58Z" - latency: 4.525093ms message: 'load-balancer-api-external: tcp connection to a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:15:58Z" - latency: 6.309603ms message: 'load-balancer-api-external: resolved host name a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:15:58Z" - latency: 4.426662ms message: 'load-balancer-api-external: tcp connection to a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:14:58Z" - latency: 7.987807ms message: 'load-balancer-api-external: resolved host name a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:14:58Z" - latency: 4.351675ms message: 'load-balancer-api-external: tcp connection to a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:13:58Z" - latency: 6.829414ms message: 'load-balancer-api-external: resolved host name a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:13:58Z" - latency: 5.045547ms message: 'load-balancer-api-external: tcp connection to a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:12:58Z" - latency: 7.169664ms message: 'load-balancer-api-external: resolved host name a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:12:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-223-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-223.ec2.internal uid: 82d96af8-7fc5-4387-9ec3-64167c47e974 resourceVersion: "60649" uid: 5a1f4d51-b635-429f-9611-0f67f424b2d3 spec: sourcePod: network-check-source-869dcfcdcd-gdgjm targetEndpoint: a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T17:40:58Z" message: 'load-balancer-api-internal: tcp connection to a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.484474ms message: 'load-balancer-api-internal: tcp connection to a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:16:58Z" - latency: 8.141176ms message: 'load-balancer-api-internal: resolved host name a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:16:58Z" - latency: 4.218416ms message: 'load-balancer-api-internal: tcp connection to a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:15:58Z" - latency: 6.192443ms message: 'load-balancer-api-internal: resolved host name a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:15:58Z" - latency: 4.842066ms message: 'load-balancer-api-internal: tcp connection to a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:14:58Z" - latency: 7.943915ms message: 'load-balancer-api-internal: resolved host name a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:14:58Z" - latency: 4.357292ms message: 'load-balancer-api-internal: tcp connection to a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:13:58Z" - latency: 6.764216ms message: 'load-balancer-api-internal: resolved host name a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:13:58Z" - latency: 5.080442ms message: 'load-balancer-api-internal: tcp connection to a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:12:58Z" - latency: 7.13264ms message: 'load-balancer-api-internal: resolved host name a930264f6dcad478a84a156a02b8d49a-2ef7313d757b7214.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:12:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-223-to-network-check-target-ip-10-0-137-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-223.ec2.internal uid: 82d96af8-7fc5-4387-9ec3-64167c47e974 resourceVersion: "60644" uid: 5740805c-280c-4025-bb4f-1fd3cacd1232 spec: sourcePod: network-check-source-869dcfcdcd-gdgjm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T17:41:58Z" message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 781.832µs message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:16:58Z" - latency: 1.019566ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:15:58Z" - latency: 1.260258ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:14:58Z" - latency: 894.28µs message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:13:58Z" - latency: 1.020877ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:12:58Z" - latency: 795.346µs message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:11:58Z" - latency: 967.735µs message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:10:58Z" - latency: 892.865µs message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:09:58Z" - latency: 910.153µs message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:08:58Z" - latency: 1.00095ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:07:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-223-to-network-check-target-ip-10-0-139-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-223.ec2.internal uid: 82d96af8-7fc5-4387-9ec3-64167c47e974 resourceVersion: "60646" uid: 940ef588-3b4d-41b3-9a7e-04271aa4a158 spec: sourcePod: network-check-source-869dcfcdcd-gdgjm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-13T17:41:58Z" message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.550727ms message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:16:58Z" - latency: 2.609107ms message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:15:58Z" - latency: 2.35542ms message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:14:58Z" - latency: 1.956258ms message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:13:58Z" - latency: 2.443882ms message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:12:58Z" - latency: 2.268933ms message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:11:58Z" - latency: 2.068467ms message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:10:58Z" - latency: 2.26197ms message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:09:58Z" - latency: 2.478029ms message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:08:58Z" - latency: 2.240641ms message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:07:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-223-to-network-check-target-ip-10-0-142-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-223.ec2.internal uid: 82d96af8-7fc5-4387-9ec3-64167c47e974 resourceVersion: "60645" uid: bdeb6736-d9d8-4e1e-a642-0419e5501ae3 spec: sourcePod: network-check-source-869dcfcdcd-gdgjm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-13T17:41:58Z" message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.167631ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:16:58Z" - latency: 2.287922ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:15:58Z" - latency: 2.372568ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:14:58Z" - latency: 2.264191ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:13:58Z" - latency: 2.478221ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:12:58Z" - latency: 2.268449ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:11:58Z" - latency: 2.655979ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:10:58Z" - latency: 2.554892ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:09:58Z" - latency: 2.595311ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:08:58Z" - latency: 2.550147ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:07:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-223-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-223.ec2.internal uid: 82d96af8-7fc5-4387-9ec3-64167c47e974 resourceVersion: "60647" uid: 4c08a62c-379c-4c9b-8afa-46c3aed98c24 spec: sourcePod: network-check-source-869dcfcdcd-gdgjm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T17:40:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 879.201µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:16:58Z" - latency: 2.014274ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:16:58Z" - latency: 1.076784ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:15:58Z" - latency: 1.674177ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:15:58Z" - latency: 776.367µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:14:58Z" - latency: 1.831449ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:14:58Z" - latency: 893.422µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:13:58Z" - latency: 1.878098ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:13:58Z" - latency: 824.268µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:12:58Z" - latency: 1.710497ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:12:58Z" kind: List metadata: resourceVersion: ""