apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:22:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-165-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-165.ec2.internal
      uid: 5755a809-67af-40ae-9e12-251c25fdf94c
    resourceVersion: "83256"
    uid: 63deb0c2-2b3a-4c99-8110-d974e7572522
  spec:
    sourcePod: network-check-source-65bdbbff45-7gxbk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T12:29: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.502608ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:11:11Z"
    - latency: 974.86µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:10:11Z"
    - latency: 1.156574ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:09:11Z"
    - latency: 980.136µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:08:11Z"
    - latency: 1.046388ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:07:11Z"
    - latency: 1.247978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:06:11Z"
    - latency: 1.227045ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:05:11Z"
    - latency: 825.029µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:04:11Z"
    - latency: 1.288531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:03:11Z"
    - latency: 1.29276ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:02:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:22:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-165-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-165.ec2.internal
      uid: 5755a809-67af-40ae-9e12-251c25fdf94c
    resourceVersion: "95621"
    uid: 34f49345-ee2e-47c5-ad1e-d7844ffe6438
  spec:
    sourcePod: network-check-source-65bdbbff45-7gxbk
    targetEndpoint: acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T12:28:11Z"
      message: 'load-balancer-api-external: tcp connection to acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.810841ms
      message: 'load-balancer-api-external: tcp connection to acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:16:11Z"
    - latency: 8.46976ms
      message: 'load-balancer-api-external: resolved host name acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:16:11Z"
    - latency: 4.457817ms
      message: 'load-balancer-api-external: tcp connection to acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:15:11Z"
    - latency: 9.238587ms
      message: 'load-balancer-api-external: resolved host name acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:15:11Z"
    - latency: 5.31934ms
      message: 'load-balancer-api-external: tcp connection to acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:14:11Z"
    - latency: 7.190391ms
      message: 'load-balancer-api-external: resolved host name acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:14:11Z"
    - latency: 4.401752ms
      message: 'load-balancer-api-external: tcp connection to acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:13:11Z"
    - latency: 8.857305ms
      message: 'load-balancer-api-external: resolved host name acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:13:11Z"
    - latency: 4.921162ms
      message: 'load-balancer-api-external: tcp connection to acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:12:11Z"
    - latency: 7.678572ms
      message: 'load-balancer-api-external: resolved host name acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:12:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:22:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-165-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-165.ec2.internal
      uid: 5755a809-67af-40ae-9e12-251c25fdf94c
    resourceVersion: "95622"
    uid: 047d352b-5486-42e2-b1f1-9e9fe5d7c41c
  spec:
    sourcePod: network-check-source-65bdbbff45-7gxbk
    targetEndpoint: acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T12:28:11Z"
      message: 'load-balancer-api-internal: tcp connection to acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.778297ms
      message: 'load-balancer-api-internal: tcp connection to acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:16:11Z"
    - latency: 8.517346ms
      message: 'load-balancer-api-internal: resolved host name acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:16:11Z"
    - latency: 4.624159ms
      message: 'load-balancer-api-internal: tcp connection to acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:15:11Z"
    - latency: 9.193361ms
      message: 'load-balancer-api-internal: resolved host name acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:15:11Z"
    - latency: 5.270745ms
      message: 'load-balancer-api-internal: tcp connection to acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:14:11Z"
    - latency: 7.225879ms
      message: 'load-balancer-api-internal: resolved host name acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:14:11Z"
    - latency: 4.493985ms
      message: 'load-balancer-api-internal: tcp connection to acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:13:11Z"
    - latency: 8.754757ms
      message: 'load-balancer-api-internal: resolved host name acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:13:11Z"
    - latency: 4.872345ms
      message: 'load-balancer-api-internal: tcp connection to acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:12:11Z"
    - latency: 7.634457ms
      message: 'load-balancer-api-internal: resolved host name acf6199e690fa4c32bf47747cb3a516d-b2cd4ee92e33c8cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:12:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:22:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-165-to-network-check-target-ip-10-0-136-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-165.ec2.internal
      uid: 5755a809-67af-40ae-9e12-251c25fdf94c
    resourceVersion: "83254"
    uid: ab235a89-81cd-47e2-bf58-80fd6f4e7e8b
  spec:
    sourcePod: network-check-source-65bdbbff45-7gxbk
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T12:29:11Z"
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.971593ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:11:11Z"
    - latency: 2.450059ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:10:11Z"
    - latency: 2.246443ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:09:11Z"
    - latency: 2.154839ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:08:11Z"
    - latency: 2.235679ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:07:11Z"
    - latency: 2.298558ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:06:11Z"
    - latency: 2.487823ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:05:11Z"
    - latency: 2.21998ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:04:11Z"
    - latency: 2.057889ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:03:11Z"
    - latency: 1.873104ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:02:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:22:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-165-to-network-check-target-ip-10-0-138-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-165.ec2.internal
      uid: 5755a809-67af-40ae-9e12-251c25fdf94c
    resourceVersion: "83255"
    uid: f8c621a8-f565-4bdd-81b8-c62224d04565
  spec:
    sourcePod: network-check-source-65bdbbff45-7gxbk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T12:29:11Z"
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.13164ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:11:11Z"
    - latency: 1.910568ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:10:11Z"
    - latency: 1.786108ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:09:11Z"
    - latency: 1.925308ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:08:11Z"
    - latency: 1.719856ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:07:11Z"
    - latency: 1.774933ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:06:11Z"
    - latency: 1.808059ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:05:11Z"
    - latency: 2.02166ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:04:11Z"
    - latency: 2.083493ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:03:11Z"
    - latency: 1.884281ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:02:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:22:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-165-to-network-check-target-ip-10-0-141-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-165.ec2.internal
      uid: 5755a809-67af-40ae-9e12-251c25fdf94c
    resourceVersion: "83253"
    uid: 5dbb5229-d734-46ab-b885-aaa728024932
  spec:
    sourcePod: network-check-source-65bdbbff45-7gxbk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T12:29:11Z"
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.071303ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:11:11Z"
    - latency: 1.087773ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:10:11Z"
    - latency: 943.544µs
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:09:11Z"
    - latency: 878.71µs
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:08:11Z"
    - latency: 943.472µs
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:07:11Z"
    - latency: 1.109127ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:06:11Z"
    - latency: 1.40478ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:05:11Z"
    - latency: 1.044871ms
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:04:11Z"
    - latency: 899.591µs
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:03:11Z"
    - latency: 868.964µs
      message: 'network-check-target-ip-10-0-141-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:02:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:22:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-165-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-165.ec2.internal
      uid: 5755a809-67af-40ae-9e12-251c25fdf94c
    resourceVersion: "95619"
    uid: 781a66fc-568a-47d8-a682-11e3cee118b2
  spec:
    sourcePod: network-check-source-65bdbbff45-7gxbk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T12:28:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 864.171µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:16:11Z"
    - latency: 1.83001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:16:11Z"
    - latency: 1.384377ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:15:11Z"
    - latency: 2.015277ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:15:11Z"
    - latency: 1.264057ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:14:11Z"
    - latency: 2.242834ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:14:11Z"
    - latency: 864.536µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:13:11Z"
    - latency: 1.982ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:13:11Z"
    - latency: 1.083817ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:12:11Z"
    - latency: 1.890618ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:12:11Z"
kind: List
metadata:
  resourceVersion: ""