apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-169-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-169.ec2.internal
      uid: 3ac154da-294e-425f-946f-772b811b6c4d
    resourceVersion: "49255"
    uid: 4434fbf9-5ade-4d77-8fc0-b0875720e0c6
  spec:
    sourcePod: network-check-source-989f8b8dc-c9zph
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:30:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.035349ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:51:03Z"
    - latency: 997.426µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:50:03Z"
    - latency: 1.114147ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:49:03Z"
    - latency: 856.793µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:48:03Z"
    - latency: 1.22204ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:47:03Z"
    - latency: 940.214µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:46:03Z"
    - latency: 1.14086ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:45:03Z"
    - latency: 1.162663ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:44:03Z"
    - latency: 1.087024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:43:03Z"
    - latency: 901.03µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:42:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-169-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-169.ec2.internal
      uid: 3ac154da-294e-425f-946f-772b811b6c4d
    resourceVersion: "52118"
    uid: a535009a-4007-4b16-a6f1-b4b9f936ada8
  spec:
    sourcePod: network-check-source-989f8b8dc-c9zph
    targetEndpoint: a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:29:04Z"
      message: 'load-balancer-api-external: tcp connection to a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.972492ms
      message: 'load-balancer-api-external: tcp connection to a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:53:03Z"
    - latency: 8.7076ms
      message: 'load-balancer-api-external: resolved host name a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:53:03Z"
    - latency: 3.861372ms
      message: 'load-balancer-api-external: tcp connection to a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:52:03Z"
    - latency: 7.932806ms
      message: 'load-balancer-api-external: resolved host name a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:52:03Z"
    - latency: 4.349921ms
      message: 'load-balancer-api-external: tcp connection to a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:51:03Z"
    - latency: 13.006545ms
      message: 'load-balancer-api-external: resolved host name a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:51:03Z"
    - latency: 3.889792ms
      message: 'load-balancer-api-external: tcp connection to a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:50:03Z"
    - latency: 8.558627ms
      message: 'load-balancer-api-external: resolved host name a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:50:03Z"
    - latency: 4.485504ms
      message: 'load-balancer-api-external: tcp connection to a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:49:03Z"
    - latency: 8.211817ms
      message: 'load-balancer-api-external: resolved host name a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:49:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-169-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-169.ec2.internal
      uid: 3ac154da-294e-425f-946f-772b811b6c4d
    resourceVersion: "52119"
    uid: 39c4364f-a918-42da-9f83-a061045c7277
  spec:
    sourcePod: network-check-source-989f8b8dc-c9zph
    targetEndpoint: a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:29:04Z"
      message: 'load-balancer-api-internal: tcp connection to a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.506546ms
      message: 'load-balancer-api-internal: tcp connection to a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:53:03Z"
    - latency: 8.632274ms
      message: 'load-balancer-api-internal: resolved host name a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:53:03Z"
    - latency: 3.823003ms
      message: 'load-balancer-api-internal: tcp connection to a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:52:03Z"
    - latency: 8.004808ms
      message: 'load-balancer-api-internal: resolved host name a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:52:03Z"
    - latency: 4.343963ms
      message: 'load-balancer-api-internal: tcp connection to a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:51:03Z"
    - latency: 13.021609ms
      message: 'load-balancer-api-internal: resolved host name a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:51:03Z"
    - latency: 3.887339ms
      message: 'load-balancer-api-internal: tcp connection to a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:50:03Z"
    - latency: 8.490239ms
      message: 'load-balancer-api-internal: resolved host name a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:50:03Z"
    - latency: 4.546795ms
      message: 'load-balancer-api-internal: tcp connection to a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:49:03Z"
    - latency: 8.144749ms
      message: 'load-balancer-api-internal: resolved host name a2c6a66dccd6d41879b63f02a8345e96-c6082d3beb4dc2bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:49:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-169-to-network-check-target-ip-10-0-128-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-169.ec2.internal
      uid: 3ac154da-294e-425f-946f-772b811b6c4d
    resourceVersion: "49253"
    uid: ea9722e3-d00e-4035-a500-bc62c4b6e8a1
  spec:
    sourcePod: network-check-source-989f8b8dc-c9zph
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:30:03Z"
      message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.864054ms
      message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:51:03Z"
    - latency: 2.137356ms
      message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:50:03Z"
    - latency: 1.907351ms
      message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:49:03Z"
    - latency: 1.899589ms
      message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:48:03Z"
    - latency: 2.048903ms
      message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:47:03Z"
    - latency: 2.052844ms
      message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:46:03Z"
    - latency: 2.326708ms
      message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:45:03Z"
    - latency: 2.06476ms
      message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:44:03Z"
    - latency: 2.031458ms
      message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:43:03Z"
    - latency: 1.961519ms
      message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:42:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-169-to-network-check-target-ip-10-0-138-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-169.ec2.internal
      uid: 3ac154da-294e-425f-946f-772b811b6c4d
    resourceVersion: "49252"
    uid: 1a597f6f-b55d-4fc3-9938-36e5c442aa94
  spec:
    sourcePod: network-check-source-989f8b8dc-c9zph
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:30:03Z"
      message: 'network-check-target-ip-10-0-138-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.94µs
      message: 'network-check-target-ip-10-0-138-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:51:03Z"
    - latency: 1.288009ms
      message: 'network-check-target-ip-10-0-138-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:50:03Z"
    - latency: 716.026µs
      message: 'network-check-target-ip-10-0-138-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:49:03Z"
    - latency: 792.305µs
      message: 'network-check-target-ip-10-0-138-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:48:03Z"
    - latency: 995.898µs
      message: 'network-check-target-ip-10-0-138-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:47:03Z"
    - latency: 747.676µs
      message: 'network-check-target-ip-10-0-138-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:46:03Z"
    - latency: 821.424µs
      message: 'network-check-target-ip-10-0-138-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:45:03Z"
    - latency: 741.702µs
      message: 'network-check-target-ip-10-0-138-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:44:03Z"
    - latency: 768.381µs
      message: 'network-check-target-ip-10-0-138-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:43:03Z"
    - latency: 857.145µs
      message: 'network-check-target-ip-10-0-138-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:42:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-169-to-network-check-target-ip-10-0-143-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-169.ec2.internal
      uid: 3ac154da-294e-425f-946f-772b811b6c4d
    resourceVersion: "49254"
    uid: e218ceae-597e-4aa3-bc0a-8d272566a0c4
  spec:
    sourcePod: network-check-source-989f8b8dc-c9zph
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:30:03Z"
      message: 'network-check-target-ip-10-0-143-138: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.070714ms
      message: 'network-check-target-ip-10-0-143-138: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:51:03Z"
    - latency: 1.951231ms
      message: 'network-check-target-ip-10-0-143-138: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:50:03Z"
    - latency: 2.098046ms
      message: 'network-check-target-ip-10-0-143-138: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:49:03Z"
    - latency: 1.468004ms
      message: 'network-check-target-ip-10-0-143-138: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:48:03Z"
    - latency: 2.034517ms
      message: 'network-check-target-ip-10-0-143-138: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:47:03Z"
    - latency: 1.905585ms
      message: 'network-check-target-ip-10-0-143-138: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:46:03Z"
    - latency: 2.235249ms
      message: 'network-check-target-ip-10-0-143-138: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:45:03Z"
    - latency: 2.082557ms
      message: 'network-check-target-ip-10-0-143-138: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:44:03Z"
    - latency: 2.640543ms
      message: 'network-check-target-ip-10-0-143-138: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:43:03Z"
    - latency: 1.779877ms
      message: 'network-check-target-ip-10-0-143-138: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:42:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-169-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-169.ec2.internal
      uid: 3ac154da-294e-425f-946f-772b811b6c4d
    resourceVersion: "52115"
    uid: 7002da93-cd18-487c-a488-576d90e68ff8
  spec:
    sourcePod: network-check-source-989f8b8dc-c9zph
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:29:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 997.979µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:53:03Z"
    - latency: 1.773365ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:53:03Z"
    - latency: 842.705µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:52:03Z"
    - latency: 1.685198ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:52:03Z"
    - latency: 1.117943ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:51:03Z"
    - latency: 1.882972ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:51:03Z"
    - latency: 1.23454ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:50:03Z"
    - latency: 1.574595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:50:03Z"
    - latency: 1.000075ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:49:03Z"
    - latency: 1.866032ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T21:49:03Z"
kind: List
metadata:
  resourceVersion: ""