apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:00:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-72-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-72.ec2.internal uid: 8d9c7bc0-8292-47e6-927c-1c0fb9071cd7 resourceVersion: "44502" uid: e505d0f7-fc3e-461f-b0eb-bee4b239e735 spec: sourcePod: network-check-source-dbd9cf844-fvdkr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T15:07:50Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 862.12µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:28:50Z" - latency: 1.088787ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:27:50Z" - latency: 1.256856ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:26:50Z" - latency: 810.014µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:25:50Z" - latency: 1.659291ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:24:50Z" - latency: 825.386µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:23:50Z" - latency: 1.049385ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:22:50Z" - latency: 854.366µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:21:50Z" - latency: 1.074285ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:20:50Z" - latency: 1.409036ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:19:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:00:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-72-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-72.ec2.internal uid: 8d9c7bc0-8292-47e6-927c-1c0fb9071cd7 resourceVersion: "46505" uid: f3a594c9-d3f3-4384-91a0-ace41be52137 spec: sourcePod: network-check-source-dbd9cf844-fvdkr targetEndpoint: a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T15:06:50Z" message: 'load-balancer-api-external: tcp connection to a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.651112ms message: 'load-balancer-api-external: tcp connection to a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:30:50Z" - latency: 7.810992ms message: 'load-balancer-api-external: resolved host name a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:30:50Z" - latency: 7.326679ms message: 'load-balancer-api-external: tcp connection to a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:29:50Z" - latency: 6.828475ms message: 'load-balancer-api-external: resolved host name a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:29:50Z" - latency: 3.687908ms message: 'load-balancer-api-external: tcp connection to a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:28:50Z" - latency: 6.896624ms message: 'load-balancer-api-external: resolved host name a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:28:50Z" - latency: 5.81339ms message: 'load-balancer-api-external: tcp connection to a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:27:50Z" - latency: 6.383743ms message: 'load-balancer-api-external: resolved host name a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:27:50Z" - latency: 4.654824ms message: 'load-balancer-api-external: tcp connection to a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:26:50Z" - latency: 6.668329ms message: 'load-balancer-api-external: resolved host name a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:26:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:00:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-72-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-72.ec2.internal uid: 8d9c7bc0-8292-47e6-927c-1c0fb9071cd7 resourceVersion: "46506" uid: d8b6d86f-7a54-4be0-8b48-1592fba4614a spec: sourcePod: network-check-source-dbd9cf844-fvdkr targetEndpoint: a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T15:06:50Z" message: 'load-balancer-api-internal: tcp connection to a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.799925ms message: 'load-balancer-api-internal: tcp connection to a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:30:50Z" - latency: 7.783112ms message: 'load-balancer-api-internal: resolved host name a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:30:50Z" - latency: 6.06648ms message: 'load-balancer-api-internal: tcp connection to a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:29:50Z" - latency: 6.86468ms message: 'load-balancer-api-internal: resolved host name a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:29:50Z" - latency: 3.719219ms message: 'load-balancer-api-internal: tcp connection to a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:28:50Z" - latency: 6.858352ms message: 'load-balancer-api-internal: resolved host name a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:28:50Z" - latency: 5.778761ms message: 'load-balancer-api-internal: tcp connection to a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:27:50Z" - latency: 6.459075ms message: 'load-balancer-api-internal: resolved host name a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:27:50Z" - latency: 4.658822ms message: 'load-balancer-api-internal: tcp connection to a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:26:50Z" - latency: 6.691491ms message: 'load-balancer-api-internal: resolved host name a2415a6f59a6f4b019301a88ef79a6a1-5dfd1d8064e0eec5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:26:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:00:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-72-to-network-check-target-ip-10-0-130-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-72.ec2.internal uid: 8d9c7bc0-8292-47e6-927c-1c0fb9071cd7 resourceVersion: "44500" uid: cecbf2ba-9464-4295-910e-d2832ec84f88 spec: sourcePod: network-check-source-dbd9cf844-fvdkr targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-10T15:07:50Z" message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.038016ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:28:50Z" - latency: 1.885312ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:27:50Z" - latency: 1.984694ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:26:50Z" - latency: 1.929342ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:25:50Z" - latency: 2.164261ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:24:50Z" - latency: 1.957385ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:23:50Z" - latency: 1.9881ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:22:50Z" - latency: 2.059651ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:21:50Z" - latency: 1.942813ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:20:50Z" - latency: 1.919321ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:19:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:00:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-72-to-network-check-target-ip-10-0-138-72 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-72.ec2.internal uid: 8d9c7bc0-8292-47e6-927c-1c0fb9071cd7 resourceVersion: "44499" uid: 20bae9b9-12f3-44e4-a03b-2144a7414820 spec: sourcePod: network-check-source-dbd9cf844-fvdkr targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T15:07:50Z" message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.140271ms message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:28:50Z" - latency: 906.508µs message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:27:50Z" - latency: 1.063184ms message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:26:50Z" - latency: 1.483136ms message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:25:50Z" - latency: 1.018306ms message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:24:50Z" - latency: 892.453µs message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:23:50Z" - latency: 1.199096ms message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:22:50Z" - latency: 1.104538ms message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:21:50Z" - latency: 1.00559ms message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:20:50Z" - latency: 1.826763ms message: 'network-check-target-ip-10-0-138-72: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:19:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:00:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-72-to-network-check-target-ip-10-0-140-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-72.ec2.internal uid: 8d9c7bc0-8292-47e6-927c-1c0fb9071cd7 resourceVersion: "44501" uid: 29b5e50d-83e4-418d-a5da-a808a08f23bf spec: sourcePod: network-check-source-dbd9cf844-fvdkr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-10T15:07:50Z" message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.046837ms message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:28:50Z" - latency: 2.189738ms message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:27:50Z" - latency: 2.356394ms message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:26:50Z" - latency: 2.44552ms message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:25:50Z" - latency: 2.304753ms message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:24:50Z" - latency: 2.3128ms message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:23:50Z" - latency: 2.265488ms message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:22:50Z" - latency: 2.272842ms message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:21:50Z" - latency: 2.405788ms message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:20:50Z" - latency: 2.334055ms message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:19:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:00:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-72-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-72.ec2.internal uid: 8d9c7bc0-8292-47e6-927c-1c0fb9071cd7 resourceVersion: "46504" uid: d6d1ddb7-b466-47aa-8fa7-4e3b1f9520fb spec: sourcePod: network-check-source-dbd9cf844-fvdkr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T15:06:50Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 939.74µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:30:50Z" - latency: 1.554129ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T15:30:50Z" - latency: 955.929µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:29:50Z" - latency: 1.716602ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T15:29:50Z" - latency: 858.059µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:28:50Z" - latency: 1.995446ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T15:28:50Z" - latency: 926.006µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:27:50Z" - latency: 1.569034ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T15:27:50Z" - latency: 877.185µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:26:50Z" - latency: 1.605073ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T15:26:50Z" kind: List metadata: resourceVersion: ""