apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-202-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-202.ec2.internal
      uid: eaa381cb-7c4a-4ea1-8e87-65543067d3a6
    resourceVersion: "39490"
    uid: 7fff0039-0a7f-4dbf-8760-f6702ed4fa22
  spec:
    sourcePod: network-check-source-7cbc45fddc-np47h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:48:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.013µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:30:03Z"
    - latency: 1.580712ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:03Z"
    - latency: 1.930434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:03Z"
    - latency: 1.212611ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:03Z"
    - latency: 1.187446ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:03Z"
    - latency: 1.078549ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:03Z"
    - latency: 1.190666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:03Z"
    - latency: 1.823755ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:03Z"
    - latency: 1.210687ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:03Z"
    - latency: 973.068µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-202-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-202.ec2.internal
      uid: eaa381cb-7c4a-4ea1-8e87-65543067d3a6
    resourceVersion: "39029"
    uid: df68170e-fdef-44ab-a069-ccb7b97180e7
  spec:
    sourcePod: network-check-source-7cbc45fddc-np47h
    targetEndpoint: a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:47:03Z"
      message: 'load-balancer-api-external: tcp connection to a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.042781ms
      message: 'load-balancer-api-external: tcp connection to a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:03Z"
    - latency: 6.529825ms
      message: 'load-balancer-api-external: resolved host name a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:29:03Z"
    - latency: 4.983863ms
      message: 'load-balancer-api-external: tcp connection to a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:03Z"
    - latency: 8.092438ms
      message: 'load-balancer-api-external: resolved host name a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:28:03Z"
    - latency: 5.499161ms
      message: 'load-balancer-api-external: tcp connection to a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:03Z"
    - latency: 7.588977ms
      message: 'load-balancer-api-external: resolved host name a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:27:03Z"
    - latency: 4.59657ms
      message: 'load-balancer-api-external: tcp connection to a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:03Z"
    - latency: 7.170048ms
      message: 'load-balancer-api-external: resolved host name a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:26:03Z"
    - latency: 4.728569ms
      message: 'load-balancer-api-external: tcp connection to a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:03Z"
    - latency: 8.382753ms
      message: 'load-balancer-api-external: resolved host name a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:25:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-202-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-202.ec2.internal
      uid: eaa381cb-7c4a-4ea1-8e87-65543067d3a6
    resourceVersion: "39028"
    uid: 97cba310-e8f4-4c6b-9c94-1695bbdc6e36
  spec:
    sourcePod: network-check-source-7cbc45fddc-np47h
    targetEndpoint: a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:47:03Z"
      message: 'load-balancer-api-internal: tcp connection to a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.877344ms
      message: 'load-balancer-api-internal: tcp connection to a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:03Z"
    - latency: 6.578456ms
      message: 'load-balancer-api-internal: resolved host name a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:29:03Z"
    - latency: 5.043318ms
      message: 'load-balancer-api-internal: tcp connection to a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:03Z"
    - latency: 8.259974ms
      message: 'load-balancer-api-internal: resolved host name a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:28:03Z"
    - latency: 5.489516ms
      message: 'load-balancer-api-internal: tcp connection to a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:03Z"
    - latency: 7.650345ms
      message: 'load-balancer-api-internal: resolved host name a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:27:03Z"
    - latency: 4.593926ms
      message: 'load-balancer-api-internal: tcp connection to a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:03Z"
    - latency: 7.300556ms
      message: 'load-balancer-api-internal: resolved host name a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:26:03Z"
    - latency: 5.825996ms
      message: 'load-balancer-api-internal: tcp connection to a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:03Z"
    - latency: 8.335335ms
      message: 'load-balancer-api-internal: resolved host name a99d170322daf4ed99e064cd58bc6fff-d6ed4a5dfa24ecda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:25:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-202-to-network-check-target-ip-10-0-132-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-202.ec2.internal
      uid: eaa381cb-7c4a-4ea1-8e87-65543067d3a6
    resourceVersion: "39488"
    uid: e0dd5be0-15d1-41da-83d3-fca3868a9247
  spec:
    sourcePod: network-check-source-7cbc45fddc-np47h
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:48:03Z"
      message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.023239ms
      message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:30:03Z"
    - latency: 2.159499ms
      message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:03Z"
    - latency: 2.282638ms
      message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:03Z"
    - latency: 2.234569ms
      message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:03Z"
    - latency: 2.132171ms
      message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:03Z"
    - latency: 2.191108ms
      message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:03Z"
    - latency: 2.23582ms
      message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:03Z"
    - latency: 2.113558ms
      message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:03Z"
    - latency: 2.335891ms
      message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:03Z"
    - latency: 2.510854ms
      message: 'network-check-target-ip-10-0-132-143: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-202-to-network-check-target-ip-10-0-134-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-202.ec2.internal
      uid: eaa381cb-7c4a-4ea1-8e87-65543067d3a6
    resourceVersion: "39489"
    uid: ba218e32-577b-44f9-9925-9b965f7c3834
  spec:
    sourcePod: network-check-source-7cbc45fddc-np47h
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:48:03Z"
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.247809ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:30:03Z"
    - latency: 2.132619ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:03Z"
    - latency: 2.519698ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:03Z"
    - latency: 2.491989ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:03Z"
    - latency: 2.158142ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:03Z"
    - latency: 2.862579ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:03Z"
    - latency: 2.192952ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:03Z"
    - latency: 2.357477ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:03Z"
    - latency: 2.413814ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:03Z"
    - latency: 2.555359ms
      message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-202-to-network-check-target-ip-10-0-135-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-202.ec2.internal
      uid: eaa381cb-7c4a-4ea1-8e87-65543067d3a6
    resourceVersion: "39487"
    uid: e158c1c6-845d-46de-b3e5-69c6be9126da
  spec:
    sourcePod: network-check-source-7cbc45fddc-np47h
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:48:03Z"
      message: 'network-check-target-ip-10-0-135-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.025887ms
      message: 'network-check-target-ip-10-0-135-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:30:03Z"
    - latency: 1.035622ms
      message: 'network-check-target-ip-10-0-135-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:03Z"
    - latency: 1.461521ms
      message: 'network-check-target-ip-10-0-135-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:03Z"
    - latency: 1.548752ms
      message: 'network-check-target-ip-10-0-135-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:03Z"
    - latency: 1.060423ms
      message: 'network-check-target-ip-10-0-135-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:03Z"
    - latency: 2.051541ms
      message: 'network-check-target-ip-10-0-135-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:03Z"
    - latency: 961.342µs
      message: 'network-check-target-ip-10-0-135-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:03Z"
    - latency: 1.049875ms
      message: 'network-check-target-ip-10-0-135-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:03Z"
    - latency: 1.461177ms
      message: 'network-check-target-ip-10-0-135-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:03Z"
    - latency: 1.429219ms
      message: 'network-check-target-ip-10-0-135-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-202-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-202.ec2.internal
      uid: eaa381cb-7c4a-4ea1-8e87-65543067d3a6
    resourceVersion: "39027"
    uid: 012892b0-ae50-44b0-9160-f4ea4cece07f
  spec:
    sourcePod: network-check-source-7cbc45fddc-np47h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:47:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.109034ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:03Z"
    - latency: 1.85825ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:29:03Z"
    - latency: 1.120821ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:03Z"
    - latency: 2.306974ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:28:03Z"
    - latency: 1.080281ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:03Z"
    - latency: 1.946281ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:27:03Z"
    - latency: 926.542µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:03Z"
    - latency: 1.922645ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:26:03Z"
    - latency: 886.832µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:03Z"
    - latency: 2.755617ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:25:03Z"
kind: List
metadata:
  resourceVersion: ""