apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:19:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-130-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-130.ec2.internal uid: 87121c58-2ecc-4b13-8871-69360988a3ef resourceVersion: "60560" uid: adfffb71-5ba1-4596-80df-1771266f82ed spec: sourcePod: network-check-source-869dcfcdcd-bp4xd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T17:26:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.300296ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:22:52Z" - latency: 1.125874ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:52Z" - latency: 827.232µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:52Z" - latency: 1.294697ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:52Z" - latency: 1.401662ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:52Z" - latency: 1.580785ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:52Z" - latency: 1.155219ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:52Z" - latency: 1.255686ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:52Z" - latency: 1.251866ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:52Z" - latency: 1.15989ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:19:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-130-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-130.ec2.internal uid: 87121c58-2ecc-4b13-8871-69360988a3ef resourceVersion: "62849" uid: bc3837ad-4342-4bbc-b73a-7e27b543655e spec: sourcePod: network-check-source-869dcfcdcd-bp4xd targetEndpoint: ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:25:52Z" message: 'load-balancer-api-external: tcp connection to ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.325918ms message: 'load-balancer-api-external: tcp connection to ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:25:52Z" - latency: 7.050858ms message: 'load-balancer-api-external: resolved host name ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:25:52Z" - latency: 5.16219ms message: 'load-balancer-api-external: tcp connection to ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:24:52Z" - latency: 7.721366ms message: 'load-balancer-api-external: resolved host name ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:24:52Z" - latency: 4.480773ms message: 'load-balancer-api-external: tcp connection to ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:23:52Z" - latency: 7.465066ms message: 'load-balancer-api-external: resolved host name ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:23:52Z" - latency: 4.383887ms message: 'load-balancer-api-external: tcp connection to ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:22:52Z" - latency: 7.497442ms message: 'load-balancer-api-external: resolved host name ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:22:52Z" - latency: 4.382464ms message: 'load-balancer-api-external: tcp connection to ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:52Z" - latency: 6.939808ms message: 'load-balancer-api-external: resolved host name ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:21:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:19:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-130-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-130.ec2.internal uid: 87121c58-2ecc-4b13-8871-69360988a3ef resourceVersion: "62850" uid: 72a0ffa7-d378-4533-96b0-d93e41f1183b spec: sourcePod: network-check-source-869dcfcdcd-bp4xd targetEndpoint: ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:25:52Z" message: 'load-balancer-api-internal: tcp connection to ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.385137ms message: 'load-balancer-api-internal: tcp connection to ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:25:52Z" - latency: 7.031611ms message: 'load-balancer-api-internal: resolved host name ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:25:52Z" - latency: 4.445909ms message: 'load-balancer-api-internal: tcp connection to ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:24:52Z" - latency: 7.487512ms message: 'load-balancer-api-internal: resolved host name ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:24:52Z" - latency: 3.902027ms message: 'load-balancer-api-internal: tcp connection to ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:23:52Z" - latency: 7.450996ms message: 'load-balancer-api-internal: resolved host name ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:23:52Z" - latency: 4.392663ms message: 'load-balancer-api-internal: tcp connection to ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:22:52Z" - latency: 7.477393ms message: 'load-balancer-api-internal: resolved host name ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:22:52Z" - latency: 3.636939ms message: 'load-balancer-api-internal: tcp connection to ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:52Z" - latency: 6.885938ms message: 'load-balancer-api-internal: resolved host name ad683cc5765bd41568caf2dbd38220a0-0b39a665eecef20c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:21:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:19:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-130-to-network-check-target-ip-10-0-128-42 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-130.ec2.internal uid: 87121c58-2ecc-4b13-8871-69360988a3ef resourceVersion: "60559" uid: 563fd2df-1bdc-426a-b417-6d06e221c5b2 spec: sourcePod: network-check-source-869dcfcdcd-bp4xd targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:26:52Z" message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.24457ms message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:22:52Z" - latency: 2.054416ms message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:52Z" - latency: 1.819524ms message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:52Z" - latency: 2.47796ms message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:52Z" - latency: 2.193377ms message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:52Z" - latency: 2.430971ms message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:52Z" - latency: 1.992935ms message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:52Z" - latency: 2.157268ms message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:52Z" - latency: 2.062969ms message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:52Z" - latency: 2.142602ms message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:19:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-130-to-network-check-target-ip-10-0-132-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-130.ec2.internal uid: 87121c58-2ecc-4b13-8871-69360988a3ef resourceVersion: "60557" uid: 72566b7c-91d3-491d-b26c-9203008e5d86 spec: sourcePod: network-check-source-869dcfcdcd-bp4xd targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:26:52Z" message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.258889ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:22:52Z" - latency: 791.605µs message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:52Z" - latency: 856.634µs message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:52Z" - latency: 916.033µs message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:52Z" - latency: 913.044µs message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:52Z" - latency: 1.734141ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:52Z" - latency: 983.948µs message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:52Z" - latency: 782.802µs message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:52Z" - latency: 1.057775ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:52Z" - latency: 1.415345ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:19:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-130-to-network-check-target-ip-10-0-133-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-130.ec2.internal uid: 87121c58-2ecc-4b13-8871-69360988a3ef resourceVersion: "60558" uid: ca95834c-d0ca-4316-a13c-07658efcdd41 spec: sourcePod: network-check-source-869dcfcdcd-bp4xd targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:26:52Z" message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.282124ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:22:52Z" - latency: 1.931895ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:52Z" - latency: 1.606172ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:52Z" - latency: 1.945723ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:52Z" - latency: 1.729263ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:52Z" - latency: 1.657271ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:52Z" - latency: 1.886743ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:52Z" - latency: 2.133152ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:52Z" - latency: 1.798178ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:52Z" - latency: 1.979117ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:19:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-130-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-130.ec2.internal uid: 87121c58-2ecc-4b13-8871-69360988a3ef resourceVersion: "62848" uid: af5c8e1c-9adf-4a64-a3fe-f8b143637ead spec: sourcePod: network-check-source-869dcfcdcd-bp4xd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T17:25:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 792.633µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:25:52Z" - latency: 2.00292ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:25:52Z" - latency: 1.102441ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:24:52Z" - latency: 2.409918ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:24:52Z" - latency: 898.703µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:23:52Z" - latency: 1.755808ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:23:52Z" - latency: 870.072µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:22:52Z" - latency: 2.281373ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:22:52Z" - latency: 909.599µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:52Z" - latency: 1.824226ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:21:52Z" kind: List metadata: resourceVersion: ""