apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-90-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-90.ec2.internal
      uid: 7cd6b791-7482-4220-9328-aa9260ccb676
    resourceVersion: "63347"
    uid: 875d4dd7-6e0e-4886-abd1-65af5b31a915
  spec:
    sourcePod: network-check-source-7d88cb55d8-ngmfv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:02:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.551µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:37:56Z"
    - latency: 1.661125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:36:56Z"
    - latency: 1.10001ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:35:56Z"
    - latency: 1.299144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:34:56Z"
    - latency: 1.156475ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:33:56Z"
    - latency: 1.050242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:32:56Z"
    - latency: 925.922µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:31:56Z"
    - latency: 933.568µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:30:56Z"
    - latency: 1.09499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:29:56Z"
    - latency: 876.915µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:28:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-90-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-90.ec2.internal
      uid: 7cd6b791-7482-4220-9328-aa9260ccb676
    resourceVersion: "63349"
    uid: a5650a2d-afed-4298-9166-cfe14886d906
  spec:
    sourcePod: network-check-source-7d88cb55d8-ngmfv
    targetEndpoint: a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:01:56Z"
      message: 'load-balancer-api-external: tcp connection to a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.808245ms
      message: 'load-balancer-api-external: tcp connection to a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:37:56Z"
    - latency: 9.007417ms
      message: 'load-balancer-api-external: resolved host name a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:37:56Z"
    - latency: 4.020272ms
      message: 'load-balancer-api-external: tcp connection to a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:36:56Z"
    - latency: 8.939024ms
      message: 'load-balancer-api-external: resolved host name a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:36:56Z"
    - latency: 5.317857ms
      message: 'load-balancer-api-external: tcp connection to a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:35:56Z"
    - latency: 10.511572ms
      message: 'load-balancer-api-external: resolved host name a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:35:56Z"
    - latency: 4.065387ms
      message: 'load-balancer-api-external: tcp connection to a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:34:56Z"
    - latency: 9.131646ms
      message: 'load-balancer-api-external: resolved host name a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:34:56Z"
    - latency: 5.761782ms
      message: 'load-balancer-api-external: tcp connection to a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:33:56Z"
    - latency: 8.957467ms
      message: 'load-balancer-api-external: resolved host name a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:33:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-90-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-90.ec2.internal
      uid: 7cd6b791-7482-4220-9328-aa9260ccb676
    resourceVersion: "63350"
    uid: 417aa3c4-ce4a-4c2d-9a6a-edc732185cfe
  spec:
    sourcePod: network-check-source-7d88cb55d8-ngmfv
    targetEndpoint: a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:01:56Z"
      message: 'load-balancer-api-internal: tcp connection to a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.593026ms
      message: 'load-balancer-api-internal: tcp connection to a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:37:56Z"
    - latency: 8.943637ms
      message: 'load-balancer-api-internal: resolved host name a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:37:56Z"
    - latency: 5.015429ms
      message: 'load-balancer-api-internal: tcp connection to a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:36:56Z"
    - latency: 8.914913ms
      message: 'load-balancer-api-internal: resolved host name a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:36:56Z"
    - latency: 5.298818ms
      message: 'load-balancer-api-internal: tcp connection to a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:35:56Z"
    - latency: 10.414539ms
      message: 'load-balancer-api-internal: resolved host name a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:35:56Z"
    - latency: 4.064935ms
      message: 'load-balancer-api-internal: tcp connection to a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:34:56Z"
    - latency: 9.088037ms
      message: 'load-balancer-api-internal: resolved host name a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:34:56Z"
    - latency: 3.974272ms
      message: 'load-balancer-api-internal: tcp connection to a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:33:56Z"
    - latency: 9.022348ms
      message: 'load-balancer-api-internal: resolved host name a3b5607f1119547edb6d15049de81d62-df70c0d27ac1a4ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:33:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-90-to-network-check-target-ip-10-0-134-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-90.ec2.internal
      uid: 7cd6b791-7482-4220-9328-aa9260ccb676
    resourceVersion: "63344"
    uid: 99dd43ca-6e6c-42d7-b33e-8dcea83fb028
  spec:
    sourcePod: network-check-source-7d88cb55d8-ngmfv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:02:56Z"
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.366823ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:37:56Z"
    - latency: 2.471195ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:36:56Z"
    - latency: 2.841027ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:35:56Z"
    - latency: 2.525534ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:34:56Z"
    - latency: 2.203727ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:33:56Z"
    - latency: 2.463275ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:32:56Z"
    - latency: 2.417777ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:31:56Z"
    - latency: 2.410571ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:30:56Z"
    - latency: 2.380461ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:29:56Z"
    - latency: 2.05315ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:28:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-90-to-network-check-target-ip-10-0-134-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-90.ec2.internal
      uid: 7cd6b791-7482-4220-9328-aa9260ccb676
    resourceVersion: "63342"
    uid: b41a0f00-6ca8-4d3a-8886-432daf9b13c7
  spec:
    sourcePod: network-check-source-7d88cb55d8-ngmfv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:02:56Z"
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.465029ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:37:56Z"
    - latency: 900.409µs
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:36:56Z"
    - latency: 1.114ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:35:56Z"
    - latency: 971.098µs
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:34:56Z"
    - latency: 900.418µs
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:33:56Z"
    - latency: 1.577678ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:32:56Z"
    - latency: 1.350102ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:31:56Z"
    - latency: 1.013405ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:30:56Z"
    - latency: 1.353663ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:29:56Z"
    - latency: 814.915µs
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:28:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-90-to-network-check-target-ip-10-0-141-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-90.ec2.internal
      uid: 7cd6b791-7482-4220-9328-aa9260ccb676
    resourceVersion: "63343"
    uid: 3e796eee-6303-4f01-a72b-cff2c752a2e9
  spec:
    sourcePod: network-check-source-7d88cb55d8-ngmfv
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:02:56Z"
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.95673ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:37:56Z"
    - latency: 1.887311ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:36:56Z"
    - latency: 2.496799ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:35:56Z"
    - latency: 2.293939ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:34:56Z"
    - latency: 2.182843ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:33:56Z"
    - latency: 2.298729ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:32:56Z"
    - latency: 2.406226ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:31:56Z"
    - latency: 2.334968ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:30:56Z"
    - latency: 2.148474ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:29:56Z"
    - latency: 2.088106ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:28:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-90-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-90.ec2.internal
      uid: 7cd6b791-7482-4220-9328-aa9260ccb676
    resourceVersion: "63345"
    uid: 5272ffab-8cb9-448c-b626-de471b2c66c6
  spec:
    sourcePod: network-check-source-7d88cb55d8-ngmfv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:01:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.072375ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:37:56Z"
    - latency: 1.795178ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:37:56Z"
    - latency: 959.374µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:36:56Z"
    - latency: 2.256986ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:36:56Z"
    - latency: 1.421566ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:35:56Z"
    - latency: 1.810422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:35:56Z"
    - latency: 1.164083ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:34:56Z"
    - latency: 2.092436ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:34:56Z"
    - latency: 975.742µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:33:56Z"
    - latency: 2.077012ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:33:56Z"
kind: List
metadata:
  resourceVersion: ""