apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T04:26:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-140-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-140.ec2.internal
      uid: 26f3cdc8-2d34-4f57-8847-5ce6631f7ccd
    resourceVersion: "54917"
    uid: 5ee96a6a-c760-411a-a372-91f58ba9e2f4
  spec:
    sourcePod: network-check-source-989f8b8dc-jnmnv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T04:34:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 835.848µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:02:00Z"
    - latency: 1.587012ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:01:00Z"
    - latency: 1.322252ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:00:00Z"
    - latency: 1.421264ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:59:00Z"
    - latency: 1.009717ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:58:00Z"
    - latency: 1.059989ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:57:00Z"
    - latency: 957.596µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:56:00Z"
    - latency: 1.278647ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:55:00Z"
    - latency: 996.822µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:54:00Z"
    - latency: 709.081µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:53:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T04:26:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-140-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-140.ec2.internal
      uid: 26f3cdc8-2d34-4f57-8847-5ce6631f7ccd
    resourceVersion: "55978"
    uid: 2c7b1932-21f9-439f-b315-8f43ed920a6b
  spec:
    sourcePod: network-check-source-989f8b8dc-jnmnv
    targetEndpoint: a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T04:33:00Z"
      message: 'load-balancer-api-external: tcp connection to a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.250875ms
      message: 'load-balancer-api-external: tcp connection to a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:03:00Z"
    - latency: 8.701527ms
      message: 'load-balancer-api-external: resolved host name a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T05:03:00Z"
    - latency: 4.705712ms
      message: 'load-balancer-api-external: tcp connection to a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:02:00Z"
    - latency: 9.574675ms
      message: 'load-balancer-api-external: resolved host name a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T05:02:00Z"
    - latency: 5.973002ms
      message: 'load-balancer-api-external: tcp connection to a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:01:00Z"
    - latency: 8.309426ms
      message: 'load-balancer-api-external: resolved host name a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T05:01:00Z"
    - latency: 5.69148ms
      message: 'load-balancer-api-external: tcp connection to a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:00:00Z"
    - latency: 7.217486ms
      message: 'load-balancer-api-external: resolved host name a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T05:00:00Z"
    - latency: 4.696181ms
      message: 'load-balancer-api-external: tcp connection to a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:59:00Z"
    - latency: 8.439472ms
      message: 'load-balancer-api-external: resolved host name a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T04:59:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T04:26:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-140-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-140.ec2.internal
      uid: 26f3cdc8-2d34-4f57-8847-5ce6631f7ccd
    resourceVersion: "55979"
    uid: 19e4de95-5b5d-41cf-8263-831bb5176073
  spec:
    sourcePod: network-check-source-989f8b8dc-jnmnv
    targetEndpoint: a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T04:33:00Z"
      message: 'load-balancer-api-internal: tcp connection to a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.653889ms
      message: 'load-balancer-api-internal: tcp connection to a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:03:00Z"
    - latency: 8.762113ms
      message: 'load-balancer-api-internal: resolved host name a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T05:03:00Z"
    - latency: 4.58113ms
      message: 'load-balancer-api-internal: tcp connection to a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:02:00Z"
    - latency: 9.548002ms
      message: 'load-balancer-api-internal: resolved host name a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T05:02:00Z"
    - latency: 3.936993ms
      message: 'load-balancer-api-internal: tcp connection to a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:01:00Z"
    - latency: 8.398799ms
      message: 'load-balancer-api-internal: resolved host name a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T05:01:00Z"
    - latency: 5.781336ms
      message: 'load-balancer-api-internal: tcp connection to a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:00:00Z"
    - latency: 7.253551ms
      message: 'load-balancer-api-internal: resolved host name a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T05:00:00Z"
    - latency: 4.327038ms
      message: 'load-balancer-api-internal: tcp connection to a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:59:00Z"
    - latency: 8.470953ms
      message: 'load-balancer-api-internal: resolved host name a22713a0380a44a7a8b732184dbdf2ec-78835c8c35656458.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T04:59:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T04:26:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-140-to-network-check-target-ip-10-0-128-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-140.ec2.internal
      uid: 26f3cdc8-2d34-4f57-8847-5ce6631f7ccd
    resourceVersion: "54915"
    uid: 5c7f80ce-fcba-4107-8c7b-bf118cdc14e1
  spec:
    sourcePod: network-check-source-989f8b8dc-jnmnv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T04:34:00Z"
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.321812ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:02:00Z"
    - latency: 2.342708ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:01:00Z"
    - latency: 2.572747ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:00:00Z"
    - latency: 2.452068ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:59:00Z"
    - latency: 2.290293ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:58:00Z"
    - latency: 2.615927ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:57:00Z"
    - latency: 1.955893ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:56:00Z"
    - latency: 2.758991ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:55:00Z"
    - latency: 1.83096ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:54:00Z"
    - latency: 2.218605ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:53:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T04:26:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-140-to-network-check-target-ip-10-0-142-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-140.ec2.internal
      uid: 26f3cdc8-2d34-4f57-8847-5ce6631f7ccd
    resourceVersion: "54916"
    uid: e64cc061-7006-481f-9550-19e9f49ac31a
  spec:
    sourcePod: network-check-source-989f8b8dc-jnmnv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T04:34:00Z"
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.032646ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:02:00Z"
    - latency: 2.313835ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:01:00Z"
    - latency: 3.063978ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:00:00Z"
    - latency: 2.964671ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:59:00Z"
    - latency: 2.490677ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:58:00Z"
    - latency: 2.154345ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:57:00Z"
    - latency: 1.967468ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:56:00Z"
    - latency: 2.30456ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:55:00Z"
    - latency: 2.268743ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:54:00Z"
    - latency: 2.086475ms
      message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:53:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T04:26:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-140-to-network-check-target-ip-10-0-142-140
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-140.ec2.internal
      uid: 26f3cdc8-2d34-4f57-8847-5ce6631f7ccd
    resourceVersion: "54914"
    uid: 49a403a6-4268-486d-bc02-06173dc8ff27
  spec:
    sourcePod: network-check-source-989f8b8dc-jnmnv
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T04:34:00Z"
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 800.329µs
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:02:00Z"
    - latency: 996.013µs
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:01:00Z"
    - latency: 1.047357ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:00:00Z"
    - latency: 1.587055ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:59:00Z"
    - latency: 955.402µs
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:58:00Z"
    - latency: 841.775µs
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:57:00Z"
    - latency: 854.884µs
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:56:00Z"
    - latency: 903.799µs
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:55:00Z"
    - latency: 1.231063ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:54:00Z"
    - latency: 1.199997ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:53:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T04:26:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-140-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-140.ec2.internal
      uid: 26f3cdc8-2d34-4f57-8847-5ce6631f7ccd
    resourceVersion: "55977"
    uid: e272c663-2161-4fde-905d-e3682fca2633
  spec:
    sourcePod: network-check-source-989f8b8dc-jnmnv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T04:33:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.253009ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:03:00Z"
    - latency: 1.741609ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T05:03:00Z"
    - latency: 1.128839ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:02:00Z"
    - latency: 2.02367ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T05:02:00Z"
    - latency: 960.962µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:01:00Z"
    - latency: 2.224966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T05:01:00Z"
    - latency: 865.876µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T05:00:00Z"
    - latency: 2.008283ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T05:00:00Z"
    - latency: 923.651µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T04:59:00Z"
    - latency: 1.688145ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T04:59:00Z"
kind: List
metadata:
  resourceVersion: ""