apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:21:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 36794e72-1006-442a-b2f7-21cf0e1f1388
    resourceVersion: "22407"
    uid: 8590fc24-7fd0-4b97-bae5-f2f118f8393a
  spec:
    sourcePod: network-check-source-56499946bc-j2sbp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:28:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 926.631µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:42:23Z"
    - latency: 962.382µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:41:23Z"
    - latency: 1.189291ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:40:23Z"
    - latency: 1.128242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:23Z"
    - latency: 948.216µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:38:23Z"
    - latency: 889.001µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:37:23Z"
    - latency: 1.138402ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:36:23Z"
    - latency: 1.125225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:35:23Z"
    - latency: 1.015549ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:34:23Z"
    - latency: 940.787µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:33:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:21:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 36794e72-1006-442a-b2f7-21cf0e1f1388
    resourceVersion: "21023"
    uid: b1385dba-2483-417e-9da4-8a4645896bc6
  spec:
    sourcePod: network-check-source-56499946bc-j2sbp
    targetEndpoint: ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:27:23Z"
      message: 'load-balancer-api-external: tcp connection to ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.610724ms
      message: 'load-balancer-api-external: tcp connection to ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:23Z"
    - latency: 7.604155ms
      message: 'load-balancer-api-external: resolved host name ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:39:23Z"
    - latency: 5.977683ms
      message: 'load-balancer-api-external: tcp connection to ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:38:23Z"
    - latency: 8.113987ms
      message: 'load-balancer-api-external: resolved host name ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:38:23Z"
    - latency: 4.772499ms
      message: 'load-balancer-api-external: tcp connection to ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:37:23Z"
    - latency: 6.765533ms
      message: 'load-balancer-api-external: resolved host name ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:37:23Z"
    - latency: 5.198291ms
      message: 'load-balancer-api-external: tcp connection to ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:36:23Z"
    - latency: 7.113514ms
      message: 'load-balancer-api-external: resolved host name ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:36:23Z"
    - latency: 4.760078ms
      message: 'load-balancer-api-external: tcp connection to ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:35:23Z"
    - latency: 8.214843ms
      message: 'load-balancer-api-external: resolved host name ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:35:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:21:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 36794e72-1006-442a-b2f7-21cf0e1f1388
    resourceVersion: "21022"
    uid: 99fb9967-e62a-45fd-8908-561ef02ec623
  spec:
    sourcePod: network-check-source-56499946bc-j2sbp
    targetEndpoint: ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:27:23Z"
      message: 'load-balancer-api-internal: tcp connection to ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.264509ms
      message: 'load-balancer-api-internal: tcp connection to ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:23Z"
    - latency: 7.657305ms
      message: 'load-balancer-api-internal: resolved host name ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:39:23Z"
    - latency: 5.977212ms
      message: 'load-balancer-api-internal: tcp connection to ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:38:23Z"
    - latency: 8.231559ms
      message: 'load-balancer-api-internal: resolved host name ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:38:23Z"
    - latency: 4.781808ms
      message: 'load-balancer-api-internal: tcp connection to ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:37:23Z"
    - latency: 6.80415ms
      message: 'load-balancer-api-internal: resolved host name ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:37:23Z"
    - latency: 5.217965ms
      message: 'load-balancer-api-internal: tcp connection to ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:36:23Z"
    - latency: 7.254303ms
      message: 'load-balancer-api-internal: resolved host name ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:36:23Z"
    - latency: 4.707547ms
      message: 'load-balancer-api-internal: tcp connection to ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:35:23Z"
    - latency: 8.289901ms
      message: 'load-balancer-api-internal: resolved host name ac2f222bd98fd4bf186b91a60a17963e-7a3c1ecb8faba3b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:35:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:21:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-network-check-target-ip-10-0-129-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 36794e72-1006-442a-b2f7-21cf0e1f1388
    resourceVersion: "22406"
    uid: e0912d9f-db3f-42c5-9da8-133a7714ec9e
  spec:
    sourcePod: network-check-source-56499946bc-j2sbp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:28:23Z"
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.346751ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:42:23Z"
    - latency: 2.575538ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:41:23Z"
    - latency: 2.388866ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:40:23Z"
    - latency: 2.307568ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:23Z"
    - latency: 2.248233ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:38:23Z"
    - latency: 2.300809ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:37:23Z"
    - latency: 2.499232ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:36:23Z"
    - latency: 2.359272ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:35:23Z"
    - latency: 2.343602ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:34:23Z"
    - latency: 2.357617ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:33:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:21:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-network-check-target-ip-10-0-136-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 36794e72-1006-442a-b2f7-21cf0e1f1388
    resourceVersion: "22404"
    uid: f920d2c2-0d95-4523-8233-0a68ca20b1f0
  spec:
    sourcePod: network-check-source-56499946bc-j2sbp
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:28:23Z"
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.104739ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:42:23Z"
    - latency: 1.025912ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:41:23Z"
    - latency: 1.375517ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:40:23Z"
    - latency: 1.312541ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:23Z"
    - latency: 977.056µs
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:38:23Z"
    - latency: 1.38953ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:37:23Z"
    - latency: 951.867µs
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:36:23Z"
    - latency: 1.012072ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:35:23Z"
    - latency: 965.42µs
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:34:23Z"
    - latency: 1.051567ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:33:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:21:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-network-check-target-ip-10-0-137-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 36794e72-1006-442a-b2f7-21cf0e1f1388
    resourceVersion: "22405"
    uid: 52adc79b-253c-4208-8b5a-e70be7487ecb
  spec:
    sourcePod: network-check-source-56499946bc-j2sbp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:28:23Z"
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.372216ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:42:23Z"
    - latency: 2.423566ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:41:23Z"
    - latency: 2.195262ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:40:23Z"
    - latency: 2.209498ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:23Z"
    - latency: 1.977347ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:38:23Z"
    - latency: 2.076181ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:37:23Z"
    - latency: 2.347122ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:36:23Z"
    - latency: 2.296575ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:35:23Z"
    - latency: 2.314547ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:34:23Z"
    - latency: 1.892403ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:33:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:21:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 36794e72-1006-442a-b2f7-21cf0e1f1388
    resourceVersion: "21021"
    uid: 3d0c5011-bdbe-4cee-af63-fc0c8edbc445
  spec:
    sourcePod: network-check-source-56499946bc-j2sbp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:27:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 859.97µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:23Z"
    - latency: 1.85423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:39:23Z"
    - latency: 1.101751ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:38:23Z"
    - latency: 2.13727ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:38:23Z"
    - latency: 801.199µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:37:23Z"
    - latency: 1.708251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:37:23Z"
    - latency: 967.643µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:36:23Z"
    - latency: 2.4639ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:36:23Z"
    - latency: 986.491µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:35:23Z"
    - latency: 1.77619ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:35:23Z"
kind: List
metadata:
  resourceVersion: ""