apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-254-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-254.ec2.internal uid: 9046c8bb-4209-4ceb-b494-8134f2ae45f7 resourceVersion: "32558" uid: 638fa84a-902f-4eac-b101-9220926422ac spec: sourcePod: network-check-source-7cbc45fddc-mpldl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T17:46:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.278219ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:21:54Z" - latency: 974.523µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:20:54Z" - latency: 1.134341ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:19:54Z" - latency: 928.089µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:18:54Z" - latency: 1.377747ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:17:54Z" - latency: 1.53307ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:16:54Z" - latency: 1.257931ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:15:54Z" - latency: 977.574µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:14:54Z" - latency: 1.099786ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:13:54Z" - latency: 1.107369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:12:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-254-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-254.ec2.internal uid: 9046c8bb-4209-4ceb-b494-8134f2ae45f7 resourceVersion: "32560" uid: d4a2c11f-6dfe-42ae-9c1d-df57d342b0bf spec: sourcePod: network-check-source-7cbc45fddc-mpldl targetEndpoint: a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T17:45:54Z" message: 'load-balancer-api-external: tcp connection to a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.641125ms message: 'load-balancer-api-external: tcp connection to a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:21:54Z" - latency: 8.108998ms message: 'load-balancer-api-external: resolved host name a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:21:54Z" - latency: 4.668695ms message: 'load-balancer-api-external: tcp connection to a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:20:54Z" - latency: 7.323353ms message: 'load-balancer-api-external: resolved host name a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:20:54Z" - latency: 4.57115ms message: 'load-balancer-api-external: tcp connection to a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:19:54Z" - latency: 8.63624ms message: 'load-balancer-api-external: resolved host name a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:19:54Z" - latency: 4.508501ms message: 'load-balancer-api-external: tcp connection to a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:18:54Z" - latency: 7.654879ms message: 'load-balancer-api-external: resolved host name a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:18:54Z" - latency: 4.04078ms message: 'load-balancer-api-external: tcp connection to a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:17:54Z" - latency: 8.194132ms message: 'load-balancer-api-external: resolved host name a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:17:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-254-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-254.ec2.internal uid: 9046c8bb-4209-4ceb-b494-8134f2ae45f7 resourceVersion: "32559" uid: 9d18c00a-ab79-4670-928f-955aaf7f8632 spec: sourcePod: network-check-source-7cbc45fddc-mpldl targetEndpoint: a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T17:45:54Z" message: 'load-balancer-api-internal: tcp connection to a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.616719ms message: 'load-balancer-api-internal: tcp connection to a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:21:54Z" - latency: 8.229289ms message: 'load-balancer-api-internal: resolved host name a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:21:54Z" - latency: 4.697698ms message: 'load-balancer-api-internal: tcp connection to a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:20:54Z" - latency: 7.376067ms message: 'load-balancer-api-internal: resolved host name a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:20:54Z" - latency: 4.596886ms message: 'load-balancer-api-internal: tcp connection to a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:19:54Z" - latency: 8.753782ms message: 'load-balancer-api-internal: resolved host name a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:19:54Z" - latency: 4.502595ms message: 'load-balancer-api-internal: tcp connection to a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:18:54Z" - latency: 7.696111ms message: 'load-balancer-api-internal: resolved host name a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:18:54Z" - latency: 4.879455ms message: 'load-balancer-api-internal: tcp connection to a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:17:54Z" - latency: 8.262628ms message: 'load-balancer-api-internal: resolved host name a94840d4c29244e59a6cb29888c37b4c-db45f3d120c12d52.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:17:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-254-to-network-check-target-ip-10-0-133-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-254.ec2.internal uid: 9046c8bb-4209-4ceb-b494-8134f2ae45f7 resourceVersion: "32556" uid: 6a6abea0-d52d-419b-8cb1-0670d5c05bec spec: sourcePod: network-check-source-7cbc45fddc-mpldl targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T17:46:54Z" message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.737142ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:21:54Z" - latency: 2.045223ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:20:54Z" - latency: 2.200953ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:19:54Z" - latency: 2.077178ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:18:54Z" - latency: 2.454757ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:17:54Z" - latency: 2.346767ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:16:54Z" - latency: 2.5464ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:15:54Z" - latency: 2.256804ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:14:54Z" - latency: 2.375753ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:13:54Z" - latency: 2.31035ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:12:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-254-to-network-check-target-ip-10-0-134-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-254.ec2.internal uid: 9046c8bb-4209-4ceb-b494-8134f2ae45f7 resourceVersion: "32554" uid: 00afa542-1a3f-4d91-9cb9-dc4b0d2d2217 spec: sourcePod: network-check-source-7cbc45fddc-mpldl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T17:46:54Z" message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.039929ms message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:21:54Z" - latency: 2.379045ms message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:20:54Z" - latency: 2.560534ms message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:19:54Z" - latency: 2.297837ms message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:18:54Z" - latency: 2.141868ms message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:17:54Z" - latency: 3.027583ms message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:16:54Z" - latency: 2.939279ms message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:15:54Z" - latency: 2.666161ms message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:14:54Z" - latency: 2.381674ms message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:13:54Z" - latency: 2.517323ms message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:12:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-254-to-network-check-target-ip-10-0-139-254 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-254.ec2.internal uid: 9046c8bb-4209-4ceb-b494-8134f2ae45f7 resourceVersion: "32555" uid: 66718334-7b70-4f5b-9df7-e2664d86f807 spec: sourcePod: network-check-source-7cbc45fddc-mpldl targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T17:46:54Z" message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 861.102µs message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:21:54Z" - latency: 1.466457ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:20:54Z" - latency: 1.4653ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:19:54Z" - latency: 1.399814ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:18:54Z" - latency: 881.306µs message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:17:54Z" - latency: 1.490973ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:16:54Z" - latency: 1.474139ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:15:54Z" - latency: 965.298µs message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:14:54Z" - latency: 900.527µs message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:13:54Z" - latency: 1.382776ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:12:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-254-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-254.ec2.internal uid: 9046c8bb-4209-4ceb-b494-8134f2ae45f7 resourceVersion: "32557" uid: d749d256-0072-4d0f-875f-ed6927964454 spec: sourcePod: network-check-source-7cbc45fddc-mpldl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T17:45:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.466713ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:21:54Z" - latency: 1.634076ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:21:54Z" - latency: 863.769µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:20:54Z" - latency: 1.552806ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:20:54Z" - latency: 1.116537ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:19:54Z" - latency: 1.406514ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:19:54Z" - latency: 879.644µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:18:54Z" - latency: 1.627572ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:18:54Z" - latency: 807.413µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:17:54Z" - latency: 1.56503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:17:54Z" kind: List metadata: resourceVersion: ""