apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:53:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: 0e4f8773-8018-4a45-85db-857574d065d3
    resourceVersion: "86576"
    uid: c0a8ae1c-807b-4973-a80e-6de0a8d32647
  spec:
    sourcePod: network-check-source-7d88cb55d8-pd6zq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T23:00:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.521µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:10:11Z"
    - latency: 1.117525ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:09:11Z"
    - latency: 950.275µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:08:11Z"
    - latency: 1.728855ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:07:11Z"
    - latency: 1.703012ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:06:11Z"
    - latency: 1.170198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:05:11Z"
    - latency: 1.012021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:04:11Z"
    - latency: 1.0469ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:03:11Z"
    - latency: 1.271368ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:02:11Z"
    - latency: 1.142117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:01:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:53:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: 0e4f8773-8018-4a45-85db-857574d065d3
    resourceVersion: "87722"
    uid: ded5d836-de87-4036-bcea-497cbcc79f49
  spec:
    sourcePod: network-check-source-7d88cb55d8-pd6zq
    targetEndpoint: ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:59:11Z"
      message: 'load-balancer-api-external: tcp connection to ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.127459ms
      message: 'load-balancer-api-external: tcp connection to ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:11:11Z"
    - latency: 7.102613ms
      message: 'load-balancer-api-external: resolved host name ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:11:11Z"
    - latency: 5.39412ms
      message: 'load-balancer-api-external: tcp connection to ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:10:11Z"
    - latency: 6.918824ms
      message: 'load-balancer-api-external: resolved host name ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:10:11Z"
    - latency: 5.368709ms
      message: 'load-balancer-api-external: tcp connection to ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:09:11Z"
    - latency: 7.177368ms
      message: 'load-balancer-api-external: resolved host name ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:09:11Z"
    - latency: 5.312565ms
      message: 'load-balancer-api-external: tcp connection to ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:08:11Z"
    - latency: 10.895787ms
      message: 'load-balancer-api-external: resolved host name ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:08:11Z"
    - latency: 4.712373ms
      message: 'load-balancer-api-external: tcp connection to ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:07:11Z"
    - latency: 7.827669ms
      message: 'load-balancer-api-external: resolved host name ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:07:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:53:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: 0e4f8773-8018-4a45-85db-857574d065d3
    resourceVersion: "87723"
    uid: 51e2a1f9-d116-4b58-b596-d69505442269
  spec:
    sourcePod: network-check-source-7d88cb55d8-pd6zq
    targetEndpoint: ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:59:11Z"
      message: 'load-balancer-api-internal: tcp connection to ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.164206ms
      message: 'load-balancer-api-internal: tcp connection to ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:11:11Z"
    - latency: 6.896514ms
      message: 'load-balancer-api-internal: resolved host name ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:11:11Z"
    - latency: 5.474326ms
      message: 'load-balancer-api-internal: tcp connection to ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:10:11Z"
    - latency: 6.86022ms
      message: 'load-balancer-api-internal: resolved host name ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:10:11Z"
    - latency: 5.377349ms
      message: 'load-balancer-api-internal: tcp connection to ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:09:11Z"
    - latency: 7.112326ms
      message: 'load-balancer-api-internal: resolved host name ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:09:11Z"
    - latency: 5.396928ms
      message: 'load-balancer-api-internal: tcp connection to ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:08:11Z"
    - latency: 10.782566ms
      message: 'load-balancer-api-internal: resolved host name ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:08:11Z"
    - latency: 4.72698ms
      message: 'load-balancer-api-internal: tcp connection to ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:07:11Z"
    - latency: 7.7316ms
      message: 'load-balancer-api-internal: resolved host name ada79eace9eb4497397b552019af76bd-dd4019bb9b7ba4c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:07:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:53:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-network-check-target-ip-10-0-128-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: 0e4f8773-8018-4a45-85db-857574d065d3
    resourceVersion: "86575"
    uid: 88f5b735-8c7e-4bd2-be28-56b86b9f480c
  spec:
    sourcePod: network-check-source-7d88cb55d8-pd6zq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T23:00:11Z"
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.304287ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:10:11Z"
    - latency: 1.887083ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:09:11Z"
    - latency: 1.953941ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:08:11Z"
    - latency: 1.821689ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:07:11Z"
    - latency: 1.861299ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:06:11Z"
    - latency: 1.535463ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:05:11Z"
    - latency: 1.637559ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:04:11Z"
    - latency: 2.037474ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:03:11Z"
    - latency: 1.827961ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:02:11Z"
    - latency: 1.899705ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:01:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:53:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-network-check-target-ip-10-0-131-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: 0e4f8773-8018-4a45-85db-857574d065d3
    resourceVersion: "86573"
    uid: 8344ef58-8482-4224-b681-5b16452c0f25
  spec:
    sourcePod: network-check-source-7d88cb55d8-pd6zq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T23:00:11Z"
      message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.08368ms
      message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:10:11Z"
    - latency: 1.098312ms
      message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:09:11Z"
    - latency: 990.412µs
      message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:08:11Z"
    - latency: 1.382735ms
      message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:07:11Z"
    - latency: 1.234642ms
      message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:06:11Z"
    - latency: 829.206µs
      message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:05:11Z"
    - latency: 832.858µs
      message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:04:11Z"
    - latency: 1.313754ms
      message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:03:11Z"
    - latency: 1.049308ms
      message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:02:11Z"
    - latency: 1.038584ms
      message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:01:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:53:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-network-check-target-ip-10-0-135-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: 0e4f8773-8018-4a45-85db-857574d065d3
    resourceVersion: "86574"
    uid: 47ef98f4-8ae0-4c8d-9d01-54585a38de58
  spec:
    sourcePod: network-check-source-7d88cb55d8-pd6zq
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T23:00:11Z"
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.983152ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:10:11Z"
    - latency: 2.217291ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:09:11Z"
    - latency: 2.347161ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:08:11Z"
    - latency: 2.179689ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:07:11Z"
    - latency: 2.287871ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:06:11Z"
    - latency: 2.214791ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:05:11Z"
    - latency: 2.064392ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:04:11Z"
    - latency: 2.503324ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:03:11Z"
    - latency: 2.31286ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:02:11Z"
    - latency: 2.148489ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:01:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:53:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: 0e4f8773-8018-4a45-85db-857574d065d3
    resourceVersion: "87721"
    uid: 0929c6a5-002a-4490-a22b-785f88693cb9
  spec:
    sourcePod: network-check-source-7d88cb55d8-pd6zq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:59:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.403285ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:11:11Z"
    - latency: 1.730012ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:11:11Z"
    - latency: 783.137µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:10:11Z"
    - latency: 1.970555ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:10:11Z"
    - latency: 921.739µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:09:11Z"
    - latency: 1.893853ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:09:11Z"
    - latency: 772.027µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:08:11Z"
    - latency: 2.338774ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:08:11Z"
    - latency: 870.315µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:07:11Z"
    - latency: 2.151397ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:07:11Z"
kind: List
metadata:
  resourceVersion: ""