apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:12:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-116-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-116.ec2.internal uid: 02113a7e-fb65-4185-b1d2-478306fd7ee3 resourceVersion: "53383" uid: 8b82072c-0841-4da7-8f60-017eb01ad5b8 spec: sourcePod: network-check-source-989f8b8dc-wqp9z targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T19:19:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.332742ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:47:51Z" - latency: 1.40668ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:46:51Z" - latency: 1.282287ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:45:51Z" - latency: 1.191729ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:44:51Z" - latency: 1.443748ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:43:51Z" - latency: 1.068959ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:42:51Z" - latency: 2.00774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:41:51Z" - latency: 1.193548ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:40:51Z" - latency: 1.17402ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:39:51Z" - latency: 1.678372ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:38:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:12:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-116-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-116.ec2.internal uid: 02113a7e-fb65-4185-b1d2-478306fd7ee3 resourceVersion: "54228" uid: d609f76c-094c-402d-b8d0-b9b7d871ed6a spec: sourcePod: network-check-source-989f8b8dc-wqp9z targetEndpoint: aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T19:18:51Z" message: 'load-balancer-api-external: tcp connection to aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.680515ms message: 'load-balancer-api-external: tcp connection to aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:48:51Z" - latency: 6.653096ms message: 'load-balancer-api-external: resolved host name aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:48:51Z" - latency: 3.220935ms message: 'load-balancer-api-external: tcp connection to aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:47:51Z" - latency: 8.059109ms message: 'load-balancer-api-external: resolved host name aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:47:51Z" - latency: 4.078004ms message: 'load-balancer-api-external: tcp connection to aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:46:51Z" - latency: 6.165747ms message: 'load-balancer-api-external: resolved host name aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:46:51Z" - latency: 4.312349ms message: 'load-balancer-api-external: tcp connection to aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:45:51Z" - latency: 6.798754ms message: 'load-balancer-api-external: resolved host name aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:45:51Z" - latency: 5.661035ms message: 'load-balancer-api-external: tcp connection to aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:44:51Z" - latency: 6.953471ms message: 'load-balancer-api-external: resolved host name aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:44:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:12:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-116-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-116.ec2.internal uid: 02113a7e-fb65-4185-b1d2-478306fd7ee3 resourceVersion: "54229" uid: afcc4c6e-26ba-4e9a-8319-9ffe7b7967dc spec: sourcePod: network-check-source-989f8b8dc-wqp9z targetEndpoint: aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T19:18:51Z" message: 'load-balancer-api-internal: tcp connection to aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.69465ms message: 'load-balancer-api-internal: tcp connection to aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:48:51Z" - latency: 6.741645ms message: 'load-balancer-api-internal: resolved host name aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:48:51Z" - latency: 3.196667ms message: 'load-balancer-api-internal: tcp connection to aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:47:51Z" - latency: 8.137251ms message: 'load-balancer-api-internal: resolved host name aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:47:51Z" - latency: 5.576798ms message: 'load-balancer-api-internal: tcp connection to aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:46:51Z" - latency: 6.260533ms message: 'load-balancer-api-internal: resolved host name aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:46:51Z" - latency: 4.045572ms message: 'load-balancer-api-internal: tcp connection to aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:45:51Z" - latency: 6.746347ms message: 'load-balancer-api-internal: resolved host name aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:45:51Z" - latency: 4.763063ms message: 'load-balancer-api-internal: tcp connection to aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:44:51Z" - latency: 7.058771ms message: 'load-balancer-api-internal: resolved host name aa89470511daa4239ab2797348e94b66-fe0fc3bc61751b4b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:44:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:12:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-116-to-network-check-target-ip-10-0-136-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-116.ec2.internal uid: 02113a7e-fb65-4185-b1d2-478306fd7ee3 resourceVersion: "53380" uid: bf73081c-d6e1-46a7-89cd-cd1a9d7400dd spec: sourcePod: network-check-source-989f8b8dc-wqp9z targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T19:19:51Z" message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.112853ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:47:51Z" - latency: 2.132834ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:46:51Z" - latency: 1.731279ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:45:51Z" - latency: 2.075516ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:44:51Z" - latency: 1.770151ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:43:51Z" - latency: 2.035702ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:42:51Z" - latency: 2.256404ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:41:51Z" - latency: 2.082268ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:40:51Z" - latency: 1.970137ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:39:51Z" - latency: 2.063366ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:38:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:12:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-116-to-network-check-target-ip-10-0-141-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-116.ec2.internal uid: 02113a7e-fb65-4185-b1d2-478306fd7ee3 resourceVersion: "53381" uid: de8f41b3-6222-4539-8d5a-e5ec80678d7c spec: sourcePod: network-check-source-989f8b8dc-wqp9z targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T19:19:51Z" message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.078689ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:47:51Z" - latency: 1.912533ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:46:51Z" - latency: 3.320315ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:45:51Z" - latency: 2.006436ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:44:51Z" - latency: 1.816935ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:43:51Z" - latency: 1.871933ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:42:51Z" - latency: 1.887517ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:41:51Z" - latency: 1.803044ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:40:51Z" - latency: 2.039891ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:39:51Z" - latency: 2.707641ms message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:38:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:12:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-116-to-network-check-target-ip-10-0-142-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-116.ec2.internal uid: 02113a7e-fb65-4185-b1d2-478306fd7ee3 resourceVersion: "53382" uid: d80131fa-08fc-4d6f-9697-3e4b50b9e4ed spec: sourcePod: network-check-source-989f8b8dc-wqp9z targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T19:19:51Z" message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 998.596µs message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:47:51Z" - latency: 1.01468ms message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:46:51Z" - latency: 1.026364ms message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:45:51Z" - latency: 1.330774ms message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:44:51Z" - latency: 1.70651ms message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:43:51Z" - latency: 950.23µs message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:42:51Z" - latency: 860.498µs message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:41:51Z" - latency: 1.530082ms message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:40:51Z" - latency: 1.099491ms message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:39:51Z" - latency: 949.751µs message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:38:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:12:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-116-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-116.ec2.internal uid: 02113a7e-fb65-4185-b1d2-478306fd7ee3 resourceVersion: "54226" uid: 728a52af-f3d5-48d3-846b-90feaaef9ccb spec: sourcePod: network-check-source-989f8b8dc-wqp9z targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T19:18:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 831.616µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:48:51Z" - latency: 2.096217ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:48:51Z" - latency: 859.295µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:47:51Z" - latency: 2.035106ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:47:51Z" - latency: 1.094598ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:46:51Z" - latency: 1.85994ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:46:51Z" - latency: 994.667µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:45:51Z" - latency: 1.786331ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:45:51Z" - latency: 1.033732ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:44:51Z" - latency: 1.71115ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:44:51Z" kind: List metadata: resourceVersion: ""