apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:21:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: 2aec4aff-47f6-4016-bf56-709af5b51db0
    resourceVersion: "70613"
    uid: 36b8822f-4645-4a34-9120-45280eb35fed
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvrx6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:28:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.45979ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:10:11Z"
    - latency: 1.562052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:09:11Z"
    - latency: 1.465553ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:08:11Z"
    - latency: 1.001948ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:07:11Z"
    - latency: 918.12µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:06:11Z"
    - latency: 1.47629ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:05:11Z"
    - latency: 1.081603ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:04:11Z"
    - latency: 1.171213ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:03:11Z"
    - latency: 1.334011ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:02:11Z"
    - latency: 1.271554ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:01:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:21:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: 2aec4aff-47f6-4016-bf56-709af5b51db0
    resourceVersion: "69474"
    uid: 0df6cb3a-6e7b-49c4-8fe9-05d94ce706e3
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvrx6
    targetEndpoint: a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:27:11Z"
      message: 'load-balancer-api-external: tcp connection to a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.113076ms
      message: 'load-balancer-api-external: tcp connection to a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:09:11Z"
    - latency: 7.443729ms
      message: 'load-balancer-api-external: resolved host name a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:09:11Z"
    - latency: 5.090597ms
      message: 'load-balancer-api-external: tcp connection to a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:08:11Z"
    - latency: 6.998669ms
      message: 'load-balancer-api-external: resolved host name a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:08:11Z"
    - latency: 5.2054ms
      message: 'load-balancer-api-external: tcp connection to a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:07:11Z"
    - latency: 7.077647ms
      message: 'load-balancer-api-external: resolved host name a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:07:11Z"
    - latency: 5.853889ms
      message: 'load-balancer-api-external: tcp connection to a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:06:11Z"
    - latency: 7.171665ms
      message: 'load-balancer-api-external: resolved host name a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:06:11Z"
    - latency: 6.098129ms
      message: 'load-balancer-api-external: tcp connection to a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:05:11Z"
    - latency: 6.733926ms
      message: 'load-balancer-api-external: resolved host name a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:05:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:21:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: 2aec4aff-47f6-4016-bf56-709af5b51db0
    resourceVersion: "69473"
    uid: 2a27d971-4a18-4482-962d-7a7579eb5579
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvrx6
    targetEndpoint: a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:27:11Z"
      message: 'load-balancer-api-internal: tcp connection to a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.102884ms
      message: 'load-balancer-api-internal: tcp connection to a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:09:11Z"
    - latency: 7.525321ms
      message: 'load-balancer-api-internal: resolved host name a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:09:11Z"
    - latency: 5.186193ms
      message: 'load-balancer-api-internal: tcp connection to a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:08:11Z"
    - latency: 7.107868ms
      message: 'load-balancer-api-internal: resolved host name a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:08:11Z"
    - latency: 5.220134ms
      message: 'load-balancer-api-internal: tcp connection to a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:07:11Z"
    - latency: 7.158279ms
      message: 'load-balancer-api-internal: resolved host name a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:07:11Z"
    - latency: 5.772304ms
      message: 'load-balancer-api-internal: tcp connection to a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:06:11Z"
    - latency: 7.210333ms
      message: 'load-balancer-api-internal: resolved host name a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:06:11Z"
    - latency: 5.91449ms
      message: 'load-balancer-api-internal: tcp connection to a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:05:11Z"
    - latency: 6.801014ms
      message: 'load-balancer-api-internal: resolved host name a219d4f15c93f41ca9181e317a974596-75e72b1e03299df2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:05:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:21:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-network-check-target-ip-10-0-129-103
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: 2aec4aff-47f6-4016-bf56-709af5b51db0
    resourceVersion: "70612"
    uid: 34083126-8a40-4695-a8bb-6203fbcea28a
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvrx6
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:28:11Z"
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.408853ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:10:11Z"
    - latency: 2.303093ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:09:11Z"
    - latency: 2.601097ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:08:11Z"
    - latency: 2.334004ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:07:11Z"
    - latency: 1.949789ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:06:11Z"
    - latency: 2.444473ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:05:11Z"
    - latency: 2.220484ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:04:11Z"
    - latency: 2.387082ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:03:11Z"
    - latency: 1.987383ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:02:11Z"
    - latency: 2.362441ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:01:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:21:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-network-check-target-ip-10-0-132-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: 2aec4aff-47f6-4016-bf56-709af5b51db0
    resourceVersion: "70611"
    uid: 46ea4672-0fc2-4442-a5b1-e34d7ef988f5
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvrx6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:28:11Z"
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.713069ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:10:11Z"
    - latency: 903.489µs
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:09:11Z"
    - latency: 1.628377ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:08:11Z"
    - latency: 941.06µs
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:07:11Z"
    - latency: 924.296µs
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:06:11Z"
    - latency: 898.48µs
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:05:11Z"
    - latency: 1.035133ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:04:11Z"
    - latency: 1.347478ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:03:11Z"
    - latency: 1.036842ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:02:11Z"
    - latency: 1.203743ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:01:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:21:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-network-check-target-ip-10-0-141-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: 2aec4aff-47f6-4016-bf56-709af5b51db0
    resourceVersion: "70614"
    uid: 185d6a21-0c68-4e51-8856-3bb47f06b722
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvrx6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:28:11Z"
      message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.605594ms
      message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:10:11Z"
    - latency: 2.007837ms
      message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:09:11Z"
    - latency: 2.192807ms
      message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:08:11Z"
    - latency: 2.163546ms
      message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:07:11Z"
    - latency: 1.856608ms
      message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:06:11Z"
    - latency: 2.334062ms
      message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:05:11Z"
    - latency: 2.120411ms
      message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:04:11Z"
    - latency: 2.393474ms
      message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:03:11Z"
    - latency: 2.038191ms
      message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:02:11Z"
    - latency: 2.013772ms
      message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:01:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:21:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: 2aec4aff-47f6-4016-bf56-709af5b51db0
    resourceVersion: "69472"
    uid: 5dc6d2f2-7e78-4e6e-bb38-41945ac16da7
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvrx6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:27:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.193073ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:09:11Z"
    - latency: 1.832032ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:09:11Z"
    - latency: 953.952µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:08:11Z"
    - latency: 2.182262ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:08:11Z"
    - latency: 905.228µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:07:11Z"
    - latency: 2.126479ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:07:11Z"
    - latency: 914.781µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:06:11Z"
    - latency: 2.125295ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:06:11Z"
    - latency: 1.146811ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:05:11Z"
    - latency: 2.032087ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:05:11Z"
kind: List
metadata:
  resourceVersion: ""