apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T09:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-133-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-133.ec2.internal
      uid: 672d13a5-18ad-4160-9eb3-0aa7f9803f60
    resourceVersion: "63223"
    uid: 4659aefc-7317-481d-baa9-65395bb7ba4c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xpb85
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T09:49:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 841.376µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:24:13Z"
    - latency: 969.814µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:23:13Z"
    - latency: 913.96µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:22:13Z"
    - latency: 1.272559ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:21:13Z"
    - latency: 1.293315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:20:13Z"
    - latency: 909.071µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:19:13Z"
    - latency: 1.211532ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:18:13Z"
    - latency: 947.719µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:17:13Z"
    - latency: 991µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:16:13Z"
    - latency: 1.294969ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:15:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T09:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-133-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-133.ec2.internal
      uid: 672d13a5-18ad-4160-9eb3-0aa7f9803f60
    resourceVersion: "63225"
    uid: f554e68c-d573-4266-9437-62ad6373eebd
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xpb85
    targetEndpoint: a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T09:48:13Z"
      message: 'load-balancer-api-external: tcp connection to a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.48619ms
      message: 'load-balancer-api-external: tcp connection to a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:24:13Z"
    - latency: 7.563541ms
      message: 'load-balancer-api-external: resolved host name a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:24:13Z"
    - latency: 4.148912ms
      message: 'load-balancer-api-external: tcp connection to a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:23:13Z"
    - latency: 7.514337ms
      message: 'load-balancer-api-external: resolved host name a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:23:13Z"
    - latency: 4.777795ms
      message: 'load-balancer-api-external: tcp connection to a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:22:13Z"
    - latency: 6.22159ms
      message: 'load-balancer-api-external: resolved host name a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:22:13Z"
    - latency: 3.496231ms
      message: 'load-balancer-api-external: tcp connection to a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:21:13Z"
    - latency: 7.152519ms
      message: 'load-balancer-api-external: resolved host name a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:21:13Z"
    - latency: 4.002758ms
      message: 'load-balancer-api-external: tcp connection to a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:20:13Z"
    - latency: 7.301054ms
      message: 'load-balancer-api-external: resolved host name a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:20:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T09:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-133-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-133.ec2.internal
      uid: 672d13a5-18ad-4160-9eb3-0aa7f9803f60
    resourceVersion: "63224"
    uid: 648cc7ed-3190-4ce4-b0f8-71c37a94fbe7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xpb85
    targetEndpoint: a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T09:48:13Z"
      message: 'load-balancer-api-internal: tcp connection to a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.564615ms
      message: 'load-balancer-api-internal: tcp connection to a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:24:13Z"
    - latency: 7.506107ms
      message: 'load-balancer-api-internal: resolved host name a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:24:13Z"
    - latency: 4.01161ms
      message: 'load-balancer-api-internal: tcp connection to a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:23:13Z"
    - latency: 7.383023ms
      message: 'load-balancer-api-internal: resolved host name a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:23:13Z"
    - latency: 4.812948ms
      message: 'load-balancer-api-internal: tcp connection to a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:22:13Z"
    - latency: 6.13154ms
      message: 'load-balancer-api-internal: resolved host name a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:22:13Z"
    - latency: 4.311293ms
      message: 'load-balancer-api-internal: tcp connection to a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:21:13Z"
    - latency: 7.07382ms
      message: 'load-balancer-api-internal: resolved host name a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:21:13Z"
    - latency: 4.642298ms
      message: 'load-balancer-api-internal: tcp connection to a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:20:13Z"
    - latency: 7.186711ms
      message: 'load-balancer-api-internal: resolved host name a7b96ae60c8a94500b31f5cf65e477ab-eeb1d14d881e3edf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:20:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T09:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-133-to-network-check-target-ip-10-0-140-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-133.ec2.internal
      uid: 672d13a5-18ad-4160-9eb3-0aa7f9803f60
    resourceVersion: "63221"
    uid: f1133858-00a7-4a65-a38e-b25f91f76536
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xpb85
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T09:49:13Z"
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.534251ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:24:13Z"
    - latency: 2.639541ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:23:13Z"
    - latency: 2.862096ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:22:13Z"
    - latency: 2.596626ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:21:13Z"
    - latency: 2.413971ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:20:13Z"
    - latency: 2.270764ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:19:13Z"
    - latency: 2.364357ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:18:13Z"
    - latency: 2.532209ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:17:13Z"
    - latency: 2.689615ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:16:13Z"
    - latency: 2.58176ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:15:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T09:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-133-to-network-check-target-ip-10-0-140-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-133.ec2.internal
      uid: 672d13a5-18ad-4160-9eb3-0aa7f9803f60
    resourceVersion: "63220"
    uid: cdba7c4c-a475-40c9-90ca-86e9dbb4d07e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xpb85
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T09:49:13Z"
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.785435ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:24:13Z"
    - latency: 1.801717ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:23:13Z"
    - latency: 2.148522ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:22:13Z"
    - latency: 2.337696ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:21:13Z"
    - latency: 1.871817ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:20:13Z"
    - latency: 1.696956ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:19:13Z"
    - latency: 2.384002ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:18:13Z"
    - latency: 2.06483ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:17:13Z"
    - latency: 2.216757ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:16:13Z"
    - latency: 2.07564ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:15:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T09:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-133-to-network-check-target-ip-10-0-142-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-133.ec2.internal
      uid: 672d13a5-18ad-4160-9eb3-0aa7f9803f60
    resourceVersion: "63219"
    uid: f493f56f-235f-47c6-a028-994eb71d5bce
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xpb85
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T09:49:13Z"
      message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.282µs
      message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:24:13Z"
    - latency: 897.539µs
      message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:23:13Z"
    - latency: 1.319827ms
      message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:22:13Z"
    - latency: 1.387071ms
      message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:21:13Z"
    - latency: 845.342µs
      message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:20:13Z"
    - latency: 857.203µs
      message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:19:13Z"
    - latency: 1.020977ms
      message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:18:13Z"
    - latency: 873.873µs
      message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:17:13Z"
    - latency: 998.718µs
      message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:16:13Z"
    - latency: 991.143µs
      message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:15:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T09:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-133-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-133.ec2.internal
      uid: 672d13a5-18ad-4160-9eb3-0aa7f9803f60
    resourceVersion: "63222"
    uid: c76ea074-e7d6-44cd-a3de-62f865a02f57
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xpb85
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T09:48:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.091495ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:24:13Z"
    - latency: 2.530234ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:24:13Z"
    - latency: 887.584µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:23:13Z"
    - latency: 1.935154ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:23:13Z"
    - latency: 932.391µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:22:13Z"
    - latency: 1.708952ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:22:13Z"
    - latency: 977.001µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:21:13Z"
    - latency: 1.821ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:21:13Z"
    - latency: 1.184097ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:20:13Z"
    - latency: 1.831947ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:20:13Z"
kind: List
metadata:
  resourceVersion: ""