apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:46:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-183-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-183.us-east-2.compute.internal
      uid: a1e78cb4-1d60-4d20-8c14-68f22d5afca2
    resourceVersion: "44457"
    uid: 513023ed-709c-4be9-8edf-940abbce8808
  spec:
    sourcePod: network-check-source-6f78d59f99-vhbjg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:53:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.587876ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:37Z"
    - latency: 1.035637ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:37Z"
    - latency: 1.266487ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:05:37Z"
    - latency: 1.580572ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:04:37Z"
    - latency: 954.693µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:03:37Z"
    - latency: 1.436171ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:02:37Z"
    - latency: 953.433µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:01:37Z"
    - latency: 2.315973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:00:37Z"
    - latency: 1.353243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:59:37Z"
    - latency: 1.142795ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:58:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:46:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-183-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-183.us-east-2.compute.internal
      uid: a1e78cb4-1d60-4d20-8c14-68f22d5afca2
    resourceVersion: "49171"
    uid: fbbdeb92-f7ca-44f2-9816-2cf17529d2a0
  spec:
    sourcePod: network-check-source-6f78d59f99-vhbjg
    targetEndpoint: ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:52:37Z"
      message: 'load-balancer-api-external: tcp connection to ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.168715ms
      message: 'load-balancer-api-external: tcp connection to ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:10:37Z"
    - latency: 58.151149ms
      message: 'load-balancer-api-external: resolved host name ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:10:37Z"
    - latency: 5.425432ms
      message: 'load-balancer-api-external: tcp connection to ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:09:37Z"
    - latency: 9.594737ms
      message: 'load-balancer-api-external: resolved host name ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:09:37Z"
    - latency: 6.705311ms
      message: 'load-balancer-api-external: tcp connection to ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:08:37Z"
    - latency: 6.945316ms
      message: 'load-balancer-api-external: resolved host name ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:08:37Z"
    - latency: 6.58953ms
      message: 'load-balancer-api-external: tcp connection to ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:37Z"
    - latency: 6.964282ms
      message: 'load-balancer-api-external: resolved host name ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:07:37Z"
    - latency: 5.523659ms
      message: 'load-balancer-api-external: tcp connection to ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:37Z"
    - latency: 7.044797ms
      message: 'load-balancer-api-external: resolved host name ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:06:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:46:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-183-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-183.us-east-2.compute.internal
      uid: a1e78cb4-1d60-4d20-8c14-68f22d5afca2
    resourceVersion: "49172"
    uid: 8fbc1c49-3dd4-4dd4-b8a6-ff894fb8fb91
  spec:
    sourcePod: network-check-source-6f78d59f99-vhbjg
    targetEndpoint: ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:52:37Z"
      message: 'load-balancer-api-internal: tcp connection to ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.009413ms
      message: 'load-balancer-api-internal: tcp connection to ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:10:37Z"
    - latency: 64.434592ms
      message: 'load-balancer-api-internal: resolved host name ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:10:37Z"
    - latency: 5.41312ms
      message: 'load-balancer-api-internal: tcp connection to ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:09:37Z"
    - latency: 9.694665ms
      message: 'load-balancer-api-internal: resolved host name ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:09:37Z"
    - latency: 6.890892ms
      message: 'load-balancer-api-internal: tcp connection to ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:08:37Z"
    - latency: 6.902661ms
      message: 'load-balancer-api-internal: resolved host name ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:08:37Z"
    - latency: 6.605147ms
      message: 'load-balancer-api-internal: tcp connection to ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:37Z"
    - latency: 7.049565ms
      message: 'load-balancer-api-internal: resolved host name ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:07:37Z"
    - latency: 5.538988ms
      message: 'load-balancer-api-internal: tcp connection to ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:37Z"
    - latency: 7.025323ms
      message: 'load-balancer-api-internal: resolved host name ac3c95a2219ae4a22a4983d905ee1a92-462607ba29ccedc4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:06:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:46:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-183-to-network-check-target-ip-10-0-128-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-183.us-east-2.compute.internal
      uid: a1e78cb4-1d60-4d20-8c14-68f22d5afca2
    resourceVersion: "44454"
    uid: 1dba0a39-aa2a-42d8-89c8-141df82b7937
  spec:
    sourcePod: network-check-source-6f78d59f99-vhbjg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:53:37Z"
      message: 'network-check-target-ip-10-0-128-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.229462ms
      message: 'network-check-target-ip-10-0-128-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:37Z"
    - latency: 936.513µs
      message: 'network-check-target-ip-10-0-128-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:37Z"
    - latency: 979.64µs
      message: 'network-check-target-ip-10-0-128-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:05:37Z"
    - latency: 963.672µs
      message: 'network-check-target-ip-10-0-128-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:04:37Z"
    - latency: 992.942µs
      message: 'network-check-target-ip-10-0-128-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:03:37Z"
    - latency: 1.419166ms
      message: 'network-check-target-ip-10-0-128-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:02:37Z"
    - latency: 900.319µs
      message: 'network-check-target-ip-10-0-128-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:01:37Z"
    - latency: 1.193935ms
      message: 'network-check-target-ip-10-0-128-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:00:37Z"
    - latency: 1.256929ms
      message: 'network-check-target-ip-10-0-128-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:59:37Z"
    - latency: 957.911µs
      message: 'network-check-target-ip-10-0-128-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:58:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:46:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-183-to-network-check-target-ip-10-0-131-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-183.us-east-2.compute.internal
      uid: a1e78cb4-1d60-4d20-8c14-68f22d5afca2
    resourceVersion: "44514"
    uid: a8d0ecfe-ff9f-40f3-ab02-18c1ab240313
  spec:
    sourcePod: network-check-source-6f78d59f99-vhbjg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:53:38Z"
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.044932ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:38Z"
    - latency: 1.884899ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:38Z"
    - latency: 1.059737ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:05:38Z"
    - latency: 1.037105ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:04:38Z"
    - latency: 2.316939ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:03:38Z"
    - latency: 2.654174ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:02:38Z"
    - latency: 2.151492ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:01:38Z"
    - latency: 2.135992ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:00:38Z"
    - latency: 1.914149ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:59:38Z"
    - latency: 842.992µs
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:58:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:46:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-183-to-network-check-target-ip-10-0-137-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-183.us-east-2.compute.internal
      uid: a1e78cb4-1d60-4d20-8c14-68f22d5afca2
    resourceVersion: "44456"
    uid: 2c7eb1f8-e983-4867-a391-aaa6cdb839a1
  spec:
    sourcePod: network-check-source-6f78d59f99-vhbjg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:53:37Z"
      message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.297181ms
      message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:37Z"
    - latency: 2.218207ms
      message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:37Z"
    - latency: 2.371624ms
      message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:05:37Z"
    - latency: 2.255923ms
      message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:04:37Z"
    - latency: 2.347561ms
      message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:03:37Z"
    - latency: 2.419597ms
      message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:02:37Z"
    - latency: 2.112397ms
      message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:01:37Z"
    - latency: 3.039063ms
      message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:00:37Z"
    - latency: 2.184359ms
      message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:59:37Z"
    - latency: 2.79877ms
      message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:58:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:46:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-183-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-183.us-east-2.compute.internal
      uid: a1e78cb4-1d60-4d20-8c14-68f22d5afca2
    resourceVersion: "49168"
    uid: 0dc63d92-e729-494b-88aa-c2c4795da4a6
  spec:
    sourcePod: network-check-source-6f78d59f99-vhbjg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:52:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.962584ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:10:37Z"
    - latency: 27.69723ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:10:37Z"
    - latency: 2.190156ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:09:37Z"
    - latency: 1.996095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:09:37Z"
    - latency: 831.473µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:08:37Z"
    - latency: 1.869018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:08:37Z"
    - latency: 2.301619ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:37Z"
    - latency: 1.944977ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:07:37Z"
    - latency: 956.695µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:37Z"
    - latency: 2.07385ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:06:37Z"
kind: List
metadata:
  resourceVersion: ""