apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T23:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-66-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-66.ec2.internal
      uid: 56cdcbaf-73b1-4f03-918e-d50274aed1a9
    resourceVersion: "53929"
    uid: 73990c09-3520-4878-95f3-629780258455
  spec:
    sourcePod: network-check-source-685456655f-rllx5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T23:46:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.601168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:07:41Z"
    - latency: 956.857µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:06:41Z"
    - latency: 977.621µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:05:41Z"
    - latency: 1.182695ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:04:41Z"
    - latency: 1.162283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:03:41Z"
    - latency: 1.167028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:02:41Z"
    - latency: 984.211µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:01:41Z"
    - latency: 1.356088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:00:41Z"
    - latency: 925.374µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T23:59:41Z"
    - latency: 937.962µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T23:58:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T23:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-66-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-66.ec2.internal
      uid: 56cdcbaf-73b1-4f03-918e-d50274aed1a9
    resourceVersion: "55903"
    uid: cf71e1ba-bff6-48a3-86fe-075f96bf5555
  spec:
    sourcePod: network-check-source-685456655f-rllx5
    targetEndpoint: abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T23:45:41Z"
      message: 'load-balancer-api-external: tcp connection to abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.15132ms
      message: 'load-balancer-api-external: tcp connection to abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:09:41Z"
    - latency: 7.55965ms
      message: 'load-balancer-api-external: resolved host name abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:09:41Z"
    - latency: 4.386861ms
      message: 'load-balancer-api-external: tcp connection to abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:08:41Z"
    - latency: 7.741225ms
      message: 'load-balancer-api-external: resolved host name abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:08:41Z"
    - latency: 4.567591ms
      message: 'load-balancer-api-external: tcp connection to abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:07:41Z"
    - latency: 7.649613ms
      message: 'load-balancer-api-external: resolved host name abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:07:41Z"
    - latency: 4.614752ms
      message: 'load-balancer-api-external: tcp connection to abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:06:41Z"
    - latency: 6.428126ms
      message: 'load-balancer-api-external: resolved host name abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:06:41Z"
    - latency: 4.289286ms
      message: 'load-balancer-api-external: tcp connection to abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:05:41Z"
    - latency: 7.332655ms
      message: 'load-balancer-api-external: resolved host name abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:05:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T23:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-66-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-66.ec2.internal
      uid: 56cdcbaf-73b1-4f03-918e-d50274aed1a9
    resourceVersion: "55902"
    uid: 2bc1c740-a93e-40b2-9309-9a88bfdd4f00
  spec:
    sourcePod: network-check-source-685456655f-rllx5
    targetEndpoint: abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T23:45:41Z"
      message: 'load-balancer-api-internal: tcp connection to abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.135292ms
      message: 'load-balancer-api-internal: tcp connection to abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:09:41Z"
    - latency: 7.723193ms
      message: 'load-balancer-api-internal: resolved host name abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:09:41Z"
    - latency: 4.419987ms
      message: 'load-balancer-api-internal: tcp connection to abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:08:41Z"
    - latency: 7.71332ms
      message: 'load-balancer-api-internal: resolved host name abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:08:41Z"
    - latency: 4.548314ms
      message: 'load-balancer-api-internal: tcp connection to abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:07:41Z"
    - latency: 7.836372ms
      message: 'load-balancer-api-internal: resolved host name abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:07:41Z"
    - latency: 4.652657ms
      message: 'load-balancer-api-internal: tcp connection to abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:06:41Z"
    - latency: 6.386615ms
      message: 'load-balancer-api-internal: resolved host name abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:06:41Z"
    - latency: 4.279774ms
      message: 'load-balancer-api-internal: tcp connection to abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:05:41Z"
    - latency: 7.421033ms
      message: 'load-balancer-api-internal: resolved host name abd68130d6438442aa806fee5933151f-e256fb3bd61ccbb1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:05:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T23:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-66-to-network-check-target-ip-10-0-138-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-66.ec2.internal
      uid: 56cdcbaf-73b1-4f03-918e-d50274aed1a9
    resourceVersion: "53926"
    uid: cd4c9198-e56b-4a60-a640-ad90de57442b
  spec:
    sourcePod: network-check-source-685456655f-rllx5
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T23:46:41Z"
      message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.235865ms
      message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:07:41Z"
    - latency: 1.038689ms
      message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:06:41Z"
    - latency: 808.056µs
      message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:05:41Z"
    - latency: 961.509µs
      message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:04:41Z"
    - latency: 824.366µs
      message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:03:41Z"
    - latency: 1.383718ms
      message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:02:41Z"
    - latency: 1.675378ms
      message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:01:41Z"
    - latency: 1.559694ms
      message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:00:41Z"
    - latency: 1.648618ms
      message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T23:59:41Z"
    - latency: 1.370712ms
      message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T23:58:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T23:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-66-to-network-check-target-ip-10-0-139-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-66.ec2.internal
      uid: 56cdcbaf-73b1-4f03-918e-d50274aed1a9
    resourceVersion: "53927"
    uid: 9c015dc9-0874-46d1-8974-74544175fc47
  spec:
    sourcePod: network-check-source-685456655f-rllx5
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T23:46:41Z"
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.901062ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:07:41Z"
    - latency: 2.247559ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:06:41Z"
    - latency: 1.754089ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:05:41Z"
    - latency: 1.828834ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:04:41Z"
    - latency: 1.842086ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:03:41Z"
    - latency: 2.776812ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:02:41Z"
    - latency: 1.510102ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:01:41Z"
    - latency: 2.129052ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:00:41Z"
    - latency: 2.335438ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T23:59:41Z"
    - latency: 3.052062ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T23:58:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T23:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-66-to-network-check-target-ip-10-0-142-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-66.ec2.internal
      uid: 56cdcbaf-73b1-4f03-918e-d50274aed1a9
    resourceVersion: "53928"
    uid: c7052b0e-748a-4d4f-9b20-fac96a7d6279
  spec:
    sourcePod: network-check-source-685456655f-rllx5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T23:46:41Z"
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.000581ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:07:41Z"
    - latency: 2.014429ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:06:41Z"
    - latency: 2.246633ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:05:41Z"
    - latency: 1.929661ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:04:41Z"
    - latency: 2.135672ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:03:41Z"
    - latency: 2.255317ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:02:41Z"
    - latency: 1.85238ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:01:41Z"
    - latency: 2.063667ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:00:41Z"
    - latency: 2.138993ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T23:59:41Z"
    - latency: 2.383786ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T23:58:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T23:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-66-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-66.ec2.internal
      uid: 56cdcbaf-73b1-4f03-918e-d50274aed1a9
    resourceVersion: "55901"
    uid: c4b5034d-ae88-401b-9399-2e95c83f1242
  spec:
    sourcePod: network-check-source-685456655f-rllx5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T23:45:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.277654ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:09:41Z"
    - latency: 1.935065ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:09:41Z"
    - latency: 1.120971ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:08:41Z"
    - latency: 2.079299ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:08:41Z"
    - latency: 1.013467ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:07:41Z"
    - latency: 2.166407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:07:41Z"
    - latency: 996.923µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:06:41Z"
    - latency: 1.97516ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:06:41Z"
    - latency: 799.472µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T00:05:41Z"
    - latency: 2.197878ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T00:05:41Z"
kind: List
metadata:
  resourceVersion: ""