apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:23:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.us-east-2.compute.internal
      uid: ed9896ab-e4cb-4591-864b-cb4cd757562b
    resourceVersion: "31276"
    uid: 54e41ca8-61bd-4ff8-ac22-2090e76c66be
  spec:
    sourcePod: network-check-source-6f78d59f99-nzn7w
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:30:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.187µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:37:26Z"
    - latency: 1.031582ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:36:26Z"
    - latency: 1.004868ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:35:26Z"
    - latency: 808.977µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:34:26Z"
    - latency: 1.126176ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:33:26Z"
    - latency: 1.645372ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:32:26Z"
    - latency: 1.388945ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:31:26Z"
    - latency: 1.090995ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:30:26Z"
    - latency: 817.153µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:29:26Z"
    - latency: 1.259236ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:23:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.us-east-2.compute.internal
      uid: ed9896ab-e4cb-4591-864b-cb4cd757562b
    resourceVersion: "26002"
    uid: 8027b2d4-f4ed-40a1-bf65-34b925fb4789
  spec:
    sourcePod: network-check-source-6f78d59f99-nzn7w
    targetEndpoint: a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:29:26Z"
      message: 'load-balancer-api-external: tcp connection to a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.881089ms
      message: 'load-balancer-api-external: tcp connection to a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:35:26Z"
    - latency: 6.942046ms
      message: 'load-balancer-api-external: resolved host name a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:35:26Z"
    - latency: 4.586572ms
      message: 'load-balancer-api-external: tcp connection to a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:34:26Z"
    - latency: 7.347266ms
      message: 'load-balancer-api-external: resolved host name a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:34:26Z"
    - latency: 18.976896ms
      message: 'load-balancer-api-external: tcp connection to a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:33:26Z"
    - latency: 8.450833ms
      message: 'load-balancer-api-external: resolved host name a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:33:26Z"
    - latency: 6.817715ms
      message: 'load-balancer-api-external: tcp connection to a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:32:26Z"
    - latency: 9.183778ms
      message: 'load-balancer-api-external: resolved host name a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:32:26Z"
    - latency: 5.039829ms
      message: 'load-balancer-api-external: tcp connection to a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:31:26Z"
    - latency: 7.646189ms
      message: 'load-balancer-api-external: resolved host name a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:31:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:23:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.us-east-2.compute.internal
      uid: ed9896ab-e4cb-4591-864b-cb4cd757562b
    resourceVersion: "26001"
    uid: 4ae12640-c0ca-448e-8e7d-a2197614d514
  spec:
    sourcePod: network-check-source-6f78d59f99-nzn7w
    targetEndpoint: a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:29:26Z"
      message: 'load-balancer-api-internal: tcp connection to a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.720875ms
      message: 'load-balancer-api-internal: tcp connection to a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:35:26Z"
    - latency: 7.05815ms
      message: 'load-balancer-api-internal: resolved host name a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:35:26Z"
    - latency: 4.630381ms
      message: 'load-balancer-api-internal: tcp connection to a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:34:26Z"
    - latency: 7.370226ms
      message: 'load-balancer-api-internal: resolved host name a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:34:26Z"
    - latency: 9.945825ms
      message: 'load-balancer-api-internal: tcp connection to a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:33:26Z"
    - latency: 8.401309ms
      message: 'load-balancer-api-internal: resolved host name a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:33:26Z"
    - latency: 6.808152ms
      message: 'load-balancer-api-internal: tcp connection to a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:32:26Z"
    - latency: 9.253125ms
      message: 'load-balancer-api-internal: resolved host name a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:32:26Z"
    - latency: 4.923753ms
      message: 'load-balancer-api-internal: tcp connection to a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:31:26Z"
    - latency: 7.746483ms
      message: 'load-balancer-api-internal: resolved host name a4c59d3c2c16441b2a5fa6dfd490a52c-01f026c92018bb63.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:31:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:23:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-network-check-target-ip-10-0-130-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.us-east-2.compute.internal
      uid: ed9896ab-e4cb-4591-864b-cb4cd757562b
    resourceVersion: "31273"
    uid: 5029c6af-e1c9-499d-932f-68ecc98544ee
  spec:
    sourcePod: network-check-source-6f78d59f99-nzn7w
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:30:26Z"
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 866.45µs
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:37:26Z"
    - latency: 1.409547ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:36:26Z"
    - latency: 956.868µs
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:35:26Z"
    - latency: 998.886µs
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:34:26Z"
    - latency: 927.414µs
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:33:26Z"
    - latency: 862.295µs
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:32:26Z"
    - latency: 1.584994ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:31:26Z"
    - latency: 1.316982ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:30:26Z"
    - latency: 1.229017ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:29:26Z"
    - latency: 1.531421ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:23:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-network-check-target-ip-10-0-130-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.us-east-2.compute.internal
      uid: ed9896ab-e4cb-4591-864b-cb4cd757562b
    resourceVersion: "31275"
    uid: 2cbc260d-5aa3-4146-8f81-2622f3bceec8
  spec:
    sourcePod: network-check-source-6f78d59f99-nzn7w
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:30:26Z"
      message: 'network-check-target-ip-10-0-130-63: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.289857ms
      message: 'network-check-target-ip-10-0-130-63: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:37:26Z"
    - latency: 2.385585ms
      message: 'network-check-target-ip-10-0-130-63: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:36:26Z"
    - latency: 2.825243ms
      message: 'network-check-target-ip-10-0-130-63: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:35:26Z"
    - latency: 2.970066ms
      message: 'network-check-target-ip-10-0-130-63: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:34:26Z"
    - latency: 2.35929ms
      message: 'network-check-target-ip-10-0-130-63: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:33:26Z"
    - latency: 2.602522ms
      message: 'network-check-target-ip-10-0-130-63: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:32:26Z"
    - latency: 2.460322ms
      message: 'network-check-target-ip-10-0-130-63: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:31:26Z"
    - latency: 2.273551ms
      message: 'network-check-target-ip-10-0-130-63: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:30:26Z"
    - latency: 2.141939ms
      message: 'network-check-target-ip-10-0-130-63: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:29:26Z"
    - latency: 2.490879ms
      message: 'network-check-target-ip-10-0-130-63: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:23:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-network-check-target-ip-10-0-143-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.us-east-2.compute.internal
      uid: ed9896ab-e4cb-4591-864b-cb4cd757562b
    resourceVersion: "31274"
    uid: 1c1dc123-e92f-42ed-89f6-0a1519d713ce
  spec:
    sourcePod: network-check-source-6f78d59f99-nzn7w
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:30:26Z"
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.99611ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:37:26Z"
    - latency: 2.410276ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:36:26Z"
    - latency: 2.454501ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:35:26Z"
    - latency: 2.489038ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:34:26Z"
    - latency: 2.752522ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:33:26Z"
    - latency: 2.409354ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:32:26Z"
    - latency: 2.443118ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:31:26Z"
    - latency: 2.394848ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:30:26Z"
    - latency: 2.216217ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:29:26Z"
    - latency: 2.257391ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:23:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-59-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-59.us-east-2.compute.internal
      uid: ed9896ab-e4cb-4591-864b-cb4cd757562b
    resourceVersion: "26000"
    uid: b1e2010a-db47-469d-9241-0003168aaf1b
  spec:
    sourcePod: network-check-source-6f78d59f99-nzn7w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:29:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 967.606µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:35:26Z"
    - latency: 2.048742ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:35:26Z"
    - latency: 939.48µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:34:26Z"
    - latency: 1.694915ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:34:26Z"
    - latency: 961.692µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:33:26Z"
    - latency: 1.675593ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:33:26Z"
    - latency: 990.042µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:32:26Z"
    - latency: 1.849382ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:32:26Z"
    - latency: 1.505914ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:31:26Z"
    - latency: 1.906178ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:31:26Z"
kind: List
metadata:
  resourceVersion: ""