apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:32:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-153-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-153.ec2.internal
      uid: 582ae0a9-9a1a-4354-b0bb-7cc15072424e
    resourceVersion: "53878"
    uid: 8dcca4df-5a5f-4ffd-bc29-fcd68a89acda
  spec:
    sourcePod: network-check-source-685456655f-gmxdr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:39:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.200369ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T11:00:22Z"
    - latency: 1.207184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:59:22Z"
    - latency: 924.141µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:58:22Z"
    - latency: 1.321837ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:57:22Z"
    - latency: 1.164718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:56:22Z"
    - latency: 1.147759ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:55:22Z"
    - latency: 3.627579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:54:22Z"
    - latency: 1.055269ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:53:22Z"
    - latency: 1.139871ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:52:22Z"
    - latency: 1.006876ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:51:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:32:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-153-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-153.ec2.internal
      uid: 582ae0a9-9a1a-4354-b0bb-7cc15072424e
    resourceVersion: "55993"
    uid: f56f92ff-4b28-4358-8c02-8cb651d459e6
  spec:
    sourcePod: network-check-source-685456655f-gmxdr
    targetEndpoint: af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:38:22Z"
      message: 'load-balancer-api-external: tcp connection to af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.847894ms
      message: 'load-balancer-api-external: tcp connection to af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T11:02:22Z"
    - latency: 7.173766ms
      message: 'load-balancer-api-external: resolved host name af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T11:02:22Z"
    - latency: 5.05019ms
      message: 'load-balancer-api-external: tcp connection to af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T11:01:22Z"
    - latency: 6.487881ms
      message: 'load-balancer-api-external: resolved host name af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T11:01:22Z"
    - latency: 4.052358ms
      message: 'load-balancer-api-external: tcp connection to af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T11:00:22Z"
    - latency: 8.426583ms
      message: 'load-balancer-api-external: resolved host name af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T11:00:22Z"
    - latency: 3.200129ms
      message: 'load-balancer-api-external: tcp connection to af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:59:22Z"
    - latency: 7.504815ms
      message: 'load-balancer-api-external: resolved host name af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:59:22Z"
    - latency: 5.051806ms
      message: 'load-balancer-api-external: tcp connection to af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:58:22Z"
    - latency: 6.990344ms
      message: 'load-balancer-api-external: resolved host name af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:58:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:32:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-153-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-153.ec2.internal
      uid: 582ae0a9-9a1a-4354-b0bb-7cc15072424e
    resourceVersion: "55994"
    uid: aeff82f5-0ce4-4915-981a-a9943a4cae75
  spec:
    sourcePod: network-check-source-685456655f-gmxdr
    targetEndpoint: af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:38:22Z"
      message: 'load-balancer-api-internal: tcp connection to af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.631337ms
      message: 'load-balancer-api-internal: tcp connection to af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T11:02:22Z"
    - latency: 7.220348ms
      message: 'load-balancer-api-internal: resolved host name af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T11:02:22Z"
    - latency: 5.041059ms
      message: 'load-balancer-api-internal: tcp connection to af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T11:01:22Z"
    - latency: 6.58056ms
      message: 'load-balancer-api-internal: resolved host name af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T11:01:22Z"
    - latency: 4.002952ms
      message: 'load-balancer-api-internal: tcp connection to af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T11:00:22Z"
    - latency: 8.496853ms
      message: 'load-balancer-api-internal: resolved host name af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T11:00:22Z"
    - latency: 3.537185ms
      message: 'load-balancer-api-internal: tcp connection to af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:59:22Z"
    - latency: 7.564179ms
      message: 'load-balancer-api-internal: resolved host name af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:59:22Z"
    - latency: 5.032318ms
      message: 'load-balancer-api-internal: tcp connection to af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:58:22Z"
    - latency: 7.056896ms
      message: 'load-balancer-api-internal: resolved host name af4f352b3b37346ef9a88ca411923dcf-2ae9af666fc8b129.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:58:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:32:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-153-to-network-check-target-ip-10-0-130-119
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-153.ec2.internal
      uid: 582ae0a9-9a1a-4354-b0bb-7cc15072424e
    resourceVersion: "53877"
    uid: d660ceeb-0ce5-427d-8a5c-42176ac8b177
  spec:
    sourcePod: network-check-source-685456655f-gmxdr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:39:22Z"
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.084596ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T11:00:22Z"
    - latency: 1.977406ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:59:22Z"
    - latency: 2.043443ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:58:22Z"
    - latency: 2.079808ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:57:22Z"
    - latency: 2.08645ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:56:22Z"
    - latency: 2.068244ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:55:22Z"
    - latency: 2.071501ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:54:22Z"
    - latency: 2.001389ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:53:22Z"
    - latency: 1.932163ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:52:22Z"
    - latency: 1.858036ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:51:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:32:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-153-to-network-check-target-ip-10-0-133-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-153.ec2.internal
      uid: 582ae0a9-9a1a-4354-b0bb-7cc15072424e
    resourceVersion: "53875"
    uid: 46cf64bc-8b37-4cd0-b39c-891c749fdac4
  spec:
    sourcePod: network-check-source-685456655f-gmxdr
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:39:22Z"
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.181674ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T11:00:22Z"
    - latency: 1.349019ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:59:22Z"
    - latency: 1.364664ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:58:22Z"
    - latency: 900.465µs
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:57:22Z"
    - latency: 870.443µs
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:56:22Z"
    - latency: 1.119165ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:55:22Z"
    - latency: 1.796704ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:54:22Z"
    - latency: 974.988µs
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:53:22Z"
    - latency: 1.062281ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:52:22Z"
    - latency: 884.318µs
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:51:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:32:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-153-to-network-check-target-ip-10-0-139-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-153.ec2.internal
      uid: 582ae0a9-9a1a-4354-b0bb-7cc15072424e
    resourceVersion: "53876"
    uid: 7df2fb94-b69d-4e90-810c-4e589b0d0578
  spec:
    sourcePod: network-check-source-685456655f-gmxdr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:39:22Z"
      message: 'network-check-target-ip-10-0-139-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.363675ms
      message: 'network-check-target-ip-10-0-139-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T11:00:22Z"
    - latency: 2.188763ms
      message: 'network-check-target-ip-10-0-139-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:59:22Z"
    - latency: 2.455811ms
      message: 'network-check-target-ip-10-0-139-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:58:22Z"
    - latency: 2.422704ms
      message: 'network-check-target-ip-10-0-139-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:57:22Z"
    - latency: 2.083909ms
      message: 'network-check-target-ip-10-0-139-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:56:22Z"
    - latency: 2.326871ms
      message: 'network-check-target-ip-10-0-139-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:55:22Z"
    - latency: 2.741785ms
      message: 'network-check-target-ip-10-0-139-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:54:22Z"
    - latency: 2.418423ms
      message: 'network-check-target-ip-10-0-139-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:53:22Z"
    - latency: 2.420432ms
      message: 'network-check-target-ip-10-0-139-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:52:22Z"
    - latency: 2.367667ms
      message: 'network-check-target-ip-10-0-139-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:51:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:32:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-153-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-153.ec2.internal
      uid: 582ae0a9-9a1a-4354-b0bb-7cc15072424e
    resourceVersion: "55992"
    uid: 1a116306-9c20-47c4-997b-8e81b24efba2
  spec:
    sourcePod: network-check-source-685456655f-gmxdr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:38:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 971.572µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T11:02:22Z"
    - latency: 2.116994ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T11:02:22Z"
    - latency: 862.732µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T11:01:22Z"
    - latency: 1.892136ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T11:01:22Z"
    - latency: 924.279µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T11:00:22Z"
    - latency: 1.724208ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T11:00:22Z"
    - latency: 779.722µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:59:22Z"
    - latency: 2.242447ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:59:22Z"
    - latency: 806.898µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:58:22Z"
    - latency: 1.894084ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:58:22Z"
kind: List
metadata:
  resourceVersion: ""