apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-237-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-237.ec2.internal uid: c72500aa-7450-44b3-90df-43ced9601e12 resourceVersion: "22657" uid: 38d26e6f-7b22-4fab-9ca9-c5a1e975a3df spec: sourcePod: network-check-source-65bdbbff45-2txjf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T18:10:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 864.319µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:24:38Z" - latency: 1.086486ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:23:38Z" - latency: 892.014µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:22:38Z" - latency: 792.97µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:21:38Z" - latency: 751.686µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:20:38Z" - latency: 943.965µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:19:38Z" - latency: 890.164µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:18:38Z" - latency: 890.677µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:17:38Z" - latency: 843.745µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:16:38Z" - latency: 1.192578ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:15:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-237-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-237.ec2.internal uid: c72500aa-7450-44b3-90df-43ced9601e12 resourceVersion: "21184" uid: 5b083cdf-ee87-44f3-979d-c35b0603371d spec: sourcePod: network-check-source-65bdbbff45-2txjf targetEndpoint: aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T18:09:38Z" message: 'load-balancer-api-external: tcp connection to aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.389516ms message: 'load-balancer-api-external: tcp connection to aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:21:38Z" - latency: 8.412418ms message: 'load-balancer-api-external: resolved host name aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:21:38Z" - latency: 5.012515ms message: 'load-balancer-api-external: tcp connection to aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:20:38Z" - latency: 8.092253ms message: 'load-balancer-api-external: resolved host name aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:20:38Z" - latency: 5.547379ms message: 'load-balancer-api-external: tcp connection to aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:19:38Z" - latency: 7.935579ms message: 'load-balancer-api-external: resolved host name aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:19:38Z" - latency: 5.068592ms message: 'load-balancer-api-external: tcp connection to aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:18:38Z" - latency: 7.794813ms message: 'load-balancer-api-external: resolved host name aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:18:38Z" - latency: 5.367382ms message: 'load-balancer-api-external: tcp connection to aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:17:38Z" - latency: 7.424024ms message: 'load-balancer-api-external: resolved host name aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:17:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-237-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-237.ec2.internal uid: c72500aa-7450-44b3-90df-43ced9601e12 resourceVersion: "21183" uid: eee47405-2791-4874-8d4d-5405f8e0dc50 spec: sourcePod: network-check-source-65bdbbff45-2txjf targetEndpoint: aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T18:09:38Z" message: 'load-balancer-api-internal: tcp connection to aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.423464ms message: 'load-balancer-api-internal: tcp connection to aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:21:38Z" - latency: 8.442569ms message: 'load-balancer-api-internal: resolved host name aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:21:38Z" - latency: 4.273603ms message: 'load-balancer-api-internal: tcp connection to aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:20:38Z" - latency: 8.189164ms message: 'load-balancer-api-internal: resolved host name aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:20:38Z" - latency: 5.527861ms message: 'load-balancer-api-internal: tcp connection to aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:19:38Z" - latency: 7.987703ms message: 'load-balancer-api-internal: resolved host name aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:19:38Z" - latency: 5.024905ms message: 'load-balancer-api-internal: tcp connection to aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:18:38Z" - latency: 7.849802ms message: 'load-balancer-api-internal: resolved host name aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:18:38Z" - latency: 5.353678ms message: 'load-balancer-api-internal: tcp connection to aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:17:38Z" - latency: 7.523927ms message: 'load-balancer-api-internal: resolved host name aca7f8fa9a1bb4c3d8246f8354ad9f18-f90a26d5c6137d70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:17:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-237-to-network-check-target-ip-10-0-128-51 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-237.ec2.internal uid: c72500aa-7450-44b3-90df-43ced9601e12 resourceVersion: "22656" uid: 55643070-c307-40ee-846a-1aede2e7ff3b spec: sourcePod: network-check-source-65bdbbff45-2txjf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:10:38Z" message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.14456ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:24:38Z" - latency: 2.089533ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:23:38Z" - latency: 2.073757ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:22:38Z" - latency: 2.216561ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:21:38Z" - latency: 1.885177ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:20:38Z" - latency: 2.671136ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:19:38Z" - latency: 2.546271ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:18:38Z" - latency: 2.257241ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:17:38Z" - latency: 2.13038ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:16:38Z" - latency: 2.314164ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:15:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-237-to-network-check-target-ip-10-0-139-237 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-237.ec2.internal uid: c72500aa-7450-44b3-90df-43ced9601e12 resourceVersion: "22654" uid: 15aafe94-54cd-48b5-a5af-db06b8a7ba8e spec: sourcePod: network-check-source-65bdbbff45-2txjf targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:10:38Z" message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.235511ms message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:24:38Z" - latency: 725.873µs message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:23:38Z" - latency: 773.974µs message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:22:38Z" - latency: 875.996µs message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:21:38Z" - latency: 739.016µs message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:20:38Z" - latency: 956.91µs message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:19:38Z" - latency: 936.476µs message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:18:38Z" - latency: 871.044µs message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:17:38Z" - latency: 1.005555ms message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:16:38Z" - latency: 1.504776ms message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:15:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-237-to-network-check-target-ip-10-0-140-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-237.ec2.internal uid: c72500aa-7450-44b3-90df-43ced9601e12 resourceVersion: "22655" uid: 6d67eb7a-368b-44e6-9671-9fc7bef14bb0 spec: sourcePod: network-check-source-65bdbbff45-2txjf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:10:38Z" message: 'network-check-target-ip-10-0-140-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.2441ms message: 'network-check-target-ip-10-0-140-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:24:38Z" - latency: 2.503577ms message: 'network-check-target-ip-10-0-140-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:23:38Z" - latency: 2.216613ms message: 'network-check-target-ip-10-0-140-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:22:38Z" - latency: 2.290475ms message: 'network-check-target-ip-10-0-140-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:21:38Z" - latency: 2.346263ms message: 'network-check-target-ip-10-0-140-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:20:38Z" - latency: 2.628675ms message: 'network-check-target-ip-10-0-140-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:19:38Z" - latency: 2.412955ms message: 'network-check-target-ip-10-0-140-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:18:38Z" - latency: 2.286977ms message: 'network-check-target-ip-10-0-140-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:17:38Z" - latency: 2.129878ms message: 'network-check-target-ip-10-0-140-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:16:38Z" - latency: 2.222464ms message: 'network-check-target-ip-10-0-140-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:15:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:03:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-237-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-237.ec2.internal uid: c72500aa-7450-44b3-90df-43ced9601e12 resourceVersion: "21181" uid: b36c8f0d-174d-476f-9797-e76ab61f72c1 spec: sourcePod: network-check-source-65bdbbff45-2txjf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T18:09:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 866.895µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:21:38Z" - latency: 1.981899ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:21:38Z" - latency: 930.88µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:20:38Z" - latency: 1.807835ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:20:38Z" - latency: 908.885µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:19:38Z" - latency: 1.724635ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:19:38Z" - latency: 1.264296ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:18:38Z" - latency: 1.493634ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:18:38Z" - latency: 914.652µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:17:38Z" - latency: 1.866843ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:17:38Z" kind: List metadata: resourceVersion: ""