apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-187-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-187.ec2.internal uid: 491b008f-3a58-4385-92ca-b632286fff95 resourceVersion: "64284" uid: 8bcd1157-1d24-49b5-8912-8b4d762f268c spec: sourcePod: network-check-source-7bc5b6bf85-68drw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T19:36:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 984.717µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:11:14Z" - latency: 952.753µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:10:14Z" - latency: 1.12634ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:09:14Z" - latency: 1.010603ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:08:14Z" - latency: 1.057542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:07:14Z" - latency: 1.525296ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:06:14Z" - latency: 1.462021ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:05:14Z" - latency: 949.99µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:04:14Z" - latency: 1.204401ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:03:14Z" - latency: 1.074111ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:02:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-187-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-187.ec2.internal uid: 491b008f-3a58-4385-92ca-b632286fff95 resourceVersion: "64285" uid: 741b8bf0-b4b6-4c22-be33-5d1cc8c051a3 spec: sourcePod: network-check-source-7bc5b6bf85-68drw targetEndpoint: a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T19:35:14Z" message: 'load-balancer-api-external: tcp connection to a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.721555ms message: 'load-balancer-api-external: tcp connection to a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:11:14Z" - latency: 8.453859ms message: 'load-balancer-api-external: resolved host name a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:11:14Z" - latency: 5.345536ms message: 'load-balancer-api-external: tcp connection to a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:10:14Z" - latency: 14.590974ms message: 'load-balancer-api-external: resolved host name a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:10:14Z" - latency: 27.859602ms message: 'load-balancer-api-external: tcp connection to a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:09:14Z" - latency: 7.550248ms message: 'load-balancer-api-external: resolved host name a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:09:14Z" - latency: 5.005711ms message: 'load-balancer-api-external: tcp connection to a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:08:14Z" - latency: 8.832801ms message: 'load-balancer-api-external: resolved host name a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:08:14Z" - latency: 4.76865ms message: 'load-balancer-api-external: tcp connection to a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:07:14Z" - latency: 11.926646ms message: 'load-balancer-api-external: resolved host name a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:07:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-187-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-187.ec2.internal uid: 491b008f-3a58-4385-92ca-b632286fff95 resourceVersion: "64286" uid: eab9c164-fa5d-4847-ae47-0a09fccaabc3 spec: sourcePod: network-check-source-7bc5b6bf85-68drw targetEndpoint: a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T19:35:14Z" message: 'load-balancer-api-internal: tcp connection to a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.783208ms message: 'load-balancer-api-internal: tcp connection to a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:11:14Z" - latency: 8.526276ms message: 'load-balancer-api-internal: resolved host name a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:11:14Z" - latency: 5.331909ms message: 'load-balancer-api-internal: tcp connection to a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:10:14Z" - latency: 14.624248ms message: 'load-balancer-api-internal: resolved host name a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:10:14Z" - latency: 5.341727ms message: 'load-balancer-api-internal: tcp connection to a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:09:14Z" - latency: 7.519605ms message: 'load-balancer-api-internal: resolved host name a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:09:14Z" - latency: 4.991857ms message: 'load-balancer-api-internal: tcp connection to a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:08:14Z" - latency: 8.994256ms message: 'load-balancer-api-internal: resolved host name a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:08:14Z" - latency: 6.128235ms message: 'load-balancer-api-internal: tcp connection to a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:07:14Z" - latency: 11.986335ms message: 'load-balancer-api-internal: resolved host name a9d9942d70e0843249198f59a459561e-1bee42b1f5ecf90b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:07:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-187-to-network-check-target-ip-10-0-135-59 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-187.ec2.internal uid: 491b008f-3a58-4385-92ca-b632286fff95 resourceVersion: "64282" uid: 395025ae-f8f9-46fa-bb7d-6d9fc0ae6b33 spec: sourcePod: network-check-source-7bc5b6bf85-68drw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T19:36:14Z" message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.0406ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:11:14Z" - latency: 2.418895ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:10:14Z" - latency: 2.252032ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:09:14Z" - latency: 2.73972ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:08:14Z" - latency: 2.418683ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:07:14Z" - latency: 2.562398ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:06:14Z" - latency: 2.383185ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:05:14Z" - latency: 2.368656ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:04:14Z" - latency: 2.405916ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:03:14Z" - latency: 2.615275ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:02:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-187-to-network-check-target-ip-10-0-138-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-187.ec2.internal uid: 491b008f-3a58-4385-92ca-b632286fff95 resourceVersion: "64281" uid: a1af76d4-ed05-4faa-8ea5-65349824cf34 spec: sourcePod: network-check-source-7bc5b6bf85-68drw targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-20T19:36:14Z" message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.500886ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:11:14Z" - latency: 2.360235ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:10:14Z" - latency: 2.378752ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:09:14Z" - latency: 2.239046ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:08:14Z" - latency: 2.429251ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:07:14Z" - latency: 2.327587ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:06:14Z" - latency: 2.555312ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:05:14Z" - latency: 2.660437ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:04:14Z" - latency: 2.02191ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:03:14Z" - latency: 2.719443ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:02:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-187-to-network-check-target-ip-10-0-143-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-187.ec2.internal uid: 491b008f-3a58-4385-92ca-b632286fff95 resourceVersion: "64279" uid: a20fcc40-2074-4973-93f2-521a12dbfdbc spec: sourcePod: network-check-source-7bc5b6bf85-68drw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T19:36:14Z" message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.461006ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:11:14Z" - latency: 1.051402ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:10:14Z" - latency: 933.836µs message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:09:14Z" - latency: 1.01777ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:08:14Z" - latency: 960.022µs message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:07:14Z" - latency: 966.166µs message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:06:14Z" - latency: 988.804µs message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:05:14Z" - latency: 908.678µs message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:04:14Z" - latency: 902.525µs message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:03:14Z" - latency: 1.372898ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:02:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-187-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-187.ec2.internal uid: 491b008f-3a58-4385-92ca-b632286fff95 resourceVersion: "64280" uid: a650e6b4-d3fc-4626-81ab-a47a205ecd5e spec: sourcePod: network-check-source-7bc5b6bf85-68drw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T19:35:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 754.911µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:11:14Z" - latency: 1.699576ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T20:11:14Z" - latency: 1.238788ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:10:14Z" - latency: 1.760533ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T20:10:14Z" - latency: 918.006µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:09:14Z" - latency: 1.836201ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T20:09:14Z" - latency: 864.536µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:08:14Z" - latency: 1.908928ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T20:08:14Z" - latency: 867.513µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:07:14Z" - latency: 1.827003ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T20:07:14Z" kind: List metadata: resourceVersion: ""