apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:49:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-166-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-166.ec2.internal
      uid: ab23d86f-935c-4182-9370-9eb09c304223
    resourceVersion: "32503"
    uid: f7453609-95a8-48d1-b3d3-443d35fc6619
  spec:
    sourcePod: network-check-source-56499946bc-sxxzg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:56: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.661254ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:31:14Z"
    - latency: 986.556µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:14Z"
    - latency: 1.036746ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:14Z"
    - latency: 958.693µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:14Z"
    - latency: 859.436µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:14Z"
    - latency: 1.121305ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:26:14Z"
    - latency: 1.159459ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:25:14Z"
    - latency: 928.765µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:24:14Z"
    - latency: 1.168732ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:23:14Z"
    - latency: 1.09658ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:22:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:49:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-166-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-166.ec2.internal
      uid: ab23d86f-935c-4182-9370-9eb09c304223
    resourceVersion: "32505"
    uid: 04f5414a-3bb7-4e8a-bce3-dbac65cdedcf
  spec:
    sourcePod: network-check-source-56499946bc-sxxzg
    targetEndpoint: a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:55:14Z"
      message: 'load-balancer-api-external: tcp connection to a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.531487ms
      message: 'load-balancer-api-external: tcp connection to a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:31:14Z"
    - latency: 8.625991ms
      message: 'load-balancer-api-external: resolved host name a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:31:14Z"
    - latency: 4.964623ms
      message: 'load-balancer-api-external: tcp connection to a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:14Z"
    - latency: 8.288288ms
      message: 'load-balancer-api-external: resolved host name a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:30:14Z"
    - latency: 4.899956ms
      message: 'load-balancer-api-external: tcp connection to a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:14Z"
    - latency: 9.386581ms
      message: 'load-balancer-api-external: resolved host name a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:29:14Z"
    - latency: 4.897425ms
      message: 'load-balancer-api-external: tcp connection to a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:14Z"
    - latency: 9.758241ms
      message: 'load-balancer-api-external: resolved host name a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:28:14Z"
    - latency: 4.963228ms
      message: 'load-balancer-api-external: tcp connection to a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:14Z"
    - latency: 8.863843ms
      message: 'load-balancer-api-external: resolved host name a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:27:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:49:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-166-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-166.ec2.internal
      uid: ab23d86f-935c-4182-9370-9eb09c304223
    resourceVersion: "32504"
    uid: a9eff13d-9f69-4de9-852c-e0d7e174783c
  spec:
    sourcePod: network-check-source-56499946bc-sxxzg
    targetEndpoint: a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:55:14Z"
      message: 'load-balancer-api-internal: tcp connection to a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.397693ms
      message: 'load-balancer-api-internal: tcp connection to a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:31:14Z"
    - latency: 8.723635ms
      message: 'load-balancer-api-internal: resolved host name a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:31:14Z"
    - latency: 4.941911ms
      message: 'load-balancer-api-internal: tcp connection to a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:14Z"
    - latency: 8.352487ms
      message: 'load-balancer-api-internal: resolved host name a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:30:14Z"
    - latency: 4.88621ms
      message: 'load-balancer-api-internal: tcp connection to a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:14Z"
    - latency: 9.426901ms
      message: 'load-balancer-api-internal: resolved host name a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:29:14Z"
    - latency: 4.098219ms
      message: 'load-balancer-api-internal: tcp connection to a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:14Z"
    - latency: 9.806996ms
      message: 'load-balancer-api-internal: resolved host name a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:28:14Z"
    - latency: 4.961238ms
      message: 'load-balancer-api-internal: tcp connection to a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:14Z"
    - latency: 8.880055ms
      message: 'load-balancer-api-internal: resolved host name a4d1233062f87478ca79609369ccfbd7-5fe848a67d900c4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:27:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:49:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-166-to-network-check-target-ip-10-0-130-150
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-166.ec2.internal
      uid: ab23d86f-935c-4182-9370-9eb09c304223
    resourceVersion: "32501"
    uid: 4e6c0d56-e6f4-4cc1-bbce-bb9c142d5f6a
  spec:
    sourcePod: network-check-source-56499946bc-sxxzg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:56:14Z"
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.172161ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:31:14Z"
    - latency: 2.039469ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:14Z"
    - latency: 2.339077ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:14Z"
    - latency: 2.106504ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:14Z"
    - latency: 1.961492ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:14Z"
    - latency: 2.298572ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:26:14Z"
    - latency: 2.337344ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:25:14Z"
    - latency: 2.293869ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:24:14Z"
    - latency: 2.091445ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:23:14Z"
    - latency: 2.319387ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:22:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:49:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-166-to-network-check-target-ip-10-0-131-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-166.ec2.internal
      uid: ab23d86f-935c-4182-9370-9eb09c304223
    resourceVersion: "32500"
    uid: 4a5a3f2b-7ae2-4cf0-bd38-af9269a95cc1
  spec:
    sourcePod: network-check-source-56499946bc-sxxzg
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:56:14Z"
      message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.89936ms
      message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:31:14Z"
    - latency: 1.59959ms
      message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:14Z"
    - latency: 1.573237ms
      message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:14Z"
    - latency: 1.828748ms
      message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:14Z"
    - latency: 1.865381ms
      message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:14Z"
    - latency: 1.852259ms
      message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:26:14Z"
    - latency: 1.875217ms
      message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:25:14Z"
    - latency: 1.851256ms
      message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:24:14Z"
    - latency: 1.833838ms
      message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:23:14Z"
    - latency: 1.830646ms
      message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:22:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:49:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-166-to-network-check-target-ip-10-0-136-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-166.ec2.internal
      uid: ab23d86f-935c-4182-9370-9eb09c304223
    resourceVersion: "32499"
    uid: e8370cc9-465a-4495-9b1a-d531d64e280b
  spec:
    sourcePod: network-check-source-56499946bc-sxxzg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:56:14Z"
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.417µs
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:31:14Z"
    - latency: 793.497µs
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:14Z"
    - latency: 952.31µs
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:14Z"
    - latency: 920.987µs
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:14Z"
    - latency: 899.554µs
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:14Z"
    - latency: 1.407507ms
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:26:14Z"
    - latency: 1.374909ms
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:25:14Z"
    - latency: 907.579µs
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:24:14Z"
    - latency: 820.31µs
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:23:14Z"
    - latency: 854.84µs
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:22:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:49:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-166-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-166.ec2.internal
      uid: ab23d86f-935c-4182-9370-9eb09c304223
    resourceVersion: "32502"
    uid: 603ed1bb-02c5-4ad7-a58a-e698666a4dac
  spec:
    sourcePod: network-check-source-56499946bc-sxxzg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:55:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 942.938µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:31:14Z"
    - latency: 1.908645ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:31:14Z"
    - latency: 829.095µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:14Z"
    - latency: 1.904495ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:30:14Z"
    - latency: 849.918µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:14Z"
    - latency: 1.90812ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:29:14Z"
    - latency: 814.014µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:14Z"
    - latency: 2.648586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:28:14Z"
    - latency: 821.694µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:14Z"
    - latency: 1.676434ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:27:14Z"
kind: List
metadata:
  resourceVersion: ""