apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-227-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-227.ec2.internal
      uid: 1220e339-780c-4d5c-aec1-eecc5da7c3e8
    resourceVersion: "22889"
    uid: 3766327b-151f-446e-8aed-62cfa05d307a
  spec:
    sourcePod: network-check-source-65bdbbff45-d724s
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:59:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 980.185µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:13:07Z"
    - latency: 946.187µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:12:07Z"
    - latency: 1.226575ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:11:07Z"
    - latency: 1.193721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:10:07Z"
    - latency: 1.074807ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:09:07Z"
    - latency: 887.604µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:08:07Z"
    - latency: 1.105704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:07:07Z"
    - latency: 1.045423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:06:07Z"
    - latency: 886.872µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:05:07Z"
    - latency: 1.672297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:04:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-227-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-227.ec2.internal
      uid: 1220e339-780c-4d5c-aec1-eecc5da7c3e8
    resourceVersion: "24326"
    uid: bbbf73fa-63f3-470e-b1a7-6ad6e4a0ea11
  spec:
    sourcePod: network-check-source-65bdbbff45-d724s
    targetEndpoint: a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:58:07Z"
      message: 'load-balancer-api-external: tcp connection to a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.133513ms
      message: 'load-balancer-api-external: tcp connection to a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:16:07Z"
    - latency: 8.165559ms
      message: 'load-balancer-api-external: resolved host name a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:16:07Z"
    - latency: 5.481319ms
      message: 'load-balancer-api-external: tcp connection to a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:15:07Z"
    - latency: 6.958853ms
      message: 'load-balancer-api-external: resolved host name a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:15:07Z"
    - latency: 5.745829ms
      message: 'load-balancer-api-external: tcp connection to a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:14:07Z"
    - latency: 6.382523ms
      message: 'load-balancer-api-external: resolved host name a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:14:07Z"
    - latency: 4.99685ms
      message: 'load-balancer-api-external: tcp connection to a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:13:07Z"
    - latency: 7.849523ms
      message: 'load-balancer-api-external: resolved host name a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:13:07Z"
    - latency: 6.767228ms
      message: 'load-balancer-api-external: tcp connection to a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:12:07Z"
    - latency: 6.354106ms
      message: 'load-balancer-api-external: resolved host name a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:12:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-227-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-227.ec2.internal
      uid: 1220e339-780c-4d5c-aec1-eecc5da7c3e8
    resourceVersion: "24325"
    uid: dbe1f4bb-2963-4331-a55c-fe41baa3d1a3
  spec:
    sourcePod: network-check-source-65bdbbff45-d724s
    targetEndpoint: a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:58:07Z"
      message: 'load-balancer-api-internal: tcp connection to a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.553779ms
      message: 'load-balancer-api-internal: tcp connection to a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:16:07Z"
    - latency: 8.109959ms
      message: 'load-balancer-api-internal: resolved host name a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:16:07Z"
    - latency: 5.470969ms
      message: 'load-balancer-api-internal: tcp connection to a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:15:07Z"
    - latency: 6.999631ms
      message: 'load-balancer-api-internal: resolved host name a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:15:07Z"
    - latency: 5.782552ms
      message: 'load-balancer-api-internal: tcp connection to a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:14:07Z"
    - latency: 6.43515ms
      message: 'load-balancer-api-internal: resolved host name a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:14:07Z"
    - latency: 4.991123ms
      message: 'load-balancer-api-internal: tcp connection to a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:13:07Z"
    - latency: 7.812785ms
      message: 'load-balancer-api-internal: resolved host name a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:13:07Z"
    - latency: 6.47039ms
      message: 'load-balancer-api-internal: tcp connection to a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:12:07Z"
    - latency: 6.381957ms
      message: 'load-balancer-api-internal: resolved host name a23a28b94a9b34090935ed32a31d2bfc-f8a65a38a32547a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:12:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-227-to-network-check-target-ip-10-0-132-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-227.ec2.internal
      uid: 1220e339-780c-4d5c-aec1-eecc5da7c3e8
    resourceVersion: "22887"
    uid: b3f94fc4-4773-47a6-b54f-d76ffc72e211
  spec:
    sourcePod: network-check-source-65bdbbff45-d724s
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:59:07Z"
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.101613ms
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:13:07Z"
    - latency: 2.567253ms
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:12:07Z"
    - latency: 2.425281ms
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:11:07Z"
    - latency: 2.203889ms
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:10:07Z"
    - latency: 2.255759ms
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:09:07Z"
    - latency: 2.296658ms
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:08:07Z"
    - latency: 2.316317ms
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:07:07Z"
    - latency: 2.535803ms
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:06:07Z"
    - latency: 2.34577ms
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:05:07Z"
    - latency: 2.37167ms
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:04:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-227-to-network-check-target-ip-10-0-141-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-227.ec2.internal
      uid: 1220e339-780c-4d5c-aec1-eecc5da7c3e8
    resourceVersion: "22888"
    uid: bda56869-7ca0-4ae7-b63c-a5716135c257
  spec:
    sourcePod: network-check-source-65bdbbff45-d724s
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:59:07Z"
      message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.125857ms
      message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:13:07Z"
    - latency: 1.964067ms
      message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:12:07Z"
    - latency: 1.965446ms
      message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:11:07Z"
    - latency: 1.785115ms
      message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:10:07Z"
    - latency: 1.967671ms
      message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:09:07Z"
    - latency: 1.919223ms
      message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:08:07Z"
    - latency: 2.043766ms
      message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:07:07Z"
    - latency: 2.065846ms
      message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:06:07Z"
    - latency: 1.833776ms
      message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:05:07Z"
    - latency: 1.959243ms
      message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:04:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-227-to-network-check-target-ip-10-0-143-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-227.ec2.internal
      uid: 1220e339-780c-4d5c-aec1-eecc5da7c3e8
    resourceVersion: "22886"
    uid: 8419299c-3e0b-40dd-b47e-1fa2240ec057
  spec:
    sourcePod: network-check-source-65bdbbff45-d724s
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:59:07Z"
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.335214ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:13:07Z"
    - latency: 922.368µs
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:12:07Z"
    - latency: 880.188µs
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:11:07Z"
    - latency: 951.635µs
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:10:07Z"
    - latency: 960.551µs
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:09:07Z"
    - latency: 1.284759ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:08:07Z"
    - latency: 1.332337ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:07:07Z"
    - latency: 902.215µs
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:06:07Z"
    - latency: 1.027497ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:05:07Z"
    - latency: 1.033287ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:04:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-227-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-227.ec2.internal
      uid: 1220e339-780c-4d5c-aec1-eecc5da7c3e8
    resourceVersion: "24324"
    uid: cc0c7df0-0524-4485-8de7-fec1cc26314b
  spec:
    sourcePod: network-check-source-65bdbbff45-d724s
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:58:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 821.67µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:16:07Z"
    - latency: 1.865023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:16:07Z"
    - latency: 1.029381ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:15:07Z"
    - latency: 1.702911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:15:07Z"
    - latency: 1.041891ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:14:07Z"
    - latency: 1.858596ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:14:07Z"
    - latency: 993.018µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:13:07Z"
    - latency: 1.797672ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:13:07Z"
    - latency: 945.036µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:12:07Z"
    - latency: 1.679326ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:12:07Z"
kind: List
metadata:
  resourceVersion: ""