apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:13:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: 6133883a-3cec-46aa-b374-03a84f07f1b9
    resourceVersion: "64310"
    uid: 7aafe251-85c8-4401-ac47-6e063155b323
  spec:
    sourcePod: network-check-source-7d88cb55d8-75wz7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:20:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.25965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:55:15Z"
    - latency: 963.125µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:54:15Z"
    - latency: 1.581245ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:53:15Z"
    - latency: 1.15724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:52:15Z"
    - latency: 793.738µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:51:15Z"
    - latency: 1.598066ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:50:15Z"
    - latency: 1.126833ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:49:15Z"
    - latency: 903.938µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:48:15Z"
    - latency: 1.192863ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:47:15Z"
    - latency: 1.240279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:46:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:13:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: 6133883a-3cec-46aa-b374-03a84f07f1b9
    resourceVersion: "70975"
    uid: ff2d80af-f57b-43ac-a5ca-9c42e29387df
  spec:
    sourcePod: network-check-source-7d88cb55d8-75wz7
    targetEndpoint: a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:19:15Z"
      message: 'load-balancer-api-external: tcp connection to a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.300454ms
      message: 'load-balancer-api-external: tcp connection to a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:15Z"
    - latency: 12.715207ms
      message: 'load-balancer-api-external: resolved host name a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:01:15Z"
    - latency: 4.102623ms
      message: 'load-balancer-api-external: tcp connection to a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:00:15Z"
    - latency: 15.16619ms
      message: 'load-balancer-api-external: resolved host name a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:00:15Z"
    - latency: 3.481512ms
      message: 'load-balancer-api-external: tcp connection to a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:59:15Z"
    - latency: 6.667379ms
      message: 'load-balancer-api-external: resolved host name a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T17:59:15Z"
    - latency: 3.799931ms
      message: 'load-balancer-api-external: tcp connection to a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:58:15Z"
    - latency: 7.249577ms
      message: 'load-balancer-api-external: resolved host name a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T17:58:15Z"
    - latency: 3.618559ms
      message: 'load-balancer-api-external: tcp connection to a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:57:15Z"
    - latency: 8.895164ms
      message: 'load-balancer-api-external: resolved host name a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T17:57:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:13:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: 6133883a-3cec-46aa-b374-03a84f07f1b9
    resourceVersion: "70974"
    uid: f852f0ae-46f7-4500-892f-7a36a96241ec
  spec:
    sourcePod: network-check-source-7d88cb55d8-75wz7
    targetEndpoint: a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:19:15Z"
      message: 'load-balancer-api-internal: tcp connection to a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.290764ms
      message: 'load-balancer-api-internal: tcp connection to a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:15Z"
    - latency: 12.618785ms
      message: 'load-balancer-api-internal: resolved host name a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:01:15Z"
    - latency: 3.524559ms
      message: 'load-balancer-api-internal: tcp connection to a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:00:15Z"
    - latency: 15.211594ms
      message: 'load-balancer-api-internal: resolved host name a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:00:15Z"
    - latency: 3.501678ms
      message: 'load-balancer-api-internal: tcp connection to a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:59:15Z"
    - latency: 6.697346ms
      message: 'load-balancer-api-internal: resolved host name a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T17:59:15Z"
    - latency: 3.805299ms
      message: 'load-balancer-api-internal: tcp connection to a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:58:15Z"
    - latency: 7.298951ms
      message: 'load-balancer-api-internal: resolved host name a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T17:58:15Z"
    - latency: 4.276971ms
      message: 'load-balancer-api-internal: tcp connection to a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:57:15Z"
    - latency: 8.957295ms
      message: 'load-balancer-api-internal: resolved host name a2c3fb584dbc14de6ae1a46b8d7740d9-aa80dd68c53f1473.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T17:57:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:13:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-network-check-target-ip-10-0-130-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: 6133883a-3cec-46aa-b374-03a84f07f1b9
    resourceVersion: "64306"
    uid: 487d37a2-d55f-48d6-8088-a6ee09ae1c15
  spec:
    sourcePod: network-check-source-7d88cb55d8-75wz7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:20:15Z"
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 913.366µs
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:55:15Z"
    - latency: 832.054µs
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:54:15Z"
    - latency: 931.588µs
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:53:15Z"
    - latency: 854.534µs
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:52:15Z"
    - latency: 928.767µs
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:51:15Z"
    - latency: 1.679745ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:50:15Z"
    - latency: 959.953µs
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:49:15Z"
    - latency: 945.054µs
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:48:15Z"
    - latency: 968.914µs
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:47:15Z"
    - latency: 942.927µs
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:46:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:13:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-network-check-target-ip-10-0-139-46
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: 6133883a-3cec-46aa-b374-03a84f07f1b9
    resourceVersion: "64307"
    uid: 71833fa9-dcb9-4b10-a881-9504b542ea99
  spec:
    sourcePod: network-check-source-7d88cb55d8-75wz7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:20:15Z"
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.152471ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:55:15Z"
    - latency: 1.817089ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:54:15Z"
    - latency: 2.204075ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:53:15Z"
    - latency: 2.257436ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:52:15Z"
    - latency: 1.940702ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:51:15Z"
    - latency: 2.351442ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:50:15Z"
    - latency: 2.19705ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:49:15Z"
    - latency: 2.213992ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:48:15Z"
    - latency: 2.15473ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:47:15Z"
    - latency: 2.080727ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:46:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:13:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-network-check-target-ip-10-0-140-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: 6133883a-3cec-46aa-b374-03a84f07f1b9
    resourceVersion: "64309"
    uid: 6cb8bd97-d9bc-46ed-b9c8-b6be697d28fe
  spec:
    sourcePod: network-check-source-7d88cb55d8-75wz7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:20:15Z"
      message: 'network-check-target-ip-10-0-140-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.119631ms
      message: 'network-check-target-ip-10-0-140-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:55:15Z"
    - latency: 1.994895ms
      message: 'network-check-target-ip-10-0-140-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:54:15Z"
    - latency: 1.978969ms
      message: 'network-check-target-ip-10-0-140-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:53:15Z"
    - latency: 2.097918ms
      message: 'network-check-target-ip-10-0-140-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:52:15Z"
    - latency: 2.31172ms
      message: 'network-check-target-ip-10-0-140-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:51:15Z"
    - latency: 2.406643ms
      message: 'network-check-target-ip-10-0-140-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:50:15Z"
    - latency: 2.361503ms
      message: 'network-check-target-ip-10-0-140-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:49:15Z"
    - latency: 2.099619ms
      message: 'network-check-target-ip-10-0-140-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:48:15Z"
    - latency: 2.036497ms
      message: 'network-check-target-ip-10-0-140-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:47:15Z"
    - latency: 2.125906ms
      message: 'network-check-target-ip-10-0-140-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:46:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:13:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: 6133883a-3cec-46aa-b374-03a84f07f1b9
    resourceVersion: "70973"
    uid: a558addf-a425-4ab3-ae98-b8bd1a974833
  spec:
    sourcePod: network-check-source-7d88cb55d8-75wz7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:19:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 956.738µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:15Z"
    - latency: 1.792456ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:01:15Z"
    - latency: 982.115µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:00:15Z"
    - latency: 1.942573ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:00:15Z"
    - latency: 940.501µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:59:15Z"
    - latency: 1.990096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T17:59:15Z"
    - latency: 975.178µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:58:15Z"
    - latency: 2.236195ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T17:58:15Z"
    - latency: 1.00541ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:57:15Z"
    - latency: 2.049238ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T17:57:15Z"
kind: List
metadata:
  resourceVersion: ""