apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:19:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-22-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-22.ec2.internal
      uid: 318dabb6-721a-4f02-8b6e-34789d954af3
    resourceVersion: "53314"
    uid: d76fef4e-418a-46ea-a645-19f86e02cd24
  spec:
    sourcePod: network-check-source-685456655f-chktm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:26:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.588649ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:47:32Z"
    - latency: 1.195495ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:46:32Z"
    - latency: 1.454559ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:45:32Z"
    - latency: 1.23057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:44:32Z"
    - latency: 992.858µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:43:32Z"
    - latency: 1.169474ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:42:32Z"
    - latency: 1.763459ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:41:32Z"
    - latency: 2.055806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:40:32Z"
    - latency: 1.070226ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:39:32Z"
    - latency: 1.099256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:38:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:19:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-22-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-22.ec2.internal
      uid: 318dabb6-721a-4f02-8b6e-34789d954af3
    resourceVersion: "54894"
    uid: 0818c106-372f-402c-a5b7-d8655b6af224
  spec:
    sourcePod: network-check-source-685456655f-chktm
    targetEndpoint: a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:25:32Z"
      message: 'load-balancer-api-external: tcp connection to a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.393044ms
      message: 'load-balancer-api-external: tcp connection to a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:49:32Z"
    - latency: 8.813919ms
      message: 'load-balancer-api-external: resolved host name a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:49:32Z"
    - latency: 3.351519ms
      message: 'load-balancer-api-external: tcp connection to a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:48:32Z"
    - latency: 9.395174ms
      message: 'load-balancer-api-external: resolved host name a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:48:32Z"
    - latency: 4.055658ms
      message: 'load-balancer-api-external: tcp connection to a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:47:32Z"
    - latency: 9.172335ms
      message: 'load-balancer-api-external: resolved host name a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:47:32Z"
    - latency: 3.562879ms
      message: 'load-balancer-api-external: tcp connection to a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:46:32Z"
    - latency: 9.529137ms
      message: 'load-balancer-api-external: resolved host name a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:46:32Z"
    - latency: 5.880085ms
      message: 'load-balancer-api-external: tcp connection to a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:45:32Z"
    - latency: 6.558371ms
      message: 'load-balancer-api-external: resolved host name a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:45:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:19:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-22-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-22.ec2.internal
      uid: 318dabb6-721a-4f02-8b6e-34789d954af3
    resourceVersion: "54893"
    uid: b7c705d5-cf4e-4406-b68f-4f505724095a
  spec:
    sourcePod: network-check-source-685456655f-chktm
    targetEndpoint: a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:25:32Z"
      message: 'load-balancer-api-internal: tcp connection to a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.346748ms
      message: 'load-balancer-api-internal: tcp connection to a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:49:32Z"
    - latency: 8.851836ms
      message: 'load-balancer-api-internal: resolved host name a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:49:32Z"
    - latency: 3.329563ms
      message: 'load-balancer-api-internal: tcp connection to a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:48:32Z"
    - latency: 9.488722ms
      message: 'load-balancer-api-internal: resolved host name a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:48:32Z"
    - latency: 3.69759ms
      message: 'load-balancer-api-internal: tcp connection to a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:47:32Z"
    - latency: 9.20376ms
      message: 'load-balancer-api-internal: resolved host name a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:47:32Z"
    - latency: 3.58645ms
      message: 'load-balancer-api-internal: tcp connection to a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:46:32Z"
    - latency: 9.471694ms
      message: 'load-balancer-api-internal: resolved host name a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:46:32Z"
    - latency: 5.916665ms
      message: 'load-balancer-api-internal: tcp connection to a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:45:32Z"
    - latency: 6.719811ms
      message: 'load-balancer-api-internal: resolved host name a2f4dfc96f0a44074b10622a13872f75-86f1e525cdb8ea93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:45:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:19:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-22-to-network-check-target-ip-10-0-131-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-22.ec2.internal
      uid: 318dabb6-721a-4f02-8b6e-34789d954af3
    resourceVersion: "53313"
    uid: 59255667-0a81-4de4-93f7-6c6a638d0956
  spec:
    sourcePod: network-check-source-685456655f-chktm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:26:32Z"
      message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.999643ms
      message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:47:32Z"
    - latency: 2.577754ms
      message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:46:32Z"
    - latency: 2.625954ms
      message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:45:32Z"
    - latency: 2.413729ms
      message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:44:32Z"
    - latency: 2.447971ms
      message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:43:32Z"
    - latency: 2.81992ms
      message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:42:32Z"
    - latency: 2.219522ms
      message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:41:32Z"
    - latency: 2.518198ms
      message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:40:32Z"
    - latency: 2.409906ms
      message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:39:32Z"
    - latency: 2.635085ms
      message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:38:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:19:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-22-to-network-check-target-ip-10-0-131-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-22.ec2.internal
      uid: 318dabb6-721a-4f02-8b6e-34789d954af3
    resourceVersion: "53311"
    uid: f069035c-0339-4e59-af69-0c67025efe5c
  spec:
    sourcePod: network-check-source-685456655f-chktm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:26:32Z"
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.870242ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:47:32Z"
    - latency: 1.141987ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:46:32Z"
    - latency: 1.047061ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:45:32Z"
    - latency: 990.985µs
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:44:32Z"
    - latency: 1.363423ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:43:32Z"
    - latency: 968.232µs
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:42:32Z"
    - latency: 878.11µs
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:41:32Z"
    - latency: 2.475515ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:40:32Z"
    - latency: 1.5103ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:39:32Z"
    - latency: 1.481103ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:38:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:19:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-22-to-network-check-target-ip-10-0-141-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-22.ec2.internal
      uid: 318dabb6-721a-4f02-8b6e-34789d954af3
    resourceVersion: "53312"
    uid: bc9fb5bb-1939-4693-9516-611028979ee7
  spec:
    sourcePod: network-check-source-685456655f-chktm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:26:32Z"
      message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.401787ms
      message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:47:32Z"
    - latency: 2.371868ms
      message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:46:32Z"
    - latency: 2.776706ms
      message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:45:32Z"
    - latency: 2.813007ms
      message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:44:32Z"
    - latency: 2.677628ms
      message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:43:32Z"
    - latency: 2.517398ms
      message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:42:32Z"
    - latency: 2.843552ms
      message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:41:32Z"
    - latency: 3.580791ms
      message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:40:32Z"
    - latency: 2.553373ms
      message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:39:32Z"
    - latency: 2.57268ms
      message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:38:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:19:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-22-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-22.ec2.internal
      uid: 318dabb6-721a-4f02-8b6e-34789d954af3
    resourceVersion: "54892"
    uid: 1e924a57-0536-4422-914e-2220c4eb8ebd
  spec:
    sourcePod: network-check-source-685456655f-chktm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:25:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 966.193µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:49:32Z"
    - latency: 1.833371ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:49:32Z"
    - latency: 1.088438ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:48:32Z"
    - latency: 2.331746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:48:32Z"
    - latency: 1.3376ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:47:32Z"
    - latency: 2.254893ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:47:32Z"
    - latency: 872.488µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:46:32Z"
    - latency: 2.625429ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:46:32Z"
    - latency: 1.156526ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:45:32Z"
    - latency: 1.954844ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:45:32Z"
kind: List
metadata:
  resourceVersion: ""