apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 86c1a36d-c9ff-4837-baf3-fdd5e96fd738
    resourceVersion: "54050"
    uid: e211be5b-62c1-47ef-b989-98faf70cb579
  spec:
    sourcePod: network-check-source-989f8b8dc-pdlhr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:20:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 874.221µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:52Z"
    - latency: 937.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:52Z"
    - latency: 1.036602ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:52Z"
    - latency: 1.207521ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:52Z"
    - latency: 1.154753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:44:52Z"
    - latency: 936.485µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:43:52Z"
    - latency: 1.05341ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:42:52Z"
    - latency: 1.244515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:41:52Z"
    - latency: 897.761µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:40:52Z"
    - latency: 967.726µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:39:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 86c1a36d-c9ff-4837-baf3-fdd5e96fd738
    resourceVersion: "55039"
    uid: 86d5263a-ca2d-4310-a8ad-2dc075949c85
  spec:
    sourcePod: network-check-source-989f8b8dc-pdlhr
    targetEndpoint: aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:19:52Z"
      message: 'load-balancer-api-external: tcp connection to aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.587064ms
      message: 'load-balancer-api-external: tcp connection to aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:49:52Z"
    - latency: 7.319453ms
      message: 'load-balancer-api-external: resolved host name aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:49:52Z"
    - latency: 5.162961ms
      message: 'load-balancer-api-external: tcp connection to aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:52Z"
    - latency: 8.022772ms
      message: 'load-balancer-api-external: resolved host name aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:48:52Z"
    - latency: 3.564467ms
      message: 'load-balancer-api-external: tcp connection to aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:52Z"
    - latency: 6.999519ms
      message: 'load-balancer-api-external: resolved host name aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:47:52Z"
    - latency: 5.704689ms
      message: 'load-balancer-api-external: tcp connection to aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:52Z"
    - latency: 6.523775ms
      message: 'load-balancer-api-external: resolved host name aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:46:52Z"
    - latency: 5.675298ms
      message: 'load-balancer-api-external: tcp connection to aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:52Z"
    - latency: 7.328838ms
      message: 'load-balancer-api-external: resolved host name aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:45:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 86c1a36d-c9ff-4837-baf3-fdd5e96fd738
    resourceVersion: "55038"
    uid: f34929f2-2102-43bb-9091-d44f40816416
  spec:
    sourcePod: network-check-source-989f8b8dc-pdlhr
    targetEndpoint: aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:19:52Z"
      message: 'load-balancer-api-internal: tcp connection to aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.368352ms
      message: 'load-balancer-api-internal: tcp connection to aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:49:52Z"
    - latency: 7.18074ms
      message: 'load-balancer-api-internal: resolved host name aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:49:52Z"
    - latency: 5.691638ms
      message: 'load-balancer-api-internal: tcp connection to aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:52Z"
    - latency: 7.930632ms
      message: 'load-balancer-api-internal: resolved host name aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:48:52Z"
    - latency: 3.541074ms
      message: 'load-balancer-api-internal: tcp connection to aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:52Z"
    - latency: 6.886639ms
      message: 'load-balancer-api-internal: resolved host name aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:47:52Z"
    - latency: 5.205222ms
      message: 'load-balancer-api-internal: tcp connection to aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:52Z"
    - latency: 6.484033ms
      message: 'load-balancer-api-internal: resolved host name aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:46:52Z"
    - latency: 5.383073ms
      message: 'load-balancer-api-internal: tcp connection to aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:52Z"
    - latency: 7.10635ms
      message: 'load-balancer-api-internal: resolved host name aedb6dbb772d04eaf8f33db33e344aa8-c7d9b4c9aa76f090.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:45:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-network-check-target-ip-10-0-133-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 86c1a36d-c9ff-4837-baf3-fdd5e96fd738
    resourceVersion: "54048"
    uid: 4361a1dc-c365-4a8f-9900-67f1537dfb07
  spec:
    sourcePod: network-check-source-989f8b8dc-pdlhr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:20:52Z"
      message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.882336ms
      message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:52Z"
    - latency: 2.257425ms
      message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:52Z"
    - latency: 2.004343ms
      message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:52Z"
    - latency: 1.977198ms
      message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:52Z"
    - latency: 2.217824ms
      message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:44:52Z"
    - latency: 2.192324ms
      message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:43:52Z"
    - latency: 1.721836ms
      message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:42:52Z"
    - latency: 2.303616ms
      message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:41:52Z"
    - latency: 2.080004ms
      message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:40:52Z"
    - latency: 2.224671ms
      message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:39:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-network-check-target-ip-10-0-135-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 86c1a36d-c9ff-4837-baf3-fdd5e96fd738
    resourceVersion: "54047"
    uid: de92a74f-3ca3-4cd2-b2e3-7ac021ef4803
  spec:
    sourcePod: network-check-source-989f8b8dc-pdlhr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:20:52Z"
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 997.414µs
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:52Z"
    - latency: 1.261184ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:52Z"
    - latency: 1.032246ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:52Z"
    - latency: 867.693µs
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:52Z"
    - latency: 1.154997ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:44:52Z"
    - latency: 966.484µs
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:43:52Z"
    - latency: 933.5µs
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:42:52Z"
    - latency: 933.441µs
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:41:52Z"
    - latency: 962.528µs
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:40:52Z"
    - latency: 1.109606ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:39:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-network-check-target-ip-10-0-137-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 86c1a36d-c9ff-4837-baf3-fdd5e96fd738
    resourceVersion: "54049"
    uid: dfbc0aef-f481-4fad-9b27-30ba80d72f9f
  spec:
    sourcePod: network-check-source-989f8b8dc-pdlhr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:20:52Z"
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.528802ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:52Z"
    - latency: 2.154604ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:52Z"
    - latency: 2.393701ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:52Z"
    - latency: 2.275464ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:52Z"
    - latency: 2.042527ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:44:52Z"
    - latency: 2.124499ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:43:52Z"
    - latency: 2.407561ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:42:52Z"
    - latency: 1.967009ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:41:52Z"
    - latency: 2.256386ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:40:52Z"
    - latency: 2.359561ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:39:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 86c1a36d-c9ff-4837-baf3-fdd5e96fd738
    resourceVersion: "55037"
    uid: fba66852-e9ab-4443-ac59-23353032d6cc
  spec:
    sourcePod: network-check-source-989f8b8dc-pdlhr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:19:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 898.399µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:49:52Z"
    - latency: 1.799812ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:49:52Z"
    - latency: 934.622µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:52Z"
    - latency: 2.384835ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:48:52Z"
    - latency: 1.222001ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:52Z"
    - latency: 1.79276ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:47:52Z"
    - latency: 920.607µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:52Z"
    - latency: 1.986441ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:46:52Z"
    - latency: 932.003µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:52Z"
    - latency: 1.867404ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:45:52Z"
kind: List
metadata:
  resourceVersion: ""