apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:17:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: 12d1f54d-b20e-4995-b550-5ff5f8e469f9
    resourceVersion: "48966"
    uid: 6c753238-694f-494b-804a-4c6505efe8ab
  spec:
    sourcePod: network-check-source-989f8b8dc-48jb9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:24:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.580891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:03Z"
    - latency: 1.322427ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:03Z"
    - latency: 828.704µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:50:03Z"
    - latency: 1.6098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:49:03Z"
    - latency: 1.369203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:48:03Z"
    - latency: 1.175036ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:47:03Z"
    - latency: 773.119µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:46:03Z"
    - latency: 932.722µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:45:03Z"
    - latency: 1.17317ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:44:03Z"
    - latency: 1.089755ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:43:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:17:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: 12d1f54d-b20e-4995-b550-5ff5f8e469f9
    resourceVersion: "49829"
    uid: 2b2a331e-7bb0-42c5-bd9e-e6c173f8f92d
  spec:
    sourcePod: network-check-source-989f8b8dc-48jb9
    targetEndpoint: a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:23:03Z"
      message: 'load-balancer-api-external: tcp connection to a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.840417ms
      message: 'load-balancer-api-external: tcp connection to a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:53:03Z"
    - latency: 7.339219ms
      message: 'load-balancer-api-external: resolved host name a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:53:03Z"
    - latency: 6.165345ms
      message: 'load-balancer-api-external: tcp connection to a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:03Z"
    - latency: 7.024127ms
      message: 'load-balancer-api-external: resolved host name a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:52:03Z"
    - latency: 3.816069ms
      message: 'load-balancer-api-external: tcp connection to a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:03Z"
    - latency: 7.037933ms
      message: 'load-balancer-api-external: resolved host name a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:51:03Z"
    - latency: 3.39698ms
      message: 'load-balancer-api-external: tcp connection to a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:50:03Z"
    - latency: 5.882158ms
      message: 'load-balancer-api-external: resolved host name a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:50:03Z"
    - latency: 5.362056ms
      message: 'load-balancer-api-external: tcp connection to a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:49:03Z"
    - latency: 7.203836ms
      message: 'load-balancer-api-external: resolved host name a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:49:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:17:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: 12d1f54d-b20e-4995-b550-5ff5f8e469f9
    resourceVersion: "49828"
    uid: 6db6364b-7287-46a5-848d-3f3f685a1056
  spec:
    sourcePod: network-check-source-989f8b8dc-48jb9
    targetEndpoint: a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:23:03Z"
      message: 'load-balancer-api-internal: tcp connection to a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.244747ms
      message: 'load-balancer-api-internal: tcp connection to a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:53:03Z"
    - latency: 7.306651ms
      message: 'load-balancer-api-internal: resolved host name a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:53:03Z"
    - latency: 6.031247ms
      message: 'load-balancer-api-internal: tcp connection to a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:03Z"
    - latency: 6.957543ms
      message: 'load-balancer-api-internal: resolved host name a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:52:03Z"
    - latency: 3.808965ms
      message: 'load-balancer-api-internal: tcp connection to a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:03Z"
    - latency: 7.065208ms
      message: 'load-balancer-api-internal: resolved host name a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:51:03Z"
    - latency: 3.386139ms
      message: 'load-balancer-api-internal: tcp connection to a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:50:03Z"
    - latency: 5.819946ms
      message: 'load-balancer-api-internal: resolved host name a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:50:03Z"
    - latency: 5.229189ms
      message: 'load-balancer-api-internal: tcp connection to a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:49:03Z"
    - latency: 7.245151ms
      message: 'load-balancer-api-internal: resolved host name a50993cfd0d46437baed33ff84848e2e-4367b8f282d02a4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:49:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:17:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-network-check-target-ip-10-0-128-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: 12d1f54d-b20e-4995-b550-5ff5f8e469f9
    resourceVersion: "48964"
    uid: d3522b8d-8fc1-4c92-9cb5-2c3f08c7695b
  spec:
    sourcePod: network-check-source-989f8b8dc-48jb9
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:24:03Z"
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 819.85µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:03Z"
    - latency: 753.268µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:03Z"
    - latency: 1.412806ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:50:03Z"
    - latency: 828.404µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:49:03Z"
    - latency: 777.954µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:48:03Z"
    - latency: 1.452566ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:47:03Z"
    - latency: 776.481µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:46:03Z"
    - latency: 874.641µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:45:03Z"
    - latency: 833.292µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:44:03Z"
    - latency: 936.211µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:43:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:17:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-network-check-target-ip-10-0-136-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: 12d1f54d-b20e-4995-b550-5ff5f8e469f9
    resourceVersion: "48963"
    uid: 6535bb71-07b6-4f87-aed1-d148ef6579be
  spec:
    sourcePod: network-check-source-989f8b8dc-48jb9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:24:03Z"
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.190489ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:03Z"
    - latency: 2.223968ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:03Z"
    - latency: 2.342482ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:50:03Z"
    - latency: 2.085011ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:49:03Z"
    - latency: 2.68198ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:48:03Z"
    - latency: 2.129473ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:47:03Z"
    - latency: 2.2178ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:46:03Z"
    - latency: 1.967296ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:45:03Z"
    - latency: 2.132333ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:44:03Z"
    - latency: 2.223947ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:43:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:17:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-network-check-target-ip-10-0-143-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: 12d1f54d-b20e-4995-b550-5ff5f8e469f9
    resourceVersion: "48965"
    uid: 9cd390fa-8c8b-4751-a4bc-a92b08449923
  spec:
    sourcePod: network-check-source-989f8b8dc-48jb9
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:24:03Z"
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.223193ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:03Z"
    - latency: 2.178282ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:03Z"
    - latency: 2.818882ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:50:03Z"
    - latency: 2.392135ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:49:03Z"
    - latency: 2.252626ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:48:03Z"
    - latency: 2.29854ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:47:03Z"
    - latency: 2.063654ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:46:03Z"
    - latency: 2.368005ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:45:03Z"
    - latency: 2.287258ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:44:03Z"
    - latency: 2.645074ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:43:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:17:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: 12d1f54d-b20e-4995-b550-5ff5f8e469f9
    resourceVersion: "49827"
    uid: 15b79bb3-cd91-4662-9842-eeb0368c5d34
  spec:
    sourcePod: network-check-source-989f8b8dc-48jb9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:23:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.254828ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:53:03Z"
    - latency: 1.786128ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:53:03Z"
    - latency: 916.746µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:03Z"
    - latency: 1.874147ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:52:03Z"
    - latency: 1.254764ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:03Z"
    - latency: 1.815132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:51:03Z"
    - latency: 1.149214ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:50:03Z"
    - latency: 1.572417ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:50:03Z"
    - latency: 834.72µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:49:03Z"
    - latency: 2.336297ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:49:03Z"
kind: List
metadata:
  resourceVersion: ""