apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-249-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-249.ec2.internal
      uid: ed75351d-af71-4b66-900f-76c960ddbb71
    resourceVersion: "32218"
    uid: 3e720838-13a6-4f72-88cd-528134394ad6
  spec:
    sourcePod: network-check-source-7d88cb55d8-f75b8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:33:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.777682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:08:11Z"
    - latency: 1.146398ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:07:11Z"
    - latency: 1.136452ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:06:11Z"
    - latency: 974.718µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:05:11Z"
    - latency: 960.956µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:04:11Z"
    - latency: 1.289502ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:03:11Z"
    - latency: 1.024479ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:02:11Z"
    - latency: 1.01448ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:01:11Z"
    - latency: 1.051201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:00:11Z"
    - latency: 1.340508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:59:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-249-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-249.ec2.internal
      uid: ed75351d-af71-4b66-900f-76c960ddbb71
    resourceVersion: "32220"
    uid: e48744f0-3654-46c2-8bc0-e85ecd3c1e2f
  spec:
    sourcePod: network-check-source-7d88cb55d8-f75b8
    targetEndpoint: a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:32:11Z"
      message: 'load-balancer-api-external: tcp connection to a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.424468ms
      message: 'load-balancer-api-external: tcp connection to a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:08:11Z"
    - latency: 8.368419ms
      message: 'load-balancer-api-external: resolved host name a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:08:11Z"
    - latency: 4.634452ms
      message: 'load-balancer-api-external: tcp connection to a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:07:11Z"
    - latency: 7.634434ms
      message: 'load-balancer-api-external: resolved host name a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:07:11Z"
    - latency: 6.052214ms
      message: 'load-balancer-api-external: tcp connection to a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:06:11Z"
    - latency: 8.146752ms
      message: 'load-balancer-api-external: resolved host name a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:06:11Z"
    - latency: 5.151162ms
      message: 'load-balancer-api-external: tcp connection to a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:05:11Z"
    - latency: 7.935441ms
      message: 'load-balancer-api-external: resolved host name a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:05:11Z"
    - latency: 5.41413ms
      message: 'load-balancer-api-external: tcp connection to a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:04:11Z"
    - latency: 8.377909ms
      message: 'load-balancer-api-external: resolved host name a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:04:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-249-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-249.ec2.internal
      uid: ed75351d-af71-4b66-900f-76c960ddbb71
    resourceVersion: "32219"
    uid: 3cebfd6d-4cf1-4a23-bba8-7a4257daaeca
  spec:
    sourcePod: network-check-source-7d88cb55d8-f75b8
    targetEndpoint: a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:32:11Z"
      message: 'load-balancer-api-internal: tcp connection to a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.416156ms
      message: 'load-balancer-api-internal: tcp connection to a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:08:11Z"
    - latency: 8.408137ms
      message: 'load-balancer-api-internal: resolved host name a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:08:11Z"
    - latency: 4.611638ms
      message: 'load-balancer-api-internal: tcp connection to a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:07:11Z"
    - latency: 7.709725ms
      message: 'load-balancer-api-internal: resolved host name a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:07:11Z"
    - latency: 6.048701ms
      message: 'load-balancer-api-internal: tcp connection to a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:06:11Z"
    - latency: 8.179929ms
      message: 'load-balancer-api-internal: resolved host name a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:06:11Z"
    - latency: 3.39232ms
      message: 'load-balancer-api-internal: tcp connection to a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:05:11Z"
    - latency: 7.986729ms
      message: 'load-balancer-api-internal: resolved host name a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:05:11Z"
    - latency: 5.844485ms
      message: 'load-balancer-api-internal: tcp connection to a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:04:11Z"
    - latency: 8.415574ms
      message: 'load-balancer-api-internal: resolved host name a5b1a9dd13bff4492b96706149ef425c-8034796fc7ded9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:04:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-249-to-network-check-target-ip-10-0-131-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-249.ec2.internal
      uid: ed75351d-af71-4b66-900f-76c960ddbb71
    resourceVersion: "32215"
    uid: d826c1bb-d40f-4097-b3dc-c8285715c5ff
  spec:
    sourcePod: network-check-source-7d88cb55d8-f75b8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:33:11Z"
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.595544ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:08:11Z"
    - latency: 2.223531ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:07:11Z"
    - latency: 2.120319ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:06:11Z"
    - latency: 2.094856ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:05:11Z"
    - latency: 2.451767ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:04:11Z"
    - latency: 2.37977ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:03:11Z"
    - latency: 2.208529ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:02:11Z"
    - latency: 2.292363ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:01:11Z"
    - latency: 2.295687ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:00:11Z"
    - latency: 2.451783ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:59:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-249-to-network-check-target-ip-10-0-141-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-249.ec2.internal
      uid: ed75351d-af71-4b66-900f-76c960ddbb71
    resourceVersion: "32216"
    uid: 8384dda6-a2e3-4d7c-9ee1-07227d5542fe
  spec:
    sourcePod: network-check-source-7d88cb55d8-f75b8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:33:11Z"
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.086622ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:08:11Z"
    - latency: 2.283209ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:07:11Z"
    - latency: 2.386834ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:06:11Z"
    - latency: 2.639703ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:05:11Z"
    - latency: 2.525756ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:04:11Z"
    - latency: 2.108527ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:03:11Z"
    - latency: 2.348156ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:02:11Z"
    - latency: 2.399599ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:01:11Z"
    - latency: 2.368744ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:00:11Z"
    - latency: 2.494859ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:59:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-249-to-network-check-target-ip-10-0-142-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-249.ec2.internal
      uid: ed75351d-af71-4b66-900f-76c960ddbb71
    resourceVersion: "32214"
    uid: afb69d63-e964-40de-acf5-8e45d450826f
  spec:
    sourcePod: network-check-source-7d88cb55d8-f75b8
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:33:11Z"
      message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 856.291µs
      message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:08:11Z"
    - latency: 892.944µs
      message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:07:11Z"
    - latency: 1.132837ms
      message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:06:11Z"
    - latency: 917.707µs
      message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:05:11Z"
    - latency: 1.096273ms
      message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:04:11Z"
    - latency: 1.483882ms
      message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:03:11Z"
    - latency: 970.195µs
      message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:02:11Z"
    - latency: 882.265µs
      message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:01:11Z"
    - latency: 907.872µs
      message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:00:11Z"
    - latency: 893.327µs
      message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:59:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-249-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-249.ec2.internal
      uid: ed75351d-af71-4b66-900f-76c960ddbb71
    resourceVersion: "32217"
    uid: d3b196d4-7f04-41a6-b390-a19ad14f573a
  spec:
    sourcePod: network-check-source-7d88cb55d8-f75b8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:32:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 968.93µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:08:11Z"
    - latency: 1.699053ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:08:11Z"
    - latency: 818.964µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:07:11Z"
    - latency: 1.942367ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:07:11Z"
    - latency: 915.405µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:06:11Z"
    - latency: 1.791377ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:06:11Z"
    - latency: 830.123µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:05:11Z"
    - latency: 1.869017ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:05:11Z"
    - latency: 1.012312ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:04:11Z"
    - latency: 1.68647ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:04:11Z"
kind: List
metadata:
  resourceVersion: ""