apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-228-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-228.ec2.internal
      uid: a7642ea4-972c-428d-ad3c-dcb6ca700635
    resourceVersion: "39849"
    uid: e773c3b5-152d-4cc7-8ae0-216742b51d54
  spec:
    sourcePod: network-check-source-7f44b6dd87-cst47
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:44:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.727µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:33:10Z"
    - latency: 832.089µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:32:10Z"
    - latency: 1.065089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:31:10Z"
    - latency: 1.165519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:30:10Z"
    - latency: 906.13µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:29:10Z"
    - latency: 962.44µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:28:10Z"
    - latency: 1.339589ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:27:10Z"
    - latency: 750.297µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:26:10Z"
    - latency: 901.042µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:25:10Z"
    - latency: 1.028325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:24:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-228-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-228.ec2.internal
      uid: a7642ea4-972c-428d-ad3c-dcb6ca700635
    resourceVersion: "42082"
    uid: b97ac9ee-8432-491c-98e2-707282bd4e19
  spec:
    sourcePod: network-check-source-7f44b6dd87-cst47
    targetEndpoint: ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:43:10Z"
      message: 'load-balancer-api-external: tcp connection to ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.399264ms
      message: 'load-balancer-api-external: tcp connection to ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:37:10Z"
    - latency: 8.317495ms
      message: 'load-balancer-api-external: resolved host name ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:37:10Z"
    - latency: 5.303094ms
      message: 'load-balancer-api-external: tcp connection to ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:36:10Z"
    - latency: 7.863679ms
      message: 'load-balancer-api-external: resolved host name ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:36:10Z"
    - latency: 5.077811ms
      message: 'load-balancer-api-external: tcp connection to ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:35:10Z"
    - latency: 10.146292ms
      message: 'load-balancer-api-external: resolved host name ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:35:10Z"
    - latency: 4.004591ms
      message: 'load-balancer-api-external: tcp connection to ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:34:10Z"
    - latency: 9.241281ms
      message: 'load-balancer-api-external: resolved host name ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:34:10Z"
    - latency: 4.624909ms
      message: 'load-balancer-api-external: tcp connection to ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:33:10Z"
    - latency: 7.94484ms
      message: 'load-balancer-api-external: resolved host name ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:33:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-228-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-228.ec2.internal
      uid: a7642ea4-972c-428d-ad3c-dcb6ca700635
    resourceVersion: "42083"
    uid: 14c52814-a82e-4aef-8a54-8ab882b921c8
  spec:
    sourcePod: network-check-source-7f44b6dd87-cst47
    targetEndpoint: ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:43:10Z"
      message: 'load-balancer-api-internal: tcp connection to ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.418609ms
      message: 'load-balancer-api-internal: tcp connection to ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:37:10Z"
    - latency: 8.262269ms
      message: 'load-balancer-api-internal: resolved host name ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:37:10Z"
    - latency: 4.944428ms
      message: 'load-balancer-api-internal: tcp connection to ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:36:10Z"
    - latency: 7.832315ms
      message: 'load-balancer-api-internal: resolved host name ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:36:10Z"
    - latency: 5.110552ms
      message: 'load-balancer-api-internal: tcp connection to ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:35:10Z"
    - latency: 10.069282ms
      message: 'load-balancer-api-internal: resolved host name ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:35:10Z"
    - latency: 4.360395ms
      message: 'load-balancer-api-internal: tcp connection to ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:34:10Z"
    - latency: 9.30612ms
      message: 'load-balancer-api-internal: resolved host name ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:34:10Z"
    - latency: 4.614944ms
      message: 'load-balancer-api-internal: tcp connection to ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:33:10Z"
    - latency: 7.973192ms
      message: 'load-balancer-api-internal: resolved host name ac267d055c1384c63a377b67d9fbb784-0b81fa47d2db52e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:33:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-228-to-network-check-target-ip-10-0-130-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-228.ec2.internal
      uid: a7642ea4-972c-428d-ad3c-dcb6ca700635
    resourceVersion: "39846"
    uid: daa4bf9d-fa55-4287-8f51-7f327e05de29
  spec:
    sourcePod: network-check-source-7f44b6dd87-cst47
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:44:10Z"
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 843.803µs
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:33:10Z"
    - latency: 809.038µs
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:32:10Z"
    - latency: 924.357µs
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:31:10Z"
    - latency: 1.106953ms
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:30:10Z"
    - latency: 853.348µs
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:29:10Z"
    - latency: 858.943µs
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:28:10Z"
    - latency: 788.976µs
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:27:10Z"
    - latency: 844.033µs
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:26:10Z"
    - latency: 914.213µs
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:25:10Z"
    - latency: 1.645175ms
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:24:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-228-to-network-check-target-ip-10-0-134-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-228.ec2.internal
      uid: a7642ea4-972c-428d-ad3c-dcb6ca700635
    resourceVersion: "39847"
    uid: 1eab294d-178a-4dad-96d8-398cb5e73027
  spec:
    sourcePod: network-check-source-7f44b6dd87-cst47
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:44:10Z"
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.204653ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:33:10Z"
    - latency: 1.793206ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:32:10Z"
    - latency: 2.022642ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:31:10Z"
    - latency: 16.029429ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:30:10Z"
    - latency: 2.074693ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:29:10Z"
    - latency: 2.20737ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:28:10Z"
    - latency: 2.578598ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:27:10Z"
    - latency: 2.410641ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:26:10Z"
    - latency: 2.259818ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:25:10Z"
    - latency: 2.082608ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:24:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-228-to-network-check-target-ip-10-0-135-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-228.ec2.internal
      uid: a7642ea4-972c-428d-ad3c-dcb6ca700635
    resourceVersion: "39848"
    uid: 0db27c99-9ea4-485c-abbf-f0750e05d042
  spec:
    sourcePod: network-check-source-7f44b6dd87-cst47
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:44:10Z"
      message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.242817ms
      message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:33:10Z"
    - latency: 2.197676ms
      message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:32:10Z"
    - latency: 2.396195ms
      message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:31:10Z"
    - latency: 2.423229ms
      message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:30:10Z"
    - latency: 2.136557ms
      message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:29:10Z"
    - latency: 2.540751ms
      message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:28:10Z"
    - latency: 2.189348ms
      message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:27:10Z"
    - latency: 2.103489ms
      message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:26:10Z"
    - latency: 2.790579ms
      message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:25:10Z"
    - latency: 2.28836ms
      message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:24:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-228-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-228.ec2.internal
      uid: a7642ea4-972c-428d-ad3c-dcb6ca700635
    resourceVersion: "42081"
    uid: fcb086ac-1f10-4f58-80ce-21e00e701a26
  spec:
    sourcePod: network-check-source-7f44b6dd87-cst47
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:43:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.056703ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:37:10Z"
    - latency: 2.673076ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:37:10Z"
    - latency: 950.183µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:36:10Z"
    - latency: 1.612885ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:36:10Z"
    - latency: 809.224µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:35:10Z"
    - latency: 1.823973ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:35:10Z"
    - latency: 1.124807ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:34:10Z"
    - latency: 1.782291ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:34:10Z"
    - latency: 1.06793ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:33:10Z"
    - latency: 1.569493ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:33:10Z"
kind: List
metadata:
  resourceVersion: ""