apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T00:12:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: c602512a-8534-49fd-b28e-ed4751816afa resourceVersion: "19619" uid: d204ebe6-c829-4421-bb1c-77f10a1e47fc spec: sourcePod: network-check-source-7f44b6dd87-w8gwf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T00:19:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.015272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:33:35Z" - latency: 678.188µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:32:35Z" - latency: 751.055µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:31:35Z" - latency: 941.621µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:30:35Z" - latency: 838.807µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:29:35Z" - latency: 869.074µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:28:35Z" - latency: 760.043µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:27:35Z" - latency: 789.009µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:26:35Z" - latency: 706.612µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:25:35Z" - latency: 884.607µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:24:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T00:12:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: c602512a-8534-49fd-b28e-ed4751816afa resourceVersion: "20837" uid: 46d38a5b-27e5-465b-aa6f-2fa6166e765e spec: sourcePod: network-check-source-7f44b6dd87-w8gwf targetEndpoint: a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T00:18:35Z" message: 'load-balancer-api-external: tcp connection to a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.280268ms message: 'load-balancer-api-external: tcp connection to a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:36:35Z" - latency: 9.093052ms message: 'load-balancer-api-external: resolved host name a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T00:36:35Z" - latency: 5.456045ms message: 'load-balancer-api-external: tcp connection to a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:35:35Z" - latency: 10.361126ms message: 'load-balancer-api-external: resolved host name a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T00:35:35Z" - latency: 5.886671ms message: 'load-balancer-api-external: tcp connection to a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:34:35Z" - latency: 9.572171ms message: 'load-balancer-api-external: resolved host name a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T00:34:35Z" - latency: 4.813803ms message: 'load-balancer-api-external: tcp connection to a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:33:35Z" - latency: 9.711892ms message: 'load-balancer-api-external: resolved host name a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T00:33:35Z" - latency: 4.887824ms message: 'load-balancer-api-external: tcp connection to a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:32:35Z" - latency: 9.194515ms message: 'load-balancer-api-external: resolved host name a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T00:32:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T00:12:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: c602512a-8534-49fd-b28e-ed4751816afa resourceVersion: "20836" uid: 327ef614-6834-4432-b9ce-9a02a3b4ab5f spec: sourcePod: network-check-source-7f44b6dd87-w8gwf targetEndpoint: a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T00:18:35Z" message: 'load-balancer-api-internal: tcp connection to a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.154919ms message: 'load-balancer-api-internal: tcp connection to a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:36:35Z" - latency: 9.169521ms message: 'load-balancer-api-internal: resolved host name a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T00:36:35Z" - latency: 4.481039ms message: 'load-balancer-api-internal: tcp connection to a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:35:35Z" - latency: 10.440304ms message: 'load-balancer-api-internal: resolved host name a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T00:35:35Z" - latency: 6.948401ms message: 'load-balancer-api-internal: tcp connection to a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:34:35Z" - latency: 9.646267ms message: 'load-balancer-api-internal: resolved host name a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T00:34:35Z" - latency: 4.777515ms message: 'load-balancer-api-internal: tcp connection to a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:33:35Z" - latency: 9.854654ms message: 'load-balancer-api-internal: resolved host name a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T00:33:35Z" - latency: 4.580425ms message: 'load-balancer-api-internal: tcp connection to a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:32:35Z" - latency: 9.269394ms message: 'load-balancer-api-internal: resolved host name a94025c2b72664a5f9622b9e46b6a8de-f8d8d0ab4875f670.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T00:32:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T00:12:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-network-check-target-ip-10-0-131-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: c602512a-8534-49fd-b28e-ed4751816afa resourceVersion: "19617" uid: c5ce7f56-0cdb-48cc-be8d-def19c6360be spec: sourcePod: network-check-source-7f44b6dd87-w8gwf targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T00:19:35Z" message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.883384ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:33:35Z" - latency: 2.021087ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:32:35Z" - latency: 1.653292ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:31:35Z" - latency: 1.837177ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:30:35Z" - latency: 1.975251ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:29:35Z" - latency: 1.898175ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:28:35Z" - latency: 1.701842ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:27:35Z" - latency: 1.849973ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:26:35Z" - latency: 1.779875ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:25:35Z" - latency: 2.012139ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:24:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T00:12:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-network-check-target-ip-10-0-134-90 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: c602512a-8534-49fd-b28e-ed4751816afa resourceVersion: "19618" uid: 1988ae05-0c18-406d-a465-95afaf8c9f31 spec: sourcePod: network-check-source-7f44b6dd87-w8gwf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T00:19:35Z" message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.93682ms message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:33:35Z" - latency: 2.11186ms message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:32:35Z" - latency: 1.961864ms message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:31:35Z" - latency: 2.163763ms message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:30:35Z" - latency: 1.890393ms message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:29:35Z" - latency: 2.181206ms message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:28:35Z" - latency: 2.113127ms message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:27:35Z" - latency: 2.190988ms message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:26:35Z" - latency: 1.589911ms message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:25:35Z" - latency: 2.210363ms message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:24:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T00:12:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-network-check-target-ip-10-0-139-51 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: c602512a-8534-49fd-b28e-ed4751816afa resourceVersion: "19616" uid: cf0dab15-e5e5-4a51-8dc4-8cbf403a3ee8 spec: sourcePod: network-check-source-7f44b6dd87-w8gwf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T00:19:35Z" message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 822.297µs message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:33:35Z" - latency: 1.250795ms message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:32:35Z" - latency: 1.458744ms message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:31:35Z" - latency: 763.803µs message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:30:35Z" - latency: 764.399µs message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:29:35Z" - latency: 856.444µs message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:28:35Z" - latency: 1.027984ms message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:27:35Z" - latency: 776.614µs message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:26:35Z" - latency: 875.173µs message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:25:35Z" - latency: 1.206563ms message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:24:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T00:12:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: c602512a-8534-49fd-b28e-ed4751816afa resourceVersion: "20834" uid: d604df29-3902-4652-a270-9c2523ad78b2 spec: sourcePod: network-check-source-7f44b6dd87-w8gwf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T00:18:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 761.508µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:36:35Z" - latency: 1.793947ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T00:36:35Z" - latency: 967.425µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:35:35Z" - latency: 2.056257ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T00:35:35Z" - latency: 801.119µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:34:35Z" - latency: 1.808665ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T00:34:35Z" - latency: 990.67µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:33:35Z" - latency: 1.829204ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T00:33:35Z" - latency: 805.583µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T00:32:35Z" - latency: 1.400635ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T00:32:35Z" kind: List metadata: resourceVersion: ""