apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-57-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-57.ec2.internal
      uid: 8b3856bb-a053-4ef8-96b4-735cace9b346
    resourceVersion: "54570"
    uid: b556c816-bcd4-42d2-8074-bd9a2d554f69
  spec:
    sourcePod: network-check-source-869dcfcdcd-v5lz8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T13:37:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 946.777µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:05:29Z"
    - latency: 895.002µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:04:29Z"
    - latency: 1.149383ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:03:29Z"
    - latency: 1.13713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:02:29Z"
    - latency: 1.032557ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:01:29Z"
    - latency: 1.005017ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:00:29Z"
    - latency: 951.285µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:59:29Z"
    - latency: 829.649µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:58:29Z"
    - latency: 805.484µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:57:29Z"
    - latency: 831.282µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:56:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-57-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-57.ec2.internal
      uid: 8b3856bb-a053-4ef8-96b4-735cace9b346
    resourceVersion: "55589"
    uid: 38becf49-a03e-42b8-ad37-8e3de98c3951
  spec:
    sourcePod: network-check-source-869dcfcdcd-v5lz8
    targetEndpoint: a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T13:36:29Z"
      message: 'load-balancer-api-external: tcp connection to a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.318396ms
      message: 'load-balancer-api-external: tcp connection to a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:06:29Z"
    - latency: 6.386469ms
      message: 'load-balancer-api-external: resolved host name a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:06:29Z"
    - latency: 3.525529ms
      message: 'load-balancer-api-external: tcp connection to a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:05:29Z"
    - latency: 6.531558ms
      message: 'load-balancer-api-external: resolved host name a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:05:29Z"
    - latency: 5.709063ms
      message: 'load-balancer-api-external: tcp connection to a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:04:29Z"
    - latency: 6.598132ms
      message: 'load-balancer-api-external: resolved host name a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:04:29Z"
    - latency: 5.735703ms
      message: 'load-balancer-api-external: tcp connection to a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:03:29Z"
    - latency: 6.567409ms
      message: 'load-balancer-api-external: resolved host name a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:03:29Z"
    - latency: 5.341417ms
      message: 'load-balancer-api-external: tcp connection to a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:02:29Z"
    - latency: 7.120179ms
      message: 'load-balancer-api-external: resolved host name a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:02:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-57-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-57.ec2.internal
      uid: 8b3856bb-a053-4ef8-96b4-735cace9b346
    resourceVersion: "55590"
    uid: 2ec14536-f684-4820-9c9f-5fbdec70ab3a
  spec:
    sourcePod: network-check-source-869dcfcdcd-v5lz8
    targetEndpoint: a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T13:36:29Z"
      message: 'load-balancer-api-internal: tcp connection to a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.327911ms
      message: 'load-balancer-api-internal: tcp connection to a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:06:29Z"
    - latency: 6.413734ms
      message: 'load-balancer-api-internal: resolved host name a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:06:29Z"
    - latency: 3.544476ms
      message: 'load-balancer-api-internal: tcp connection to a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:05:29Z"
    - latency: 6.632916ms
      message: 'load-balancer-api-internal: resolved host name a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:05:29Z"
    - latency: 5.747002ms
      message: 'load-balancer-api-internal: tcp connection to a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:04:29Z"
    - latency: 6.674042ms
      message: 'load-balancer-api-internal: resolved host name a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:04:29Z"
    - latency: 5.237141ms
      message: 'load-balancer-api-internal: tcp connection to a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:03:29Z"
    - latency: 6.503539ms
      message: 'load-balancer-api-internal: resolved host name a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:03:29Z"
    - latency: 4.106115ms
      message: 'load-balancer-api-internal: tcp connection to a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:02:29Z"
    - latency: 7.166432ms
      message: 'load-balancer-api-internal: resolved host name a30579bedd4154d44bc4d32e109ceee5-bf65eb79cdf9ce7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:02:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-57-to-network-check-target-ip-10-0-128-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-57.ec2.internal
      uid: 8b3856bb-a053-4ef8-96b4-735cace9b346
    resourceVersion: "54567"
    uid: 4fe784c2-f8e8-4d9a-89ec-efbb7b7fa28b
  spec:
    sourcePod: network-check-source-869dcfcdcd-v5lz8
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T13:37:29Z"
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.293µs
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:05:29Z"
    - latency: 668.575µs
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:04:29Z"
    - latency: 1.354742ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:03:29Z"
    - latency: 971.521µs
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:02:29Z"
    - latency: 1.279307ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:01:29Z"
    - latency: 1.051611ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:00:29Z"
    - latency: 887.227µs
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:59:29Z"
    - latency: 863.556µs
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:58:29Z"
    - latency: 1.144279ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:57:29Z"
    - latency: 989.87µs
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:56:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-57-to-network-check-target-ip-10-0-135-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-57.ec2.internal
      uid: 8b3856bb-a053-4ef8-96b4-735cace9b346
    resourceVersion: "54568"
    uid: 85795350-4976-4090-bc05-c4051d4d3635
  spec:
    sourcePod: network-check-source-869dcfcdcd-v5lz8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T13:37:29Z"
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.279922ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:05:29Z"
    - latency: 2.640418ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:04:29Z"
    - latency: 2.235016ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:03:29Z"
    - latency: 2.239884ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:02:29Z"
    - latency: 2.2721ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:01:29Z"
    - latency: 2.267874ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:00:29Z"
    - latency: 2.515841ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:59:29Z"
    - latency: 2.23381ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:58:29Z"
    - latency: 2.069116ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:57:29Z"
    - latency: 2.27892ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:56:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-57-to-network-check-target-ip-10-0-136-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-57.ec2.internal
      uid: 8b3856bb-a053-4ef8-96b4-735cace9b346
    resourceVersion: "54569"
    uid: c47ac58d-92b9-44cc-82f0-23b581c1e9ec
  spec:
    sourcePod: network-check-source-869dcfcdcd-v5lz8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T13:37:29Z"
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.049885ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:05:29Z"
    - latency: 1.993686ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:04:29Z"
    - latency: 2.16746ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:03:29Z"
    - latency: 2.204375ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:02:29Z"
    - latency: 2.118566ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:01:29Z"
    - latency: 2.018511ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:00:29Z"
    - latency: 1.991953ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:59:29Z"
    - latency: 1.875838ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:58:29Z"
    - latency: 1.941716ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:57:29Z"
    - latency: 1.933735ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T13:56:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T13:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-57-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-57.ec2.internal
      uid: 8b3856bb-a053-4ef8-96b4-735cace9b346
    resourceVersion: "55588"
    uid: d49eb1df-428d-49aa-a2a6-b923263d3992
  spec:
    sourcePod: network-check-source-869dcfcdcd-v5lz8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T13:36:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 855.359µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:06:29Z"
    - latency: 1.781026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:06:29Z"
    - latency: 876.253µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:05:29Z"
    - latency: 1.697866ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:05:29Z"
    - latency: 1.001307ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:04:29Z"
    - latency: 1.572189ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:04:29Z"
    - latency: 1.198852ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:03:29Z"
    - latency: 1.781541ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:03:29Z"
    - latency: 756.749µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T14:02:29Z"
    - latency: 1.717992ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T14:02:29Z"
kind: List
metadata:
  resourceVersion: ""