apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T01:32:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-17-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-17.ec2.internal
      uid: 26b935e1-d974-4979-b49d-a29ebc00f4a5
    resourceVersion: "63929"
    uid: 4488771a-5bd6-4283-870f-a7a4f8e1ef80
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q9lh5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T01:39:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 785.28µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:14:19Z"
    - latency: 1.189685ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:13:19Z"
    - latency: 853.805µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:12:19Z"
    - latency: 854.124µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:11:19Z"
    - latency: 880.977µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:10:19Z"
    - latency: 1.282151ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:09:19Z"
    - latency: 1.123941ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:08:19Z"
    - latency: 1.0557ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:07:19Z"
    - latency: 1.224719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:06:19Z"
    - latency: 1.266036ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:05:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T01:32:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-17-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-17.ec2.internal
      uid: 26b935e1-d974-4979-b49d-a29ebc00f4a5
    resourceVersion: "63930"
    uid: 677104cd-d274-4da3-8167-8bcce4ac9808
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q9lh5
    targetEndpoint: a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T01:38:19Z"
      message: 'load-balancer-api-external: tcp connection to a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.992543ms
      message: 'load-balancer-api-external: tcp connection to a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:14:19Z"
    - latency: 7.814677ms
      message: 'load-balancer-api-external: resolved host name a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:14:19Z"
    - latency: 3.676965ms
      message: 'load-balancer-api-external: tcp connection to a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:13:19Z"
    - latency: 8.551222ms
      message: 'load-balancer-api-external: resolved host name a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:13:19Z"
    - latency: 4.532302ms
      message: 'load-balancer-api-external: tcp connection to a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:12:19Z"
    - latency: 7.880265ms
      message: 'load-balancer-api-external: resolved host name a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:12:19Z"
    - latency: 3.615256ms
      message: 'load-balancer-api-external: tcp connection to a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:11:19Z"
    - latency: 6.959638ms
      message: 'load-balancer-api-external: resolved host name a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:11:19Z"
    - latency: 3.813949ms
      message: 'load-balancer-api-external: tcp connection to a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:10:19Z"
    - latency: 6.153127ms
      message: 'load-balancer-api-external: resolved host name a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:10:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T01:32:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-17-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-17.ec2.internal
      uid: 26b935e1-d974-4979-b49d-a29ebc00f4a5
    resourceVersion: "63931"
    uid: 1e4230aa-8169-45ce-a629-0bd90ce862da
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q9lh5
    targetEndpoint: a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T01:38:19Z"
      message: 'load-balancer-api-internal: tcp connection to a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.70155ms
      message: 'load-balancer-api-internal: tcp connection to a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:14:19Z"
    - latency: 7.74323ms
      message: 'load-balancer-api-internal: resolved host name a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:14:19Z"
    - latency: 3.651768ms
      message: 'load-balancer-api-internal: tcp connection to a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:13:19Z"
    - latency: 8.583331ms
      message: 'load-balancer-api-internal: resolved host name a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:13:19Z"
    - latency: 4.621429ms
      message: 'load-balancer-api-internal: tcp connection to a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:12:19Z"
    - latency: 7.816452ms
      message: 'load-balancer-api-internal: resolved host name a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:12:19Z"
    - latency: 3.586357ms
      message: 'load-balancer-api-internal: tcp connection to a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:11:19Z"
    - latency: 7.003171ms
      message: 'load-balancer-api-internal: resolved host name a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:11:19Z"
    - latency: 3.802298ms
      message: 'load-balancer-api-internal: tcp connection to a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:10:19Z"
    - latency: 6.093396ms
      message: 'load-balancer-api-internal: resolved host name a4e838dd2ea1c4265b05cc42f175974a-5eb761dfdc4714bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:10:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T01:32:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-17-to-network-check-target-ip-10-0-129-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-17.ec2.internal
      uid: 26b935e1-d974-4979-b49d-a29ebc00f4a5
    resourceVersion: "63925"
    uid: 9207bd68-8a38-4ceb-8e8c-15a64ffde8d2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q9lh5
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T01:39:19Z"
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.808µs
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:14:19Z"
    - latency: 942.945µs
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:13:19Z"
    - latency: 867.448µs
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:12:19Z"
    - latency: 907.158µs
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:11:19Z"
    - latency: 957.489µs
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:10:19Z"
    - latency: 827.144µs
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:09:19Z"
    - latency: 1.013423ms
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:08:19Z"
    - latency: 1.005079ms
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:07:19Z"
    - latency: 857.337µs
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:06:19Z"
    - latency: 1.123672ms
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:05:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T01:32:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-17-to-network-check-target-ip-10-0-131-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-17.ec2.internal
      uid: 26b935e1-d974-4979-b49d-a29ebc00f4a5
    resourceVersion: "63926"
    uid: 1fce333a-dc63-4ebb-84a2-9ee18a0935e7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q9lh5
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T01:39:19Z"
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.250373ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:14:19Z"
    - latency: 2.360716ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:13:19Z"
    - latency: 2.318434ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:12:19Z"
    - latency: 2.162144ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:11:19Z"
    - latency: 1.884439ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:10:19Z"
    - latency: 2.057427ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:09:19Z"
    - latency: 2.398232ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:08:19Z"
    - latency: 2.366825ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:07:19Z"
    - latency: 2.385975ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:06:19Z"
    - latency: 2.172413ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:05:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T01:32:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-17-to-network-check-target-ip-10-0-136-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-17.ec2.internal
      uid: 26b935e1-d974-4979-b49d-a29ebc00f4a5
    resourceVersion: "63928"
    uid: f9b4b11d-242f-4053-aa26-a7ebf0eeb5f0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q9lh5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T01:39:19Z"
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.839133ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:14:19Z"
    - latency: 2.090035ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:13:19Z"
    - latency: 1.933291ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:12:19Z"
    - latency: 2.016644ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:11:19Z"
    - latency: 1.595507ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:10:19Z"
    - latency: 2.143345ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:09:19Z"
    - latency: 1.905721ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:08:19Z"
    - latency: 2.218583ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:07:19Z"
    - latency: 1.96766ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:06:19Z"
    - latency: 1.860466ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:05:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T01:32:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-17-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-17.ec2.internal
      uid: 26b935e1-d974-4979-b49d-a29ebc00f4a5
    resourceVersion: "63927"
    uid: 6dbdb318-17db-433f-b54d-079e75a03f40
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q9lh5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T01:38:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 824.39µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:14:19Z"
    - latency: 2.117459ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:14:19Z"
    - latency: 813.795µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:13:19Z"
    - latency: 1.603407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:13:19Z"
    - latency: 773.829µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:12:19Z"
    - latency: 2.544273ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:12:19Z"
    - latency: 1.004767ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:11:19Z"
    - latency: 1.961834ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:11:19Z"
    - latency: 910.67µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T02:10:19Z"
    - latency: 1.598535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T02:10:19Z"
kind: List
metadata:
  resourceVersion: ""