apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:51:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-145-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-145.ec2.internal
      uid: 2b0acd06-aa7f-4462-84a9-52cf481e315f
    resourceVersion: "60479"
    uid: 3038d02f-2d53-4f1b-9ed8-01779c80fe7b
  spec:
    sourcePod: network-check-source-869dcfcdcd-cjwq7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:58:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 828.127µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:33:00Z"
    - latency: 897.63µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:32:00Z"
    - latency: 1.115534ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:31:00Z"
    - latency: 1.013902ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:30:00Z"
    - latency: 921.096µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:29:00Z"
    - latency: 2.415499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:28:00Z"
    - latency: 1.171153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:27:00Z"
    - latency: 1.048726ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:26:00Z"
    - latency: 1.051357ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:25:00Z"
    - latency: 885.051µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:24:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:51:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-145-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-145.ec2.internal
      uid: 2b0acd06-aa7f-4462-84a9-52cf481e315f
    resourceVersion: "60481"
    uid: ddd83535-0276-4f0c-b1c9-800a70d82dd8
  spec:
    sourcePod: network-check-source-869dcfcdcd-cjwq7
    targetEndpoint: a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:57:00Z"
      message: 'load-balancer-api-external: tcp connection to a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.709032ms
      message: 'load-balancer-api-external: tcp connection to a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:33:00Z"
    - latency: 6.888324ms
      message: 'load-balancer-api-external: resolved host name a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:33:00Z"
    - latency: 3.752846ms
      message: 'load-balancer-api-external: tcp connection to a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:32:00Z"
    - latency: 6.747825ms
      message: 'load-balancer-api-external: resolved host name a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:32:00Z"
    - latency: 3.992054ms
      message: 'load-balancer-api-external: tcp connection to a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:31:00Z"
    - latency: 6.639721ms
      message: 'load-balancer-api-external: resolved host name a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:31:00Z"
    - latency: 4.994741ms
      message: 'load-balancer-api-external: tcp connection to a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:30:00Z"
    - latency: 6.584913ms
      message: 'load-balancer-api-external: resolved host name a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:30:00Z"
    - latency: 4.331798ms
      message: 'load-balancer-api-external: tcp connection to a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:29:00Z"
    - latency: 7.127615ms
      message: 'load-balancer-api-external: resolved host name a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:29:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:51:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-145-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-145.ec2.internal
      uid: 2b0acd06-aa7f-4462-84a9-52cf481e315f
    resourceVersion: "60480"
    uid: 7a05f97a-44aa-4aeb-9fd3-42ef63f9cc34
  spec:
    sourcePod: network-check-source-869dcfcdcd-cjwq7
    targetEndpoint: a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:57:00Z"
      message: 'load-balancer-api-internal: tcp connection to a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.341832ms
      message: 'load-balancer-api-internal: tcp connection to a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:33:00Z"
    - latency: 6.984435ms
      message: 'load-balancer-api-internal: resolved host name a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:33:00Z"
    - latency: 3.635907ms
      message: 'load-balancer-api-internal: tcp connection to a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:32:00Z"
    - latency: 6.81847ms
      message: 'load-balancer-api-internal: resolved host name a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:32:00Z"
    - latency: 4.245359ms
      message: 'load-balancer-api-internal: tcp connection to a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:31:00Z"
    - latency: 6.593246ms
      message: 'load-balancer-api-internal: resolved host name a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:31:00Z"
    - latency: 3.35931ms
      message: 'load-balancer-api-internal: tcp connection to a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:30:00Z"
    - latency: 6.688539ms
      message: 'load-balancer-api-internal: resolved host name a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:30:00Z"
    - latency: 4.398525ms
      message: 'load-balancer-api-internal: tcp connection to a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:29:00Z"
    - latency: 7.203515ms
      message: 'load-balancer-api-internal: resolved host name a7de21b2c1a5941879d6eb5201d110ee-55bc1ccbe1a038b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:29:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:51:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-145-to-network-check-target-ip-10-0-129-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-145.ec2.internal
      uid: 2b0acd06-aa7f-4462-84a9-52cf481e315f
    resourceVersion: "60475"
    uid: 782699ba-3933-4757-97dc-755d4027c036
  spec:
    sourcePod: network-check-source-869dcfcdcd-cjwq7
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:58:00Z"
      message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.607µs
      message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:33:00Z"
    - latency: 792.771µs
      message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:32:00Z"
    - latency: 1.42653ms
      message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:31:00Z"
    - latency: 735.831µs
      message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:30:00Z"
    - latency: 833.09µs
      message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:29:00Z"
    - latency: 1.030736ms
      message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:28:00Z"
    - latency: 1.365389ms
      message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:27:00Z"
    - latency: 987.063µs
      message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:26:00Z"
    - latency: 825.338µs
      message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:25:00Z"
    - latency: 1.64233ms
      message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:24:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:51:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-145-to-network-check-target-ip-10-0-135-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-145.ec2.internal
      uid: 2b0acd06-aa7f-4462-84a9-52cf481e315f
    resourceVersion: "60477"
    uid: bf5502d7-99a4-4be2-8632-1b5308ba8a83
  spec:
    sourcePod: network-check-source-869dcfcdcd-cjwq7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:58:00Z"
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.283085ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:33:00Z"
    - latency: 1.819248ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:32:00Z"
    - latency: 1.79491ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:31:00Z"
    - latency: 1.804841ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:30:00Z"
    - latency: 2.556226ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:29:00Z"
    - latency: 2.035056ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:28:00Z"
    - latency: 2.627794ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:27:00Z"
    - latency: 1.453056ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:26:00Z"
    - latency: 1.692056ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:25:00Z"
    - latency: 1.958925ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:24:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:51:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-145-to-network-check-target-ip-10-0-139-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-145.ec2.internal
      uid: 2b0acd06-aa7f-4462-84a9-52cf481e315f
    resourceVersion: "60476"
    uid: da27c3cf-5d19-4dce-bfe1-bb2c57425d55
  spec:
    sourcePod: network-check-source-869dcfcdcd-cjwq7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:58:00Z"
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.960981ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:33:00Z"
    - latency: 1.965531ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:32:00Z"
    - latency: 2.226299ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:31:00Z"
    - latency: 2.23138ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:30:00Z"
    - latency: 2.480571ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:29:00Z"
    - latency: 2.366356ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:28:00Z"
    - latency: 2.510663ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:27:00Z"
    - latency: 2.180062ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:26:00Z"
    - latency: 2.170706ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:25:00Z"
    - latency: 2.361715ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:24:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T15:51:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-145-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-145.ec2.internal
      uid: 2b0acd06-aa7f-4462-84a9-52cf481e315f
    resourceVersion: "60478"
    uid: ba97cd03-5509-4e3c-9042-ccc1f41c80b8
  spec:
    sourcePod: network-check-source-869dcfcdcd-cjwq7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T15:57:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 765.161µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:33:00Z"
    - latency: 1.676437ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:33:00Z"
    - latency: 858.831µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:32:00Z"
    - latency: 1.699124ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:32:00Z"
    - latency: 951.855µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:31:00Z"
    - latency: 1.699356ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:31:00Z"
    - latency: 848.021µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:30:00Z"
    - latency: 1.647966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:30:00Z"
    - latency: 1.068812ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T16:29:00Z"
    - latency: 1.851109ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T16:29:00Z"
kind: List
metadata:
  resourceVersion: ""