apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:17:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-234-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-234.ec2.internal uid: 906573f7-6233-49ad-8c1e-daae9b914b4e resourceVersion: "33382" uid: fafaab3b-a15b-4f34-b13d-d017754aba9e spec: sourcePod: network-check-source-685456655f-5h772 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T20:24:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 931.771µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:59:59Z" - latency: 854.759µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:58:59Z" - latency: 830.122µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:57:59Z" - latency: 1.103988ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:56:59Z" - latency: 866.676µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:55:59Z" - latency: 1.417076ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:54:59Z" - latency: 1.153751ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:53:59Z" - latency: 812.119µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:52:59Z" - latency: 1.026457ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:51:59Z" - latency: 899.951µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:50:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:17:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-234-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-234.ec2.internal uid: 906573f7-6233-49ad-8c1e-daae9b914b4e resourceVersion: "33383" uid: e87a7a0e-d509-4876-904c-01dc143538cc spec: sourcePod: network-check-source-685456655f-5h772 targetEndpoint: aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:23:59Z" message: 'load-balancer-api-external: tcp connection to aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.178444ms message: 'load-balancer-api-external: tcp connection to aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:59:59Z" - latency: 6.795096ms message: 'load-balancer-api-external: resolved host name aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:59:59Z" - latency: 5.580457ms message: 'load-balancer-api-external: tcp connection to aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:58:59Z" - latency: 6.66478ms message: 'load-balancer-api-external: resolved host name aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:58:59Z" - latency: 5.101545ms message: 'load-balancer-api-external: tcp connection to aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:57:59Z" - latency: 7.00498ms message: 'load-balancer-api-external: resolved host name aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:57:59Z" - latency: 4.16227ms message: 'load-balancer-api-external: tcp connection to aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:56:59Z" - latency: 6.052053ms message: 'load-balancer-api-external: resolved host name aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:56:59Z" - latency: 5.224092ms message: 'load-balancer-api-external: tcp connection to aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:55:59Z" - latency: 7.08304ms message: 'load-balancer-api-external: resolved host name aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:55:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:17:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-234-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-234.ec2.internal uid: 906573f7-6233-49ad-8c1e-daae9b914b4e resourceVersion: "33384" uid: ca3ff172-9605-47da-95c0-95a9e6bdfe6a spec: sourcePod: network-check-source-685456655f-5h772 targetEndpoint: aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:23:59Z" message: 'load-balancer-api-internal: tcp connection to aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.110226ms message: 'load-balancer-api-internal: tcp connection to aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:59:59Z" - latency: 6.816273ms message: 'load-balancer-api-internal: resolved host name aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:59:59Z" - latency: 4.81827ms message: 'load-balancer-api-internal: tcp connection to aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:58:59Z" - latency: 6.721452ms message: 'load-balancer-api-internal: resolved host name aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:58:59Z" - latency: 5.12036ms message: 'load-balancer-api-internal: tcp connection to aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:57:59Z" - latency: 7.020154ms message: 'load-balancer-api-internal: resolved host name aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:57:59Z" - latency: 5.900148ms message: 'load-balancer-api-internal: tcp connection to aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:56:59Z" - latency: 6.077251ms message: 'load-balancer-api-internal: resolved host name aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:56:59Z" - latency: 4.511439ms message: 'load-balancer-api-internal: tcp connection to aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:55:59Z" - latency: 7.128638ms message: 'load-balancer-api-internal: resolved host name aba8e1a7068504e86a336d2bff0e82e7-575ffa43588b758c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:55:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:17:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-234-to-network-check-target-ip-10-0-128-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-234.ec2.internal uid: 906573f7-6233-49ad-8c1e-daae9b914b4e resourceVersion: "33380" uid: 3fbf54e4-6218-4b85-bd93-408b56b61975 spec: sourcePod: network-check-source-685456655f-5h772 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:24:59Z" message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.128572ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:59:59Z" - latency: 2.198825ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:58:59Z" - latency: 1.908205ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:57:59Z" - latency: 2.046597ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:56:59Z" - latency: 2.043373ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:55:59Z" - latency: 2.446373ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:54:59Z" - latency: 2.536365ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:53:59Z" - latency: 2.156968ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:52:59Z" - latency: 2.27599ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:51:59Z" - latency: 2.337057ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:50:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:17:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-234-to-network-check-target-ip-10-0-137-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-234.ec2.internal uid: 906573f7-6233-49ad-8c1e-daae9b914b4e resourceVersion: "33378" uid: 037128dc-9d44-43d0-b88f-afd25bfaea5e spec: sourcePod: network-check-source-685456655f-5h772 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:24:59Z" message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 865.928µs message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:59:59Z" - latency: 1.243507ms message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:58:59Z" - latency: 832.16µs message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:57:59Z" - latency: 868.847µs message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:56:59Z" - latency: 895.266µs message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:55:59Z" - latency: 887.269µs message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:54:59Z" - latency: 740.175µs message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:53:59Z" - latency: 713.656µs message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:52:59Z" - latency: 860.112µs message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:51:59Z" - latency: 714.901µs message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:50:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:17:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-234-to-network-check-target-ip-10-0-142-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-234.ec2.internal uid: 906573f7-6233-49ad-8c1e-daae9b914b4e resourceVersion: "33379" uid: c45d5dee-5fac-4318-88f7-985a8dfa9b01 spec: sourcePod: network-check-source-685456655f-5h772 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:24:59Z" message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.866ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:59:59Z" - latency: 1.933348ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:58:59Z" - latency: 1.649506ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:57:59Z" - latency: 1.783281ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:56:59Z" - latency: 1.651138ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:55:59Z" - latency: 1.70098ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:54:59Z" - latency: 1.903392ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:53:59Z" - latency: 1.800402ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:52:59Z" - latency: 1.640031ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:51:59Z" - latency: 1.904725ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:50:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:17:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-234-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-234.ec2.internal uid: 906573f7-6233-49ad-8c1e-daae9b914b4e resourceVersion: "33381" uid: 385b2d83-11bb-4d1e-8824-128fe9391034 spec: sourcePod: network-check-source-685456655f-5h772 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T20:23:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 976.044µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:59:59Z" - latency: 1.746086ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:59:59Z" - latency: 992.301µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:58:59Z" - latency: 1.911154ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:58:59Z" - latency: 1.079049ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:57:59Z" - latency: 1.896399ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:57:59Z" - latency: 964.825µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:56:59Z" - latency: 2.163614ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:56:59Z" - latency: 800.367µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:55:59Z" - latency: 2.003725ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:55:59Z" kind: List metadata: resourceVersion: ""