apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-109-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-109.ec2.internal
      uid: 44ab1128-f331-44d1-a8f9-6063c84582a8
    resourceVersion: "50131"
    uid: e5fd6888-31bb-41b1-8a43-e72502a19190
  spec:
    sourcePod: network-check-source-989f8b8dc-4kfh8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:40:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 990.38µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:08:05Z"
    - latency: 1.067572ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:07:05Z"
    - latency: 891.307µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:06:05Z"
    - latency: 1.047887ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:05:05Z"
    - latency: 1.014106ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:04:05Z"
    - latency: 1.000364ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:03:05Z"
    - latency: 938.43µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:02:05Z"
    - latency: 1.005662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:01:05Z"
    - latency: 927.132µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:00:05Z"
    - latency: 1.050658ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:59:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-109-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-109.ec2.internal
      uid: 44ab1128-f331-44d1-a8f9-6063c84582a8
    resourceVersion: "50774"
    uid: e2e0f910-3505-40c4-bd7e-a6fddebc6d77
  spec:
    sourcePod: network-check-source-989f8b8dc-4kfh8
    targetEndpoint: aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:39:05Z"
      message: 'load-balancer-api-external: tcp connection to aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.179693ms
      message: 'load-balancer-api-external: tcp connection to aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:09:05Z"
    - latency: 9.597782ms
      message: 'load-balancer-api-external: resolved host name aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:09:05Z"
    - latency: 4.651506ms
      message: 'load-balancer-api-external: tcp connection to aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:08:05Z"
    - latency: 8.35255ms
      message: 'load-balancer-api-external: resolved host name aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:08:05Z"
    - latency: 6.229801ms
      message: 'load-balancer-api-external: tcp connection to aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:07:05Z"
    - latency: 9.359154ms
      message: 'load-balancer-api-external: resolved host name aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:07:05Z"
    - latency: 4.443044ms
      message: 'load-balancer-api-external: tcp connection to aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:06:05Z"
    - latency: 7.545213ms
      message: 'load-balancer-api-external: resolved host name aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:06:05Z"
    - latency: 3.457862ms
      message: 'load-balancer-api-external: tcp connection to aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:05:05Z"
    - latency: 9.955841ms
      message: 'load-balancer-api-external: resolved host name aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:05:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-109-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-109.ec2.internal
      uid: 44ab1128-f331-44d1-a8f9-6063c84582a8
    resourceVersion: "50775"
    uid: bec74245-a759-4406-b121-6563712ad29c
  spec:
    sourcePod: network-check-source-989f8b8dc-4kfh8
    targetEndpoint: aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:39:05Z"
      message: 'load-balancer-api-internal: tcp connection to aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.186165ms
      message: 'load-balancer-api-internal: tcp connection to aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:09:05Z"
    - latency: 9.661884ms
      message: 'load-balancer-api-internal: resolved host name aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:09:05Z"
    - latency: 4.351357ms
      message: 'load-balancer-api-internal: tcp connection to aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:08:05Z"
    - latency: 8.315612ms
      message: 'load-balancer-api-internal: resolved host name aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:08:05Z"
    - latency: 5.906185ms
      message: 'load-balancer-api-internal: tcp connection to aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:07:05Z"
    - latency: 9.431274ms
      message: 'load-balancer-api-internal: resolved host name aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:07:05Z"
    - latency: 4.861538ms
      message: 'load-balancer-api-internal: tcp connection to aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:06:05Z"
    - latency: 7.461072ms
      message: 'load-balancer-api-internal: resolved host name aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:06:05Z"
    - latency: 3.321141ms
      message: 'load-balancer-api-internal: tcp connection to aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:05:05Z"
    - latency: 10.027813ms
      message: 'load-balancer-api-internal: resolved host name aa83d0826f7474e7fb286714692df698-6619dc3dd664048e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:05:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-109-to-network-check-target-ip-10-0-130-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-109.ec2.internal
      uid: 44ab1128-f331-44d1-a8f9-6063c84582a8
    resourceVersion: "50130"
    uid: a23bbdf1-89a1-4c86-8df3-a435b2304a9c
  spec:
    sourcePod: network-check-source-989f8b8dc-4kfh8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:40:05Z"
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.55717ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:08:05Z"
    - latency: 2.42155ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:07:05Z"
    - latency: 2.299121ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:06:05Z"
    - latency: 2.381444ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:05:05Z"
    - latency: 2.194883ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:04:05Z"
    - latency: 2.511735ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:03:05Z"
    - latency: 2.296586ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:02:05Z"
    - latency: 2.349147ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:01:05Z"
    - latency: 2.354545ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:00:05Z"
    - latency: 2.129348ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:59:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-109-to-network-check-target-ip-10-0-132-109
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-109.ec2.internal
      uid: 44ab1128-f331-44d1-a8f9-6063c84582a8
    resourceVersion: "50128"
    uid: cb2cdb50-ad74-43d8-bbb8-a12790adf753
  spec:
    sourcePod: network-check-source-989f8b8dc-4kfh8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:40:05Z"
      message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.255468ms
      message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:08:05Z"
    - latency: 1.326052ms
      message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:07:05Z"
    - latency: 915.489µs
      message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:06:05Z"
    - latency: 867.065µs
      message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:05:05Z"
    - latency: 1.330021ms
      message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:04:05Z"
    - latency: 1.106826ms
      message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:03:05Z"
    - latency: 1.065421ms
      message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:02:05Z"
    - latency: 1.032762ms
      message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:01:05Z"
    - latency: 951.41µs
      message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:00:05Z"
    - latency: 990.517µs
      message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:59:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-109-to-network-check-target-ip-10-0-136-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-109.ec2.internal
      uid: 44ab1128-f331-44d1-a8f9-6063c84582a8
    resourceVersion: "50129"
    uid: c58a2136-1e30-4ee6-a36e-41ccea89664b
  spec:
    sourcePod: network-check-source-989f8b8dc-4kfh8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:40:05Z"
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.586454ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:08:05Z"
    - latency: 3.264247ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:07:05Z"
    - latency: 2.510497ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:06:05Z"
    - latency: 2.302319ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:05:05Z"
    - latency: 2.474335ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:04:05Z"
    - latency: 2.013503ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:03:05Z"
    - latency: 2.451143ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:02:05Z"
    - latency: 2.53243ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:01:05Z"
    - latency: 2.585874ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:00:05Z"
    - latency: 2.284298ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:59:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-109-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-109.ec2.internal
      uid: 44ab1128-f331-44d1-a8f9-6063c84582a8
    resourceVersion: "50773"
    uid: 30a9c266-1151-4701-8209-968b0c453bfe
  spec:
    sourcePod: network-check-source-989f8b8dc-4kfh8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:39:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.246µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:09:05Z"
    - latency: 2.162112ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:09:05Z"
    - latency: 810.846µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:08:05Z"
    - latency: 1.753275ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:08:05Z"
    - latency: 1.427837ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:07:05Z"
    - latency: 1.577792ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:07:05Z"
    - latency: 1.132854ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:06:05Z"
    - latency: 1.577895ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:06:05Z"
    - latency: 870.862µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:05:05Z"
    - latency: 1.999029ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:05:05Z"
kind: List
metadata:
  resourceVersion: ""