apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:55:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-37-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-37.ec2.internal
      uid: 4122ef5d-b12c-4b72-8e51-cea44731c190
    resourceVersion: "54906"
    uid: 9b2bc674-e377-42e6-a753-7971a9791b0c
  spec:
    sourcePod: network-check-source-989f8b8dc-6p5nh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:02:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.220055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:30:27Z"
    - latency: 1.125836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:29:27Z"
    - latency: 1.101434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:28:27Z"
    - latency: 1.057842ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:27:27Z"
    - latency: 897.944µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:26:27Z"
    - latency: 1.02018ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:25:27Z"
    - latency: 1.146952ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:24:27Z"
    - latency: 1.288053ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:23:27Z"
    - latency: 1.18516ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:22:27Z"
    - latency: 986.614µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:21:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:55:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-37-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-37.ec2.internal
      uid: 4122ef5d-b12c-4b72-8e51-cea44731c190
    resourceVersion: "55910"
    uid: b74d9ee5-8557-49fe-b3fa-584e2e3229ce
  spec:
    sourcePod: network-check-source-989f8b8dc-6p5nh
    targetEndpoint: a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:01:27Z"
      message: 'load-balancer-api-external: tcp connection to a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.254829ms
      message: 'load-balancer-api-external: tcp connection to a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:31:27Z"
    - latency: 7.179853ms
      message: 'load-balancer-api-external: resolved host name a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:31:27Z"
    - latency: 6.574366ms
      message: 'load-balancer-api-external: tcp connection to a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:30:27Z"
    - latency: 6.448078ms
      message: 'load-balancer-api-external: resolved host name a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:30:27Z"
    - latency: 4.897032ms
      message: 'load-balancer-api-external: tcp connection to a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:29:27Z"
    - latency: 6.109673ms
      message: 'load-balancer-api-external: resolved host name a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:29:27Z"
    - latency: 3.98164ms
      message: 'load-balancer-api-external: tcp connection to a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:28:27Z"
    - latency: 8.532801ms
      message: 'load-balancer-api-external: resolved host name a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:28:27Z"
    - latency: 5.980422ms
      message: 'load-balancer-api-external: tcp connection to a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:27:27Z"
    - latency: 6.41652ms
      message: 'load-balancer-api-external: resolved host name a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:27:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:55:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-37-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-37.ec2.internal
      uid: 4122ef5d-b12c-4b72-8e51-cea44731c190
    resourceVersion: "55911"
    uid: a298cbca-22db-4a16-82d8-39765f03c5dd
  spec:
    sourcePod: network-check-source-989f8b8dc-6p5nh
    targetEndpoint: a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:01:27Z"
      message: 'load-balancer-api-internal: tcp connection to a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.245093ms
      message: 'load-balancer-api-internal: tcp connection to a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:31:27Z"
    - latency: 7.333103ms
      message: 'load-balancer-api-internal: resolved host name a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:31:27Z"
    - latency: 4.816304ms
      message: 'load-balancer-api-internal: tcp connection to a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:30:27Z"
    - latency: 6.393373ms
      message: 'load-balancer-api-internal: resolved host name a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:30:27Z"
    - latency: 4.43306ms
      message: 'load-balancer-api-internal: tcp connection to a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:29:27Z"
    - latency: 6.131231ms
      message: 'load-balancer-api-internal: resolved host name a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:29:27Z"
    - latency: 4.037483ms
      message: 'load-balancer-api-internal: tcp connection to a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:28:27Z"
    - latency: 8.449053ms
      message: 'load-balancer-api-internal: resolved host name a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:28:27Z"
    - latency: 5.997067ms
      message: 'load-balancer-api-internal: tcp connection to a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:27:27Z"
    - latency: 6.452632ms
      message: 'load-balancer-api-internal: resolved host name a74ddfa4809b7446aaca7827d3d627f5-37b759b2c7977f52.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:27:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:55:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-37-to-network-check-target-ip-10-0-129-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-37.ec2.internal
      uid: 4122ef5d-b12c-4b72-8e51-cea44731c190
    resourceVersion: "54904"
    uid: 9441feea-a69f-458f-8d9e-59838e2919a5
  spec:
    sourcePod: network-check-source-989f8b8dc-6p5nh
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:02:27Z"
      message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.193475ms
      message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:30:27Z"
    - latency: 2.288122ms
      message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:29:27Z"
    - latency: 1.928471ms
      message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:28:27Z"
    - latency: 2.226698ms
      message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:27:27Z"
    - latency: 2.368195ms
      message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:26:27Z"
    - latency: 2.079711ms
      message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:25:27Z"
    - latency: 2.781846ms
      message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:24:27Z"
    - latency: 1.928619ms
      message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:23:27Z"
    - latency: 2.03012ms
      message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:22:27Z"
    - latency: 1.813655ms
      message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:21:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:55:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-37-to-network-check-target-ip-10-0-130-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-37.ec2.internal
      uid: 4122ef5d-b12c-4b72-8e51-cea44731c190
    resourceVersion: "54903"
    uid: 8d63b52b-a37f-444d-9e86-a10c7f2e6007
  spec:
    sourcePod: network-check-source-989f8b8dc-6p5nh
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:02:27Z"
      message: 'network-check-target-ip-10-0-130-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.174µs
      message: 'network-check-target-ip-10-0-130-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:30:27Z"
    - latency: 911.767µs
      message: 'network-check-target-ip-10-0-130-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:29:27Z"
    - latency: 838.115µs
      message: 'network-check-target-ip-10-0-130-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:28:27Z"
    - latency: 1.209655ms
      message: 'network-check-target-ip-10-0-130-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:27:27Z"
    - latency: 1.621778ms
      message: 'network-check-target-ip-10-0-130-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:26:27Z"
    - latency: 782.773µs
      message: 'network-check-target-ip-10-0-130-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:25:27Z"
    - latency: 1.868127ms
      message: 'network-check-target-ip-10-0-130-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:24:27Z"
    - latency: 1.461483ms
      message: 'network-check-target-ip-10-0-130-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:23:27Z"
    - latency: 928.938µs
      message: 'network-check-target-ip-10-0-130-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:22:27Z"
    - latency: 976.587µs
      message: 'network-check-target-ip-10-0-130-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:21:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:55:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-37-to-network-check-target-ip-10-0-134-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-37.ec2.internal
      uid: 4122ef5d-b12c-4b72-8e51-cea44731c190
    resourceVersion: "54905"
    uid: 0b1a5b1d-fa70-47f6-97db-c6f8fbe50b5b
  spec:
    sourcePod: network-check-source-989f8b8dc-6p5nh
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:02:27Z"
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.989671ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:30:27Z"
    - latency: 2.031367ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:29:27Z"
    - latency: 2.130665ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:28:27Z"
    - latency: 1.862185ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:27:27Z"
    - latency: 1.999825ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:26:27Z"
    - latency: 1.963299ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:25:27Z"
    - latency: 4.543353ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:24:27Z"
    - latency: 1.658803ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:23:27Z"
    - latency: 1.756995ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:22:27Z"
    - latency: 1.844466ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:21:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T17:55:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-37-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-37.ec2.internal
      uid: 4122ef5d-b12c-4b72-8e51-cea44731c190
    resourceVersion: "55908"
    uid: 99d44641-a0ed-4a36-a2ba-acf29244b8c8
  spec:
    sourcePod: network-check-source-989f8b8dc-6p5nh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:01:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 942.021µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:31:27Z"
    - latency: 2.0522ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:31:27Z"
    - latency: 1.073555ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:30:27Z"
    - latency: 1.681161ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:30:27Z"
    - latency: 1.040627ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:29:27Z"
    - latency: 1.564878ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:29:27Z"
    - latency: 868.293µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:28:27Z"
    - latency: 1.770603ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:28:27Z"
    - latency: 960.411µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:27:27Z"
    - latency: 1.893285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:27:27Z"
kind: List
metadata:
  resourceVersion: ""