apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T21:17:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 61a0e1ba-8103-4de8-9441-ca533a87dc2b
    resourceVersion: "161796"
    uid: e9e61a14-49e6-408a-a57c-70fd4627d85c
  spec:
    sourcePod: network-check-source-6f78d59f99-cbc4j
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T21:24:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.771µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:20:54Z"
    - latency: 1.450802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:19:54Z"
    - latency: 1.903831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:18:54Z"
    - latency: 1.00676ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:17:54Z"
    - latency: 1.110434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:16:54Z"
    - latency: 1.233599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:15:54Z"
    - latency: 1.484318ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:14:54Z"
    - latency: 1.226308ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:13:54Z"
    - latency: 1.402479ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:12:54Z"
    - latency: 1.971419ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:11:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T21:17:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 61a0e1ba-8103-4de8-9441-ca533a87dc2b
    resourceVersion: "153721"
    uid: d47cbf1f-7475-4a89-b127-84c3d40eafb6
  spec:
    sourcePod: network-check-source-6f78d59f99-cbc4j
    targetEndpoint: afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T21:23:54Z"
      message: 'load-balancer-api-external: tcp connection to afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.015197ms
      message: 'load-balancer-api-external: tcp connection to afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:17:54Z"
    - latency: 8.160449ms
      message: 'load-balancer-api-external: resolved host name afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:17:54Z"
    - latency: 18.852548ms
      message: 'load-balancer-api-external: tcp connection to afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:16:54Z"
    - latency: 11.57957ms
      message: 'load-balancer-api-external: resolved host name afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:16:54Z"
    - latency: 17.199744ms
      message: 'load-balancer-api-external: tcp connection to afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:15:54Z"
    - latency: 7.283201ms
      message: 'load-balancer-api-external: resolved host name afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:15:54Z"
    - latency: 15.185481ms
      message: 'load-balancer-api-external: tcp connection to afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:14:54Z"
    - latency: 8.510021ms
      message: 'load-balancer-api-external: resolved host name afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:14:54Z"
    - latency: 14.924594ms
      message: 'load-balancer-api-external: tcp connection to afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:13:54Z"
    - latency: 10.577994ms
      message: 'load-balancer-api-external: resolved host name afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:13:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T21:17:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 61a0e1ba-8103-4de8-9441-ca533a87dc2b
    resourceVersion: "153722"
    uid: d064af88-b51c-4d3d-aa68-522b279891e7
  spec:
    sourcePod: network-check-source-6f78d59f99-cbc4j
    targetEndpoint: afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T21:23:54Z"
      message: 'load-balancer-api-internal: tcp connection to afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.080022ms
      message: 'load-balancer-api-internal: tcp connection to afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:17:54Z"
    - latency: 8.170999ms
      message: 'load-balancer-api-internal: resolved host name afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:17:54Z"
    - latency: 18.869645ms
      message: 'load-balancer-api-internal: tcp connection to afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:16:54Z"
    - latency: 11.601307ms
      message: 'load-balancer-api-internal: resolved host name afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:16:54Z"
    - latency: 17.116435ms
      message: 'load-balancer-api-internal: tcp connection to afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:15:54Z"
    - latency: 7.356588ms
      message: 'load-balancer-api-internal: resolved host name afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:15:54Z"
    - latency: 16.466339ms
      message: 'load-balancer-api-internal: tcp connection to afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:14:54Z"
    - latency: 8.541612ms
      message: 'load-balancer-api-internal: resolved host name afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:14:54Z"
    - latency: 17.265539ms
      message: 'load-balancer-api-internal: tcp connection to afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:13:54Z"
    - latency: 10.619516ms
      message: 'load-balancer-api-internal: resolved host name afc4651372ede4a0683f6d4565062c59-acecc3ad1fb221f2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:13:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T21:17:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-network-check-target-ip-10-0-131-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 61a0e1ba-8103-4de8-9441-ca533a87dc2b
    resourceVersion: "161793"
    uid: 97d2cc50-51be-4e75-98c6-2875023f12c4
  spec:
    sourcePod: network-check-source-6f78d59f99-cbc4j
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T21:24:54Z"
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.098038ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:20:54Z"
    - latency: 1.375511ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:19:54Z"
    - latency: 1.386722ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:18:54Z"
    - latency: 1.06005ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:17:54Z"
    - latency: 1.176934ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:16:54Z"
    - latency: 1.59155ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:15:54Z"
    - latency: 1.219976ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:14:54Z"
    - latency: 1.611098ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:13:54Z"
    - latency: 1.718244ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:12:54Z"
    - latency: 2.721482ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:11:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T21:17:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-network-check-target-ip-10-0-136-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 61a0e1ba-8103-4de8-9441-ca533a87dc2b
    resourceVersion: "161794"
    uid: d982c768-78f0-4bf2-931b-2f347864e215
  spec:
    sourcePod: network-check-source-6f78d59f99-cbc4j
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T21:24:54Z"
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.074268ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:20:54Z"
    - latency: 2.432419ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:19:54Z"
    - latency: 2.387286ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:18:54Z"
    - latency: 2.288194ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:17:54Z"
    - latency: 2.282619ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:16:54Z"
    - latency: 2.234571ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:15:54Z"
    - latency: 2.497316ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:14:54Z"
    - latency: 2.268498ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:13:54Z"
    - latency: 2.332712ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:12:54Z"
    - latency: 3.152621ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:11:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T21:17:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-network-check-target-ip-10-0-136-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 61a0e1ba-8103-4de8-9441-ca533a87dc2b
    resourceVersion: "161795"
    uid: 1d2514ad-f9af-4efd-a3ea-60d694e2a9a1
  spec:
    sourcePod: network-check-source-6f78d59f99-cbc4j
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T21:24:54Z"
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.325784ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:20:54Z"
    - latency: 2.655827ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:19:54Z"
    - latency: 2.81574ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:18:54Z"
    - latency: 2.314041ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:17:54Z"
    - latency: 2.318478ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:16:54Z"
    - latency: 2.443581ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:15:54Z"
    - latency: 2.926907ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:14:54Z"
    - latency: 2.736325ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:13:54Z"
    - latency: 2.704092ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:12:54Z"
    - latency: 3.97851ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:11:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T21:17:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 61a0e1ba-8103-4de8-9441-ca533a87dc2b
    resourceVersion: "153720"
    uid: 33550204-d94e-4d1b-a12a-ec8922756e71
  spec:
    sourcePod: network-check-source-6f78d59f99-cbc4j
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T21:23:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.255822ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:17:54Z"
    - latency: 2.437423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:17:54Z"
    - latency: 1.067386ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:16:54Z"
    - latency: 2.834181ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:16:54Z"
    - latency: 1.149084ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:15:54Z"
    - latency: 2.380866ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:15:54Z"
    - latency: 1.082215ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:14:54Z"
    - latency: 2.472536ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:14:54Z"
    - latency: 1.174799ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T22:13:54Z"
    - latency: 2.273512ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T22:13:54Z"
kind: List
metadata:
  resourceVersion: ""