apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-210-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-210.ec2.internal
      uid: 2d4d2ed9-4ec4-441d-be75-c009f25c2404
    resourceVersion: "64205"
    uid: d771e01a-ad77-40eb-99f4-52fa4f0df681
  spec:
    sourcePod: network-check-source-7d88cb55d8-zx4vv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:52:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.005386ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:27:23Z"
    - latency: 1.124969ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:26:23Z"
    - latency: 1.086431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:25:23Z"
    - latency: 1.036299ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:24:23Z"
    - latency: 1.241417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:23:23Z"
    - latency: 1.243101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:22:23Z"
    - latency: 980.794µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:21:23Z"
    - latency: 870.912µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:20:23Z"
    - latency: 1.110584ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:19:23Z"
    - latency: 935.824µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:18:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-210-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-210.ec2.internal
      uid: 2d4d2ed9-4ec4-441d-be75-c009f25c2404
    resourceVersion: "64210"
    uid: 9b9a582a-699d-4fcc-b8b3-7df7e461594d
  spec:
    sourcePod: network-check-source-7d88cb55d8-zx4vv
    targetEndpoint: a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:51:23Z"
      message: 'load-balancer-api-external: tcp connection to a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.040865ms
      message: 'load-balancer-api-external: tcp connection to a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:27:23Z"
    - latency: 8.552354ms
      message: 'load-balancer-api-external: resolved host name a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:27:23Z"
    - latency: 5.295714ms
      message: 'load-balancer-api-external: tcp connection to a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:26:23Z"
    - latency: 8.379329ms
      message: 'load-balancer-api-external: resolved host name a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:26:23Z"
    - latency: 6.36647ms
      message: 'load-balancer-api-external: tcp connection to a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:25:23Z"
    - latency: 9.24096ms
      message: 'load-balancer-api-external: resolved host name a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:25:23Z"
    - latency: 3.312702ms
      message: 'load-balancer-api-external: tcp connection to a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:24:23Z"
    - latency: 7.177666ms
      message: 'load-balancer-api-external: resolved host name a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:24:23Z"
    - latency: 4.940523ms
      message: 'load-balancer-api-external: tcp connection to a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:23:23Z"
    - latency: 8.307882ms
      message: 'load-balancer-api-external: resolved host name a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:23:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-210-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-210.ec2.internal
      uid: 2d4d2ed9-4ec4-441d-be75-c009f25c2404
    resourceVersion: "64207"
    uid: d67f74ed-1bf3-4548-bcd9-2b3e799c3eea
  spec:
    sourcePod: network-check-source-7d88cb55d8-zx4vv
    targetEndpoint: a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:51:23Z"
      message: 'load-balancer-api-internal: tcp connection to a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.083099ms
      message: 'load-balancer-api-internal: tcp connection to a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:27:23Z"
    - latency: 8.503884ms
      message: 'load-balancer-api-internal: resolved host name a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:27:23Z"
    - latency: 5.275122ms
      message: 'load-balancer-api-internal: tcp connection to a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:26:23Z"
    - latency: 8.354832ms
      message: 'load-balancer-api-internal: resolved host name a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:26:23Z"
    - latency: 6.772014ms
      message: 'load-balancer-api-internal: tcp connection to a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:25:23Z"
    - latency: 9.190552ms
      message: 'load-balancer-api-internal: resolved host name a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:25:23Z"
    - latency: 3.51719ms
      message: 'load-balancer-api-internal: tcp connection to a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:24:23Z"
    - latency: 7.124662ms
      message: 'load-balancer-api-internal: resolved host name a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:24:23Z"
    - latency: 3.67804ms
      message: 'load-balancer-api-internal: tcp connection to a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:23:23Z"
    - latency: 8.276324ms
      message: 'load-balancer-api-internal: resolved host name a366c8fb29cb445fdb935c349d4b46ee-fab7f049654425a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:23:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-210-to-network-check-target-ip-10-0-131-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-210.ec2.internal
      uid: 2d4d2ed9-4ec4-441d-be75-c009f25c2404
    resourceVersion: "64201"
    uid: 55d41992-25f4-46c1-97d2-960067aa546b
  spec:
    sourcePod: network-check-source-7d88cb55d8-zx4vv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:52:23Z"
      message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.420979ms
      message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:27:23Z"
    - latency: 1.0849ms
      message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:26:23Z"
    - latency: 865.401µs
      message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:25:23Z"
    - latency: 941.662µs
      message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:24:23Z"
    - latency: 886.022µs
      message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:23:23Z"
    - latency: 1.012008ms
      message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:22:23Z"
    - latency: 859.768µs
      message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:21:23Z"
    - latency: 1.02931ms
      message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:20:23Z"
    - latency: 834.415µs
      message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:19:23Z"
    - latency: 1.050987ms
      message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:18:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-210-to-network-check-target-ip-10-0-133-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-210.ec2.internal
      uid: 2d4d2ed9-4ec4-441d-be75-c009f25c2404
    resourceVersion: "64203"
    uid: ed43f3cb-fe44-499c-ae04-f7b87c1d1909
  spec:
    sourcePod: network-check-source-7d88cb55d8-zx4vv
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:52:23Z"
      message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.657481ms
      message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:27:23Z"
    - latency: 2.449074ms
      message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:26:23Z"
    - latency: 2.344782ms
      message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:25:23Z"
    - latency: 2.543192ms
      message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:24:23Z"
    - latency: 2.318916ms
      message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:23:23Z"
    - latency: 2.203681ms
      message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:22:23Z"
    - latency: 2.268576ms
      message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:21:23Z"
    - latency: 2.370857ms
      message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:20:23Z"
    - latency: 2.571681ms
      message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:19:23Z"
    - latency: 2.760947ms
      message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:18:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-210-to-network-check-target-ip-10-0-143-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-210.ec2.internal
      uid: 2d4d2ed9-4ec4-441d-be75-c009f25c2404
    resourceVersion: "64202"
    uid: 2f5b6679-84b8-4160-91d8-85f6cd2805dd
  spec:
    sourcePod: network-check-source-7d88cb55d8-zx4vv
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:52:23Z"
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.537243ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:27:23Z"
    - latency: 2.471933ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:26:23Z"
    - latency: 1.823392ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:25:23Z"
    - latency: 2.287907ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:24:23Z"
    - latency: 2.665163ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:23:23Z"
    - latency: 2.445783ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:22:23Z"
    - latency: 2.759088ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:21:23Z"
    - latency: 2.373293ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:20:23Z"
    - latency: 2.525448ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:19:23Z"
    - latency: 2.275859ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:18:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-210-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-210.ec2.internal
      uid: 2d4d2ed9-4ec4-441d-be75-c009f25c2404
    resourceVersion: "64204"
    uid: cf77c0b1-f3b1-4f8a-9da9-5ec6b0946d4d
  spec:
    sourcePod: network-check-source-7d88cb55d8-zx4vv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:51:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.056293ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:27:23Z"
    - latency: 2.328227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:27:23Z"
    - latency: 831.132µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:26:23Z"
    - latency: 1.872923ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:26:23Z"
    - latency: 732.766µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:25:23Z"
    - latency: 2.078385ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:25:23Z"
    - latency: 895.253µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:24:23Z"
    - latency: 1.715741ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:24:23Z"
    - latency: 1.186604ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:23:23Z"
    - latency: 1.940058ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:23:23Z"
kind: List
metadata:
  resourceVersion: ""