apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-114-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-114.ec2.internal
      uid: efffcb47-7dda-4f7d-aa96-2b109cd979b1
    resourceVersion: "60745"
    uid: 60a7dbc2-2dac-434c-b659-eaa04b9b2b98
  spec:
    sourcePod: network-check-source-869dcfcdcd-kl8kl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:30:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 845.96µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:03Z"
    - latency: 965.728µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:03Z"
    - latency: 928.568µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:03Z"
    - latency: 1.275305ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:03Z"
    - latency: 1.57802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:01:03Z"
    - latency: 1.037409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:00:03Z"
    - latency: 977.575µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:59:03Z"
    - latency: 924.374µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:58:03Z"
    - latency: 1.470667ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:57:03Z"
    - latency: 1.233014ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:56:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-114-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-114.ec2.internal
      uid: efffcb47-7dda-4f7d-aa96-2b109cd979b1
    resourceVersion: "60747"
    uid: 504614f6-6df2-40fb-ab30-2e83de5d65fc
  spec:
    sourcePod: network-check-source-869dcfcdcd-kl8kl
    targetEndpoint: a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:29:03Z"
      message: 'load-balancer-api-external: tcp connection to a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.691449ms
      message: 'load-balancer-api-external: tcp connection to a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:03Z"
    - latency: 6.767128ms
      message: 'load-balancer-api-external: resolved host name a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:05:03Z"
    - latency: 5.013233ms
      message: 'load-balancer-api-external: tcp connection to a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:03Z"
    - latency: 6.934851ms
      message: 'load-balancer-api-external: resolved host name a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:04:03Z"
    - latency: 5.020965ms
      message: 'load-balancer-api-external: tcp connection to a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:03Z"
    - latency: 6.885184ms
      message: 'load-balancer-api-external: resolved host name a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:03:03Z"
    - latency: 6.612395ms
      message: 'load-balancer-api-external: tcp connection to a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:03Z"
    - latency: 7.345149ms
      message: 'load-balancer-api-external: resolved host name a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:02:03Z"
    - latency: 4.262828ms
      message: 'load-balancer-api-external: tcp connection to a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:01:03Z"
    - latency: 7.548399ms
      message: 'load-balancer-api-external: resolved host name a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:01:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-114-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-114.ec2.internal
      uid: efffcb47-7dda-4f7d-aa96-2b109cd979b1
    resourceVersion: "60746"
    uid: 9fba45a2-e98c-4e17-81d1-abf13671b809
  spec:
    sourcePod: network-check-source-869dcfcdcd-kl8kl
    targetEndpoint: a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:29:03Z"
      message: 'load-balancer-api-internal: tcp connection to a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.358842ms
      message: 'load-balancer-api-internal: tcp connection to a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:03Z"
    - latency: 6.816103ms
      message: 'load-balancer-api-internal: resolved host name a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:05:03Z"
    - latency: 5.044816ms
      message: 'load-balancer-api-internal: tcp connection to a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:03Z"
    - latency: 6.886112ms
      message: 'load-balancer-api-internal: resolved host name a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:04:03Z"
    - latency: 4.968503ms
      message: 'load-balancer-api-internal: tcp connection to a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:03Z"
    - latency: 6.971068ms
      message: 'load-balancer-api-internal: resolved host name a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:03:03Z"
    - latency: 4.516514ms
      message: 'load-balancer-api-internal: tcp connection to a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:03Z"
    - latency: 7.268069ms
      message: 'load-balancer-api-internal: resolved host name a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:02:03Z"
    - latency: 4.270316ms
      message: 'load-balancer-api-internal: tcp connection to a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:01:03Z"
    - latency: 7.477053ms
      message: 'load-balancer-api-internal: resolved host name a1a857bc829d741929c12891da1cc2c6-17b745bcfd2304a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:01:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-114-to-network-check-target-ip-10-0-130-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-114.ec2.internal
      uid: efffcb47-7dda-4f7d-aa96-2b109cd979b1
    resourceVersion: "60741"
    uid: a80ad533-34b4-4070-ba06-ff823c5d7bf8
  spec:
    sourcePod: network-check-source-869dcfcdcd-kl8kl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:30:03Z"
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.132451ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:03Z"
    - latency: 866.984µs
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:03Z"
    - latency: 919.907µs
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:03Z"
    - latency: 905.901µs
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:03Z"
    - latency: 960.02µs
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:01:03Z"
    - latency: 900.068µs
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:00:03Z"
    - latency: 864.42µs
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:59:03Z"
    - latency: 860.189µs
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:58:03Z"
    - latency: 875.273µs
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:57:03Z"
    - latency: 867.25µs
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:56:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-114-to-network-check-target-ip-10-0-133-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-114.ec2.internal
      uid: efffcb47-7dda-4f7d-aa96-2b109cd979b1
    resourceVersion: "60742"
    uid: e81fbfd7-2fc5-44bf-a5a4-46151fccfe47
  spec:
    sourcePod: network-check-source-869dcfcdcd-kl8kl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:30:03Z"
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.130867ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:03Z"
    - latency: 2.079064ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:03Z"
    - latency: 3.154004ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:03Z"
    - latency: 1.972455ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:03Z"
    - latency: 2.43282ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:01:03Z"
    - latency: 2.287295ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:00:03Z"
    - latency: 2.300558ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:59:03Z"
    - latency: 1.905777ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:58:03Z"
    - latency: 2.011975ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:57:03Z"
    - latency: 2.35771ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:56:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-114-to-network-check-target-ip-10-0-134-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-114.ec2.internal
      uid: efffcb47-7dda-4f7d-aa96-2b109cd979b1
    resourceVersion: "60743"
    uid: c791fd46-0cff-4b36-9a0b-913c7a66070a
  spec:
    sourcePod: network-check-source-869dcfcdcd-kl8kl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:30:03Z"
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.935631ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:03Z"
    - latency: 2.333737ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:03Z"
    - latency: 3.046295ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:03Z"
    - latency: 2.304834ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:03Z"
    - latency: 2.319058ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:01:03Z"
    - latency: 2.0082ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:00:03Z"
    - latency: 2.388608ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:59:03Z"
    - latency: 2.245963ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:58:03Z"
    - latency: 2.085852ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:57:03Z"
    - latency: 2.234551ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:56:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-114-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-114.ec2.internal
      uid: efffcb47-7dda-4f7d-aa96-2b109cd979b1
    resourceVersion: "60744"
    uid: 4cfc1546-1e2f-4b63-9721-5c9b6a6ad4ad
  spec:
    sourcePod: network-check-source-869dcfcdcd-kl8kl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:29:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.077558ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:03Z"
    - latency: 1.939449ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:05:03Z"
    - latency: 969.673µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:03Z"
    - latency: 2.048534ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:04:03Z"
    - latency: 1.322623ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:03Z"
    - latency: 2.140142ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:03:03Z"
    - latency: 958.119µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:03Z"
    - latency: 1.971303ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:02:03Z"
    - latency: 1.26672ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:01:03Z"
    - latency: 1.844081ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:01:03Z"
kind: List
metadata:
  resourceVersion: ""