apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-3-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-3.ec2.internal
      uid: c56562d0-d7e3-4730-a8e7-d930af22d546
    resourceVersion: "69371"
    uid: c771fc93-355e-44a8-a7d8-c67ba85b3575
  spec:
    sourcePod: network-check-source-7d88cb55d8-wqs5n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:11:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.180186ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:53:09Z"
    - latency: 1.02994ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:52:09Z"
    - latency: 1.358188ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:51:09Z"
    - latency: 1.257585ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:50:09Z"
    - latency: 1.043835ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:49:09Z"
    - latency: 884.771µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:48:09Z"
    - latency: 1.204246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:47:09Z"
    - latency: 1.14884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:46:09Z"
    - latency: 1.255126ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:45:09Z"
    - latency: 1.060239ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:44:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-3-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-3.ec2.internal
      uid: c56562d0-d7e3-4730-a8e7-d930af22d546
    resourceVersion: "79058"
    uid: 1b8e08bf-f83c-4e59-92ed-29b635945471
  spec:
    sourcePod: network-check-source-7d88cb55d8-wqs5n
    targetEndpoint: aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:10:09Z"
      message: 'load-balancer-api-external: tcp connection to aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.204882ms
      message: 'load-balancer-api-external: tcp connection to aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:58:09Z"
    - latency: 7.329691ms
      message: 'load-balancer-api-external: resolved host name aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:58:09Z"
    - latency: 5.439143ms
      message: 'load-balancer-api-external: tcp connection to aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:57:09Z"
    - latency: 7.634931ms
      message: 'load-balancer-api-external: resolved host name aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:57:09Z"
    - latency: 5.781867ms
      message: 'load-balancer-api-external: tcp connection to aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:56:09Z"
    - latency: 6.994246ms
      message: 'load-balancer-api-external: resolved host name aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:56:09Z"
    - latency: 4.719778ms
      message: 'load-balancer-api-external: tcp connection to aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:55:09Z"
    - latency: 6.98523ms
      message: 'load-balancer-api-external: resolved host name aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:55:09Z"
    - latency: 4.535371ms
      message: 'load-balancer-api-external: tcp connection to aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:54:09Z"
    - latency: 7.602875ms
      message: 'load-balancer-api-external: resolved host name aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:54:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-3-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-3.ec2.internal
      uid: c56562d0-d7e3-4730-a8e7-d930af22d546
    resourceVersion: "79059"
    uid: 15e621a7-4989-49ae-906f-b8ef8f970d8b
  spec:
    sourcePod: network-check-source-7d88cb55d8-wqs5n
    targetEndpoint: aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:10:09Z"
      message: 'load-balancer-api-internal: tcp connection to aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.297908ms
      message: 'load-balancer-api-internal: tcp connection to aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:58:09Z"
    - latency: 7.236262ms
      message: 'load-balancer-api-internal: resolved host name aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:58:09Z"
    - latency: 5.361192ms
      message: 'load-balancer-api-internal: tcp connection to aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:57:09Z"
    - latency: 7.661516ms
      message: 'load-balancer-api-internal: resolved host name aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:57:09Z"
    - latency: 5.981196ms
      message: 'load-balancer-api-internal: tcp connection to aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:56:09Z"
    - latency: 7.022508ms
      message: 'load-balancer-api-internal: resolved host name aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:56:09Z"
    - latency: 4.492703ms
      message: 'load-balancer-api-internal: tcp connection to aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:55:09Z"
    - latency: 6.947813ms
      message: 'load-balancer-api-internal: resolved host name aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:55:09Z"
    - latency: 4.563557ms
      message: 'load-balancer-api-internal: tcp connection to aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:54:09Z"
    - latency: 7.682223ms
      message: 'load-balancer-api-internal: resolved host name aa7a85fe2a4524ef6ac4a49183204b08-705437d9b3b86c39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:54:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-3-to-network-check-target-ip-10-0-137-91
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-3.ec2.internal
      uid: c56562d0-d7e3-4730-a8e7-d930af22d546
    resourceVersion: "69369"
    uid: 39418ca8-5deb-4b12-b812-9260f88aedea
  spec:
    sourcePod: network-check-source-7d88cb55d8-wqs5n
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:11:09Z"
      message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.591152ms
      message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:53:09Z"
    - latency: 2.440368ms
      message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:52:09Z"
    - latency: 2.466503ms
      message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:51:09Z"
    - latency: 2.251097ms
      message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:50:09Z"
    - latency: 2.433855ms
      message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:49:09Z"
    - latency: 2.441463ms
      message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:48:09Z"
    - latency: 2.20339ms
      message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:47:09Z"
    - latency: 2.328246ms
      message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:46:09Z"
    - latency: 2.406227ms
      message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:45:09Z"
    - latency: 2.358528ms
      message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:44:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-3-to-network-check-target-ip-10-0-141-71
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-3.ec2.internal
      uid: c56562d0-d7e3-4730-a8e7-d930af22d546
    resourceVersion: "69370"
    uid: b1b2b94b-7d7e-4ce7-a7fb-76f06527ad34
  spec:
    sourcePod: network-check-source-7d88cb55d8-wqs5n
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:11:09Z"
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.138902ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:53:09Z"
    - latency: 2.338954ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:52:09Z"
    - latency: 2.176318ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:51:09Z"
    - latency: 2.354341ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:50:09Z"
    - latency: 1.696329ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:49:09Z"
    - latency: 1.877623ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:48:09Z"
    - latency: 1.951453ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:47:09Z"
    - latency: 2.147681ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:46:09Z"
    - latency: 2.356485ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:45:09Z"
    - latency: 2.500845ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:44:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-3-to-network-check-target-ip-10-0-143-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-3.ec2.internal
      uid: c56562d0-d7e3-4730-a8e7-d930af22d546
    resourceVersion: "69368"
    uid: b798f113-7be3-43bb-89c6-d5d1b015612e
  spec:
    sourcePod: network-check-source-7d88cb55d8-wqs5n
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:11:09Z"
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.101837ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:53:09Z"
    - latency: 1.122509ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:52:09Z"
    - latency: 1.01643ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:51:09Z"
    - latency: 806.465µs
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:50:09Z"
    - latency: 1.694496ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:49:09Z"
    - latency: 880.001µs
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:48:09Z"
    - latency: 1.088814ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:47:09Z"
    - latency: 1.061743ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:46:09Z"
    - latency: 1.225477ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:45:09Z"
    - latency: 1.51083ms
      message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:44:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-3-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-3.ec2.internal
      uid: c56562d0-d7e3-4730-a8e7-d930af22d546
    resourceVersion: "79057"
    uid: 5206cbd3-1270-4e64-93d8-692ee1fecbcf
  spec:
    sourcePod: network-check-source-7d88cb55d8-wqs5n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:10:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.622µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:58:09Z"
    - latency: 1.704865ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:58:09Z"
    - latency: 944.084µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:57:09Z"
    - latency: 1.75298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:57:09Z"
    - latency: 1.338699ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:56:09Z"
    - latency: 1.980282ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:56:09Z"
    - latency: 1.453044ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:55:09Z"
    - latency: 1.941684ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:55:09Z"
    - latency: 968.497µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:54:09Z"
    - latency: 1.723717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:54:09Z"
kind: List
metadata:
  resourceVersion: ""