apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:46:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 62e42b16-10f3-4a9c-a00c-53f6e3620741
    resourceVersion: "43981"
    uid: 4bfba207-34fe-46b7-8c7b-09c5cbce68a6
  spec:
    sourcePod: network-check-source-7f44b6dd87-nnrj6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:53:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.22745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:14:18Z"
    - latency: 1.036729ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:13:18Z"
    - latency: 1.039046ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:12:18Z"
    - latency: 1.21925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:11:18Z"
    - latency: 973.135µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:10:18Z"
    - latency: 818.158µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:09:18Z"
    - latency: 1.134318ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:08:18Z"
    - latency: 1.100729ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:07:18Z"
    - latency: 813.264µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:06:18Z"
    - latency: 1.032301ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:05:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:46:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 62e42b16-10f3-4a9c-a00c-53f6e3620741
    resourceVersion: "39669"
    uid: 437c3083-6e55-4819-a89a-4cea5a928bfb
  spec:
    sourcePod: network-check-source-7f44b6dd87-nnrj6
    targetEndpoint: ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:52:18Z"
      message: 'load-balancer-api-external: tcp connection to ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.270229ms
      message: 'load-balancer-api-external: tcp connection to ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:10:18Z"
    - latency: 7.362655ms
      message: 'load-balancer-api-external: resolved host name ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:10:18Z"
    - latency: 3.174111ms
      message: 'load-balancer-api-external: tcp connection to ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:09:18Z"
    - latency: 7.888634ms
      message: 'load-balancer-api-external: resolved host name ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:09:18Z"
    - latency: 5.01388ms
      message: 'load-balancer-api-external: tcp connection to ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:08:18Z"
    - latency: 7.303263ms
      message: 'load-balancer-api-external: resolved host name ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:08:18Z"
    - latency: 4.619127ms
      message: 'load-balancer-api-external: tcp connection to ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:07:18Z"
    - latency: 6.940585ms
      message: 'load-balancer-api-external: resolved host name ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:07:18Z"
    - latency: 4.153271ms
      message: 'load-balancer-api-external: tcp connection to ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:06:18Z"
    - latency: 7.489333ms
      message: 'load-balancer-api-external: resolved host name ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:06:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:46:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 62e42b16-10f3-4a9c-a00c-53f6e3620741
    resourceVersion: "39668"
    uid: f805033e-1202-479a-b383-dd5b344e2908
  spec:
    sourcePod: network-check-source-7f44b6dd87-nnrj6
    targetEndpoint: ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:52:18Z"
      message: 'load-balancer-api-internal: tcp connection to ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.687293ms
      message: 'load-balancer-api-internal: tcp connection to ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:10:18Z"
    - latency: 7.472758ms
      message: 'load-balancer-api-internal: resolved host name ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:10:18Z"
    - latency: 4.420591ms
      message: 'load-balancer-api-internal: tcp connection to ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:09:18Z"
    - latency: 7.813749ms
      message: 'load-balancer-api-internal: resolved host name ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:09:18Z"
    - latency: 4.979731ms
      message: 'load-balancer-api-internal: tcp connection to ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:08:18Z"
    - latency: 7.365884ms
      message: 'load-balancer-api-internal: resolved host name ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:08:18Z"
    - latency: 4.629493ms
      message: 'load-balancer-api-internal: tcp connection to ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:07:18Z"
    - latency: 6.873589ms
      message: 'load-balancer-api-internal: resolved host name ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:07:18Z"
    - latency: 3.881157ms
      message: 'load-balancer-api-internal: tcp connection to ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:06:18Z"
    - latency: 7.441468ms
      message: 'load-balancer-api-internal: resolved host name ac781bc92428e480b88cb06ca1d4b1ff-5b7094008319d333.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:06:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:46:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-network-check-target-ip-10-0-133-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 62e42b16-10f3-4a9c-a00c-53f6e3620741
    resourceVersion: "43980"
    uid: 1761a023-5c7b-4a20-aec3-66dec11f02cd
  spec:
    sourcePod: network-check-source-7f44b6dd87-nnrj6
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:53:18Z"
      message: 'network-check-target-ip-10-0-133-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.314662ms
      message: 'network-check-target-ip-10-0-133-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:14:18Z"
    - latency: 2.307209ms
      message: 'network-check-target-ip-10-0-133-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:13:18Z"
    - latency: 2.263229ms
      message: 'network-check-target-ip-10-0-133-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:12:18Z"
    - latency: 2.25097ms
      message: 'network-check-target-ip-10-0-133-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:11:18Z"
    - latency: 2.357429ms
      message: 'network-check-target-ip-10-0-133-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:10:18Z"
    - latency: 2.539338ms
      message: 'network-check-target-ip-10-0-133-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:09:18Z"
    - latency: 2.235253ms
      message: 'network-check-target-ip-10-0-133-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:08:18Z"
    - latency: 2.461278ms
      message: 'network-check-target-ip-10-0-133-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:07:18Z"
    - latency: 2.373714ms
      message: 'network-check-target-ip-10-0-133-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:06:18Z"
    - latency: 2.525263ms
      message: 'network-check-target-ip-10-0-133-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:05:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:46:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-network-check-target-ip-10-0-133-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 62e42b16-10f3-4a9c-a00c-53f6e3620741
    resourceVersion: "43979"
    uid: d3410b07-caab-40b6-bec6-cde2c2349780
  spec:
    sourcePod: network-check-source-7f44b6dd87-nnrj6
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:53:18Z"
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.391877ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:14:18Z"
    - latency: 2.179767ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:13:18Z"
    - latency: 2.065871ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:12:18Z"
    - latency: 2.22608ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:11:18Z"
    - latency: 2.0353ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:10:18Z"
    - latency: 2.368114ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:09:18Z"
    - latency: 2.239793ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:08:18Z"
    - latency: 2.244105ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:07:18Z"
    - latency: 2.121418ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:06:18Z"
    - latency: 2.18774ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:05:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:46:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-network-check-target-ip-10-0-141-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 62e42b16-10f3-4a9c-a00c-53f6e3620741
    resourceVersion: "43978"
    uid: df7848cf-e493-47f6-a6e8-6dc678882a51
  spec:
    sourcePod: network-check-source-7f44b6dd87-nnrj6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:53:18Z"
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 997.221µs
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:14:18Z"
    - latency: 840.725µs
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:13:18Z"
    - latency: 891.817µs
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:12:18Z"
    - latency: 852.315µs
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:11:18Z"
    - latency: 952.519µs
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:10:18Z"
    - latency: 977.374µs
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:09:18Z"
    - latency: 874.042µs
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:08:18Z"
    - latency: 882.702µs
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:07:18Z"
    - latency: 979.25µs
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:06:18Z"
    - latency: 1.349607ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:05:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:46:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 62e42b16-10f3-4a9c-a00c-53f6e3620741
    resourceVersion: "39667"
    uid: 487fdb0a-f7c2-4584-a2e5-af004e5f551a
  spec:
    sourcePod: network-check-source-7f44b6dd87-nnrj6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T21:52:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.366378ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:10:18Z"
    - latency: 1.47375ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:10:18Z"
    - latency: 831.097µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:09:18Z"
    - latency: 1.694686ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:09:18Z"
    - latency: 795.268µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:08:18Z"
    - latency: 1.684175ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:08:18Z"
    - latency: 909.876µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:07:18Z"
    - latency: 1.652994ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:07:18Z"
    - latency: 1.010173ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:06:18Z"
    - latency: 1.618481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:06:18Z"
kind: List
metadata:
  resourceVersion: ""