apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-173-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-173.ec2.internal
      uid: 587cc825-0d9b-4029-904a-2a5aeaa1ad27
    resourceVersion: "49029"
    uid: 22cf01b1-ee54-4d64-8a25-1e6c5d4b3b8a
  spec:
    sourcePod: network-check-source-989f8b8dc-8gwsg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:43:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.182381ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:49Z"
    - latency: 1.540498ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:49Z"
    - latency: 1.203514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:49Z"
    - latency: 1.308555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:49Z"
    - latency: 999.066µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:49Z"
    - latency: 902.197µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:49Z"
    - latency: 1.037595ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:49Z"
    - latency: 975.375µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:49Z"
    - latency: 1.193709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:49Z"
    - latency: 884.669µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-173-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-173.ec2.internal
      uid: 587cc825-0d9b-4029-904a-2a5aeaa1ad27
    resourceVersion: "49916"
    uid: 237f5232-4c91-4bf3-bf66-add9cc19140b
  spec:
    sourcePod: network-check-source-989f8b8dc-8gwsg
    targetEndpoint: afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:42:49Z"
      message: 'load-balancer-api-external: tcp connection to afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.49946ms
      message: 'load-balancer-api-external: tcp connection to afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:12:49Z"
    - latency: 8.12987ms
      message: 'load-balancer-api-external: resolved host name afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:12:49Z"
    - latency: 7.033156ms
      message: 'load-balancer-api-external: tcp connection to afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:49Z"
    - latency: 8.063455ms
      message: 'load-balancer-api-external: resolved host name afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:11:49Z"
    - latency: 4.53928ms
      message: 'load-balancer-api-external: tcp connection to afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:49Z"
    - latency: 7.153733ms
      message: 'load-balancer-api-external: resolved host name afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:10:49Z"
    - latency: 4.350963ms
      message: 'load-balancer-api-external: tcp connection to afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:49Z"
    - latency: 8.680154ms
      message: 'load-balancer-api-external: resolved host name afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:09:49Z"
    - latency: 2.878863ms
      message: 'load-balancer-api-external: tcp connection to afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:49Z"
    - latency: 7.972241ms
      message: 'load-balancer-api-external: resolved host name afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-173-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-173.ec2.internal
      uid: 587cc825-0d9b-4029-904a-2a5aeaa1ad27
    resourceVersion: "49917"
    uid: d8006eb5-fa2b-4076-92e5-85dfaebe11cd
  spec:
    sourcePod: network-check-source-989f8b8dc-8gwsg
    targetEndpoint: afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:42:49Z"
      message: 'load-balancer-api-internal: tcp connection to afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.960145ms
      message: 'load-balancer-api-internal: tcp connection to afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:12:49Z"
    - latency: 8.090033ms
      message: 'load-balancer-api-internal: resolved host name afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:12:49Z"
    - latency: 6.376087ms
      message: 'load-balancer-api-internal: tcp connection to afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:49Z"
    - latency: 8.08917ms
      message: 'load-balancer-api-internal: resolved host name afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:11:49Z"
    - latency: 5.066455ms
      message: 'load-balancer-api-internal: tcp connection to afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:49Z"
    - latency: 7.119665ms
      message: 'load-balancer-api-internal: resolved host name afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:10:49Z"
    - latency: 4.47767ms
      message: 'load-balancer-api-internal: tcp connection to afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:49Z"
    - latency: 8.65438ms
      message: 'load-balancer-api-internal: resolved host name afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:09:49Z"
    - latency: 3.946677ms
      message: 'load-balancer-api-internal: tcp connection to afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:49Z"
    - latency: 7.92531ms
      message: 'load-balancer-api-internal: resolved host name afddd40976e9d4d449fa751ed1aafa1c-250160ec2382a89c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-173-to-network-check-target-ip-10-0-131-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-173.ec2.internal
      uid: 587cc825-0d9b-4029-904a-2a5aeaa1ad27
    resourceVersion: "49028"
    uid: 957f8d90-abe9-45e3-ac91-bc9aa97c6809
  spec:
    sourcePod: network-check-source-989f8b8dc-8gwsg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:43:49Z"
      message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.392359ms
      message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:49Z"
    - latency: 2.607406ms
      message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:49Z"
    - latency: 2.339832ms
      message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:49Z"
    - latency: 2.48918ms
      message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:49Z"
    - latency: 2.298609ms
      message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:49Z"
    - latency: 2.074461ms
      message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:49Z"
    - latency: 2.357278ms
      message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:49Z"
    - latency: 2.490898ms
      message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:49Z"
    - latency: 2.356757ms
      message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:49Z"
    - latency: 2.006901ms
      message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-173-to-network-check-target-ip-10-0-136-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-173.ec2.internal
      uid: 587cc825-0d9b-4029-904a-2a5aeaa1ad27
    resourceVersion: "49026"
    uid: 1d091b00-6836-4185-92d3-5d4d062d1e79
  spec:
    sourcePod: network-check-source-989f8b8dc-8gwsg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:43:49Z"
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.825672ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:49Z"
    - latency: 2.203036ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:49Z"
    - latency: 2.417169ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:49Z"
    - latency: 2.131058ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:49Z"
    - latency: 2.672617ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:49Z"
    - latency: 2.301163ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:49Z"
    - latency: 2.792795ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:49Z"
    - latency: 2.820857ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:49Z"
    - latency: 2.351513ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:49Z"
    - latency: 2.012085ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-173-to-network-check-target-ip-10-0-138-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-173.ec2.internal
      uid: 587cc825-0d9b-4029-904a-2a5aeaa1ad27
    resourceVersion: "49027"
    uid: 97890acf-898c-4403-8dd3-84009ba5a440
  spec:
    sourcePod: network-check-source-989f8b8dc-8gwsg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:43:49Z"
      message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.584993ms
      message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:49Z"
    - latency: 1.680418ms
      message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:49Z"
    - latency: 923.111µs
      message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:49Z"
    - latency: 1.158259ms
      message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:49Z"
    - latency: 1.016212ms
      message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:49Z"
    - latency: 819.753µs
      message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:49Z"
    - latency: 1.436628ms
      message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:49Z"
    - latency: 1.731695ms
      message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:49Z"
    - latency: 1.343658ms
      message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:49Z"
    - latency: 924.693µs
      message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-173-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-173.ec2.internal
      uid: 587cc825-0d9b-4029-904a-2a5aeaa1ad27
    resourceVersion: "49915"
    uid: e83eb9ba-3f49-4182-af59-579bb75c1c4c
  spec:
    sourcePod: network-check-source-989f8b8dc-8gwsg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:42:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 751.418µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:12:49Z"
    - latency: 1.75014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:12:49Z"
    - latency: 1.118057ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:49Z"
    - latency: 2.404565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:11:49Z"
    - latency: 870.431µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:49Z"
    - latency: 1.956903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:10:49Z"
    - latency: 804.283µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:49Z"
    - latency: 2.197113ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:09:49Z"
    - latency: 821.785µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:49Z"
    - latency: 1.765494ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:49Z"
kind: List
metadata:
  resourceVersion: ""