apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-97-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-97.ec2.internal
      uid: 6eadce4a-66ea-4934-8021-2db705e36b8e
    resourceVersion: "32071"
    uid: df70239b-baea-467e-b853-ef20192be476
  spec:
    sourcePod: network-check-source-869dcfcdcd-tbpsz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:29:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.565559ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:04:44Z"
    - latency: 969.975µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:03:44Z"
    - latency: 1.065901ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:02:44Z"
    - latency: 1.193273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:01:44Z"
    - latency: 1.077919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:44Z"
    - latency: 911.07µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:59:44Z"
    - latency: 936.753µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:58:44Z"
    - latency: 849.31µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:57:44Z"
    - latency: 1.044338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:56:44Z"
    - latency: 1.5058ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:55:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-97-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-97.ec2.internal
      uid: 6eadce4a-66ea-4934-8021-2db705e36b8e
    resourceVersion: "32072"
    uid: 2582ddeb-eb7a-457f-9b43-099ecb1aa99f
  spec:
    sourcePod: network-check-source-869dcfcdcd-tbpsz
    targetEndpoint: aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:28:44Z"
      message: 'load-balancer-api-external: tcp connection to aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.717572ms
      message: 'load-balancer-api-external: tcp connection to aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:04:44Z"
    - latency: 9.066414ms
      message: 'load-balancer-api-external: resolved host name aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:04:44Z"
    - latency: 8.404656ms
      message: 'load-balancer-api-external: tcp connection to aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:03:44Z"
    - latency: 8.355384ms
      message: 'load-balancer-api-external: resolved host name aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:03:44Z"
    - latency: 4.434648ms
      message: 'load-balancer-api-external: tcp connection to aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:02:44Z"
    - latency: 7.981852ms
      message: 'load-balancer-api-external: resolved host name aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:02:44Z"
    - latency: 3.827589ms
      message: 'load-balancer-api-external: tcp connection to aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:01:44Z"
    - latency: 8.925733ms
      message: 'load-balancer-api-external: resolved host name aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:01:44Z"
    - latency: 4.413843ms
      message: 'load-balancer-api-external: tcp connection to aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:44Z"
    - latency: 9.110321ms
      message: 'load-balancer-api-external: resolved host name aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:00:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-97-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-97.ec2.internal
      uid: 6eadce4a-66ea-4934-8021-2db705e36b8e
    resourceVersion: "32073"
    uid: e4505adc-a89e-4a76-b4e3-362d36360a9e
  spec:
    sourcePod: network-check-source-869dcfcdcd-tbpsz
    targetEndpoint: aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:28:44Z"
      message: 'load-balancer-api-internal: tcp connection to aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.68974ms
      message: 'load-balancer-api-internal: tcp connection to aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:04:44Z"
    - latency: 9.159239ms
      message: 'load-balancer-api-internal: resolved host name aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:04:44Z"
    - latency: 8.451522ms
      message: 'load-balancer-api-internal: tcp connection to aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:03:44Z"
    - latency: 8.384865ms
      message: 'load-balancer-api-internal: resolved host name aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:03:44Z"
    - latency: 3.814529ms
      message: 'load-balancer-api-internal: tcp connection to aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:02:44Z"
    - latency: 7.99792ms
      message: 'load-balancer-api-internal: resolved host name aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:02:44Z"
    - latency: 5.163416ms
      message: 'load-balancer-api-internal: tcp connection to aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:01:44Z"
    - latency: 8.952041ms
      message: 'load-balancer-api-internal: resolved host name aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:01:44Z"
    - latency: 4.396944ms
      message: 'load-balancer-api-internal: tcp connection to aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:44Z"
    - latency: 9.162909ms
      message: 'load-balancer-api-internal: resolved host name aefae840c03ea4dd5bb965c18706fbba-4fc83b2b1d262dff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:00:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-97-to-network-check-target-ip-10-0-128-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-97.ec2.internal
      uid: 6eadce4a-66ea-4934-8021-2db705e36b8e
    resourceVersion: "32070"
    uid: 76107a54-e21d-45a2-ba0f-36f01517db0d
  spec:
    sourcePod: network-check-source-869dcfcdcd-tbpsz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:29:44Z"
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.589123ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:04:44Z"
    - latency: 2.350645ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:03:44Z"
    - latency: 2.116568ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:02:44Z"
    - latency: 2.21626ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:01:44Z"
    - latency: 2.323962ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:44Z"
    - latency: 1.963581ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:59:44Z"
    - latency: 1.992551ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:58:44Z"
    - latency: 2.009445ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:57:44Z"
    - latency: 2.28203ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:56:44Z"
    - latency: 2.200969ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:55:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-97-to-network-check-target-ip-10-0-128-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-97.ec2.internal
      uid: 6eadce4a-66ea-4934-8021-2db705e36b8e
    resourceVersion: "32068"
    uid: 5b0af6fc-58a7-4e14-a1e7-b18fa847ca3d
  spec:
    sourcePod: network-check-source-869dcfcdcd-tbpsz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:29:44Z"
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.13145ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:04:44Z"
    - latency: 2.868635ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:03:44Z"
    - latency: 2.560688ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:02:44Z"
    - latency: 2.543751ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:01:44Z"
    - latency: 2.176536ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:44Z"
    - latency: 2.200273ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:59:44Z"
    - latency: 2.077954ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:58:44Z"
    - latency: 2.28797ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:57:44Z"
    - latency: 2.263808ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:56:44Z"
    - latency: 2.091456ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:55:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-97-to-network-check-target-ip-10-0-134-97
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-97.ec2.internal
      uid: 6eadce4a-66ea-4934-8021-2db705e36b8e
    resourceVersion: "32067"
    uid: d5ae36ed-2dde-4a21-b40e-991d7ed2456c
  spec:
    sourcePod: network-check-source-869dcfcdcd-tbpsz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:29:44Z"
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.211µs
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:04:44Z"
    - latency: 950.829µs
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:03:44Z"
    - latency: 1.202074ms
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:02:44Z"
    - latency: 1.608807ms
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:01:44Z"
    - latency: 871.608µs
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:44Z"
    - latency: 866.534µs
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:59:44Z"
    - latency: 837.734µs
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:58:44Z"
    - latency: 898.361µs
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:57:44Z"
    - latency: 984.264µs
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:56:44Z"
    - latency: 892.935µs
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:55:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:22:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-97-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-97.ec2.internal
      uid: 6eadce4a-66ea-4934-8021-2db705e36b8e
    resourceVersion: "32069"
    uid: bb9e902b-04bb-4e6f-9a0e-d304c4ed46b2
  spec:
    sourcePod: network-check-source-869dcfcdcd-tbpsz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:28:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 992.06µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:04:44Z"
    - latency: 1.663152ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:04:44Z"
    - latency: 1.228761ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:03:44Z"
    - latency: 1.679487ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:03:44Z"
    - latency: 765.843µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:02:44Z"
    - latency: 1.652799ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:02:44Z"
    - latency: 892.868µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:01:44Z"
    - latency: 2.182301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:01:44Z"
    - latency: 806.802µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:44Z"
    - latency: 1.83622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:00:44Z"
kind: List
metadata:
  resourceVersion: ""