apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:58:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-114-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-114.ec2.internal uid: 4a351a48-cdfa-4cbf-8995-5d9e02fc2cf9 resourceVersion: "70379" uid: 88c9bb60-259f-4174-a03c-0777d0344a43 spec: sourcePod: network-check-source-7d88cb55d8-p59jd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T22:05:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.196759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:47:14Z" - latency: 1.035274ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:46:14Z" - latency: 1.217593ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:45:14Z" - latency: 1.044419ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:44:14Z" - latency: 1.396496ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:43:14Z" - latency: 953.033µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:42:14Z" - latency: 1.16247ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:41:14Z" - latency: 991.108µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:40:14Z" - latency: 1.203896ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:39:14Z" - latency: 1.047387ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:38:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:58:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-114-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-114.ec2.internal uid: 4a351a48-cdfa-4cbf-8995-5d9e02fc2cf9 resourceVersion: "69473" uid: cf9c477b-3e05-486a-8b38-5ae76b05f35e spec: sourcePod: network-check-source-7d88cb55d8-p59jd targetEndpoint: a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T22:04:14Z" message: 'load-balancer-api-external: tcp connection to a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.303208ms message: 'load-balancer-api-external: tcp connection to a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:46:14Z" - latency: 9.017566ms message: 'load-balancer-api-external: resolved host name a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:46:14Z" - latency: 5.627041ms message: 'load-balancer-api-external: tcp connection to a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:45:14Z" - latency: 8.595843ms message: 'load-balancer-api-external: resolved host name a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:45:14Z" - latency: 4.674478ms message: 'load-balancer-api-external: tcp connection to a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:44:14Z" - latency: 8.888316ms message: 'load-balancer-api-external: resolved host name a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:44:14Z" - latency: 3.670427ms message: 'load-balancer-api-external: tcp connection to a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:43:14Z" - latency: 8.535879ms message: 'load-balancer-api-external: resolved host name a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:43:14Z" - latency: 4.148481ms message: 'load-balancer-api-external: tcp connection to a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:42:14Z" - latency: 8.74721ms message: 'load-balancer-api-external: resolved host name a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:42:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:58:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-114-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-114.ec2.internal uid: 4a351a48-cdfa-4cbf-8995-5d9e02fc2cf9 resourceVersion: "69472" uid: 49323704-fb10-4cf8-ae99-67806930f9d0 spec: sourcePod: network-check-source-7d88cb55d8-p59jd targetEndpoint: a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T22:04:14Z" message: 'load-balancer-api-internal: tcp connection to a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.147603ms message: 'load-balancer-api-internal: tcp connection to a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:46:14Z" - latency: 8.987456ms message: 'load-balancer-api-internal: resolved host name a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:46:14Z" - latency: 5.60856ms message: 'load-balancer-api-internal: tcp connection to a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:45:14Z" - latency: 8.559049ms message: 'load-balancer-api-internal: resolved host name a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:45:14Z" - latency: 5.507416ms message: 'load-balancer-api-internal: tcp connection to a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:44:14Z" - latency: 8.839086ms message: 'load-balancer-api-internal: resolved host name a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:44:14Z" - latency: 4.259992ms message: 'load-balancer-api-internal: tcp connection to a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:43:14Z" - latency: 8.479385ms message: 'load-balancer-api-internal: resolved host name a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:43:14Z" - latency: 4.300553ms message: 'load-balancer-api-internal: tcp connection to a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:42:14Z" - latency: 8.722717ms message: 'load-balancer-api-internal: resolved host name a74884872aa8449c290395f873793007-38248ffdf191ff36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:42:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:58:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-114-to-network-check-target-ip-10-0-134-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-114.ec2.internal uid: 4a351a48-cdfa-4cbf-8995-5d9e02fc2cf9 resourceVersion: "70376" uid: f41ff767-020e-4311-b380-c51609d6783e spec: sourcePod: network-check-source-7d88cb55d8-p59jd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T22:05:14Z" message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.350642ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:47:14Z" - latency: 2.486311ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:46:14Z" - latency: 2.544864ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:45:14Z" - latency: 2.17183ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:44:14Z" - latency: 2.334492ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:43:14Z" - latency: 2.303194ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:42:14Z" - latency: 2.416749ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:41:14Z" - latency: 2.398341ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:40:14Z" - latency: 2.53276ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:39:14Z" - latency: 2.161798ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:38:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:58:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-114-to-network-check-target-ip-10-0-136-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-114.ec2.internal uid: 4a351a48-cdfa-4cbf-8995-5d9e02fc2cf9 resourceVersion: "70378" uid: 2bb481bd-4191-4b04-bd7e-b392dd4a50cc spec: sourcePod: network-check-source-7d88cb55d8-p59jd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T22:05:14Z" message: 'network-check-target-ip-10-0-136-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.259025ms message: 'network-check-target-ip-10-0-136-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:47:14Z" - latency: 1.990766ms message: 'network-check-target-ip-10-0-136-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:46:14Z" - latency: 2.062656ms message: 'network-check-target-ip-10-0-136-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:45:14Z" - latency: 1.879314ms message: 'network-check-target-ip-10-0-136-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:44:14Z" - latency: 2.241805ms message: 'network-check-target-ip-10-0-136-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:43:14Z" - latency: 2.567672ms message: 'network-check-target-ip-10-0-136-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:42:14Z" - latency: 2.551617ms message: 'network-check-target-ip-10-0-136-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:41:14Z" - latency: 2.525498ms message: 'network-check-target-ip-10-0-136-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:40:14Z" - latency: 2.039553ms message: 'network-check-target-ip-10-0-136-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:39:14Z" - latency: 1.969803ms message: 'network-check-target-ip-10-0-136-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:38:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:58:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-114-to-network-check-target-ip-10-0-140-114 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-114.ec2.internal uid: 4a351a48-cdfa-4cbf-8995-5d9e02fc2cf9 resourceVersion: "70375" uid: d3c0e15f-1958-4cdc-8a11-fc9ca5563b49 spec: sourcePod: network-check-source-7d88cb55d8-p59jd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T22:05:14Z" message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 939.472µs message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:47:14Z" - latency: 1.372469ms message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:46:14Z" - latency: 887.135µs message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:45:14Z" - latency: 801.888µs message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:44:14Z" - latency: 1.108333ms message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:43:14Z" - latency: 950.994µs message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:42:14Z" - latency: 1.019313ms message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:41:14Z" - latency: 809.585µs message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:40:14Z" - latency: 882.385µs message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:39:14Z" - latency: 866.445µs message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:38:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:58:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-114-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-114.ec2.internal uid: 4a351a48-cdfa-4cbf-8995-5d9e02fc2cf9 resourceVersion: "69471" uid: 883b4580-93f9-43f2-b028-4c6b92a9c13a spec: sourcePod: network-check-source-7d88cb55d8-p59jd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T22:04:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 900.45µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:46:14Z" - latency: 1.810089ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:46:14Z" - latency: 908.798µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:45:14Z" - latency: 2.002854ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:45:14Z" - latency: 935.071µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:44:14Z" - latency: 2.149625ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:44:14Z" - latency: 1.189248ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:43:14Z" - latency: 1.975595ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:43:14Z" - latency: 1.088489ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:42:14Z" - latency: 1.761095ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:42:14Z" kind: List metadata: resourceVersion: ""