apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T22:13:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.ec2.internal
      uid: ece25633-a4dd-43d1-9a6a-990700a5de3d
    resourceVersion: "53864"
    uid: e522c264-6612-42ce-8309-3916d43e5098
  spec:
    sourcePod: network-check-source-685456655f-nzhrn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:20:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.054741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:41:39Z"
    - latency: 878.263µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:40:39Z"
    - latency: 1.472804ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:39:39Z"
    - latency: 1.133908ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:38:39Z"
    - latency: 1.295761ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:37:39Z"
    - latency: 1.192536ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:36:39Z"
    - latency: 1.028175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:35:39Z"
    - latency: 1.302266ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:34:39Z"
    - latency: 1.16041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:33:39Z"
    - latency: 937.007µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:32:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T22:13:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.ec2.internal
      uid: ece25633-a4dd-43d1-9a6a-990700a5de3d
    resourceVersion: "55336"
    uid: 43657a5e-9017-4110-82a7-7212014e21d2
  spec:
    sourcePod: network-check-source-685456655f-nzhrn
    targetEndpoint: aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:19:39Z"
      message: 'load-balancer-api-external: tcp connection to aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.916814ms
      message: 'load-balancer-api-external: tcp connection to aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:43:39Z"
    - latency: 8.945341ms
      message: 'load-balancer-api-external: resolved host name aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:43:39Z"
    - latency: 5.207164ms
      message: 'load-balancer-api-external: tcp connection to aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:42:39Z"
    - latency: 10.500442ms
      message: 'load-balancer-api-external: resolved host name aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:42:39Z"
    - latency: 4.277702ms
      message: 'load-balancer-api-external: tcp connection to aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:41:39Z"
    - latency: 8.975562ms
      message: 'load-balancer-api-external: resolved host name aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:41:39Z"
    - latency: 5.290252ms
      message: 'load-balancer-api-external: tcp connection to aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:40:39Z"
    - latency: 11.055458ms
      message: 'load-balancer-api-external: resolved host name aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:40:39Z"
    - latency: 4.168808ms
      message: 'load-balancer-api-external: tcp connection to aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:39:39Z"
    - latency: 8.831369ms
      message: 'load-balancer-api-external: resolved host name aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:39:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T22:13:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.ec2.internal
      uid: ece25633-a4dd-43d1-9a6a-990700a5de3d
    resourceVersion: "55335"
    uid: 00fbce44-6d91-45b4-8dbf-787d6b0553bf
  spec:
    sourcePod: network-check-source-685456655f-nzhrn
    targetEndpoint: aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:19:39Z"
      message: 'load-balancer-api-internal: tcp connection to aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.926859ms
      message: 'load-balancer-api-internal: tcp connection to aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:43:39Z"
    - latency: 8.865243ms
      message: 'load-balancer-api-internal: resolved host name aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:43:39Z"
    - latency: 4.743995ms
      message: 'load-balancer-api-internal: tcp connection to aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:42:39Z"
    - latency: 10.55542ms
      message: 'load-balancer-api-internal: resolved host name aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:42:39Z"
    - latency: 4.246615ms
      message: 'load-balancer-api-internal: tcp connection to aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:41:39Z"
    - latency: 8.957912ms
      message: 'load-balancer-api-internal: resolved host name aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:41:39Z"
    - latency: 5.23479ms
      message: 'load-balancer-api-internal: tcp connection to aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:40:39Z"
    - latency: 11.128042ms
      message: 'load-balancer-api-internal: resolved host name aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:40:39Z"
    - latency: 4.160154ms
      message: 'load-balancer-api-internal: tcp connection to aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:39:39Z"
    - latency: 8.882008ms
      message: 'load-balancer-api-internal: resolved host name aad92bc6fb06340ff8ee20a326ebd014-749fb0e024757a81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:39:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T22:13:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-network-check-target-ip-10-0-137-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.ec2.internal
      uid: ece25633-a4dd-43d1-9a6a-990700a5de3d
    resourceVersion: "53862"
    uid: 6ddadd4f-b70c-4223-b032-0d41ed5e8bf2
  spec:
    sourcePod: network-check-source-685456655f-nzhrn
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:20:39Z"
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.088386ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:41:39Z"
    - latency: 1.066174ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:40:39Z"
    - latency: 1.225901ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:39:39Z"
    - latency: 921.964µs
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:38:39Z"
    - latency: 1.472284ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:37:39Z"
    - latency: 1.269981ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:36:39Z"
    - latency: 1.008699ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:35:39Z"
    - latency: 864.881µs
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:34:39Z"
    - latency: 1.033556ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:33:39Z"
    - latency: 968.322µs
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:32:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T22:13:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-network-check-target-ip-10-0-139-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.ec2.internal
      uid: ece25633-a4dd-43d1-9a6a-990700a5de3d
    resourceVersion: "53861"
    uid: 03b948ec-279e-4eb3-9cb5-05c85393378a
  spec:
    sourcePod: network-check-source-685456655f-nzhrn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:20:39Z"
      message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.201658ms
      message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:41:39Z"
    - latency: 2.374285ms
      message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:40:39Z"
    - latency: 2.17323ms
      message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:39:39Z"
    - latency: 2.081936ms
      message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:38:39Z"
    - latency: 2.402716ms
      message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:37:39Z"
    - latency: 2.317161ms
      message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:36:39Z"
    - latency: 2.439903ms
      message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:35:39Z"
    - latency: 2.440545ms
      message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:34:39Z"
    - latency: 2.426094ms
      message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:33:39Z"
    - latency: 2.303165ms
      message: 'network-check-target-ip-10-0-139-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:32:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T22:13:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-network-check-target-ip-10-0-139-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.ec2.internal
      uid: ece25633-a4dd-43d1-9a6a-990700a5de3d
    resourceVersion: "53860"
    uid: 0e184e2e-7440-4c7e-865f-2abe4746ed37
  spec:
    sourcePod: network-check-source-685456655f-nzhrn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:20:39Z"
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.99315ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:41:39Z"
    - latency: 2.10837ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:40:39Z"
    - latency: 2.397179ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:39:39Z"
    - latency: 2.078124ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:38:39Z"
    - latency: 2.448357ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:37:39Z"
    - latency: 2.353103ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:36:39Z"
    - latency: 2.798398ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:35:39Z"
    - latency: 2.477471ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:34:39Z"
    - latency: 2.492385ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:33:39Z"
    - latency: 2.435827ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:32:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-04T22:13:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.ec2.internal
      uid: ece25633-a4dd-43d1-9a6a-990700a5de3d
    resourceVersion: "55334"
    uid: e8c395db-a329-44fe-b469-f9fd420634e0
  spec:
    sourcePod: network-check-source-685456655f-nzhrn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-04T22:19:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.208407ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:43:39Z"
    - latency: 1.730565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:43:39Z"
    - latency: 999.52µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:42:39Z"
    - latency: 1.807154ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:42:39Z"
    - latency: 871.19µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:41:39Z"
    - latency: 1.974937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:41:39Z"
    - latency: 1.000351ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:40:39Z"
    - latency: 1.724636ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:40:39Z"
    - latency: 911.418µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-04T22:39:39Z"
    - latency: 2.360145ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-04T22:39:39Z"
kind: List
metadata:
  resourceVersion: ""