apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-22T16:59:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-234-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-234.ec2.internal
      uid: e6fa8542-59db-469e-ad82-e6a91092625b
    resourceVersion: "21332"
    uid: eb45bb1d-411e-495e-a782-5e45990599f7
  spec:
    sourcePod: network-check-source-757774bcb8-sp7zj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-22T17:06:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 999.954µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:34:16Z"
    - latency: 1.015617ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:33:16Z"
    - latency: 1.865052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:32:16Z"
    - latency: 1.305372ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:31:16Z"
    - latency: 894.972µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:30:16Z"
    - latency: 840.379µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:29:16Z"
    - latency: 1.083774ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:28:16Z"
    - latency: 1.363801ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:27:16Z"
    - latency: 981.833µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:26:16Z"
    - latency: 1.04585ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-22T16:59:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-234-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-234.ec2.internal
      uid: e6fa8542-59db-469e-ad82-e6a91092625b
    resourceVersion: "19833"
    uid: 8b781c2d-e82a-4d84-bfc9-b18e7463ceab
  spec:
    sourcePod: network-check-source-757774bcb8-sp7zj
    targetEndpoint: ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-22T17:05:16Z"
      message: 'load-balancer-api-external: tcp connection to ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 14.291028ms
      message: 'load-balancer-api-external: tcp connection to ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:29:16Z"
    - latency: 9.19379ms
      message: 'load-balancer-api-external: resolved host name ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:29:16Z"
    - latency: 15.075527ms
      message: 'load-balancer-api-external: tcp connection to ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:28:16Z"
    - latency: 7.570811ms
      message: 'load-balancer-api-external: resolved host name ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:28:16Z"
    - latency: 15.866138ms
      message: 'load-balancer-api-external: tcp connection to ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:27:16Z"
    - latency: 8.203467ms
      message: 'load-balancer-api-external: resolved host name ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:27:16Z"
    - latency: 18.663724ms
      message: 'load-balancer-api-external: tcp connection to ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:26:16Z"
    - latency: 8.603193ms
      message: 'load-balancer-api-external: resolved host name ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:26:16Z"
    - latency: 17.266156ms
      message: 'load-balancer-api-external: tcp connection to ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:25:16Z"
    - latency: 8.968179ms
      message: 'load-balancer-api-external: resolved host name ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-22T16:59:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-234-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-234.ec2.internal
      uid: e6fa8542-59db-469e-ad82-e6a91092625b
    resourceVersion: "19834"
    uid: 43645c09-b6db-4646-8089-12ec8f99daa2
  spec:
    sourcePod: network-check-source-757774bcb8-sp7zj
    targetEndpoint: ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-22T17:05:16Z"
      message: 'load-balancer-api-internal: tcp connection to ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 14.274027ms
      message: 'load-balancer-api-internal: tcp connection to ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:29:16Z"
    - latency: 9.330142ms
      message: 'load-balancer-api-internal: resolved host name ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:29:16Z"
    - latency: 15.10464ms
      message: 'load-balancer-api-internal: tcp connection to ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:28:16Z"
    - latency: 7.546187ms
      message: 'load-balancer-api-internal: resolved host name ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:28:16Z"
    - latency: 14.857029ms
      message: 'load-balancer-api-internal: tcp connection to ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:27:16Z"
    - latency: 8.172523ms
      message: 'load-balancer-api-internal: resolved host name ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:27:16Z"
    - latency: 18.674257ms
      message: 'load-balancer-api-internal: tcp connection to ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:26:16Z"
    - latency: 8.561063ms
      message: 'load-balancer-api-internal: resolved host name ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:26:16Z"
    - latency: 16.441821ms
      message: 'load-balancer-api-internal: tcp connection to ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:25:16Z"
    - latency: 9.064875ms
      message: 'load-balancer-api-internal: resolved host name ae29190c5bc7746cb8514735bcacd07d-4004b3586869de14.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-22T16:59:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-234-to-network-check-target-ip-10-0-133-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-234.ec2.internal
      uid: e6fa8542-59db-469e-ad82-e6a91092625b
    resourceVersion: "21330"
    uid: 36697c36-ca8a-420b-9037-b43d77e783eb
  spec:
    sourcePod: network-check-source-757774bcb8-sp7zj
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-22T17:06:16Z"
      message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.285325ms
      message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:34:16Z"
    - latency: 2.255857ms
      message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:33:16Z"
    - latency: 2.610017ms
      message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:32:16Z"
    - latency: 2.313533ms
      message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:31:16Z"
    - latency: 2.171843ms
      message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:30:16Z"
    - latency: 2.243576ms
      message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:29:16Z"
    - latency: 2.427245ms
      message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:28:16Z"
    - latency: 2.442265ms
      message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:27:16Z"
    - latency: 2.493064ms
      message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:26:16Z"
    - latency: 2.294421ms
      message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-22T16:59:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-234-to-network-check-target-ip-10-0-135-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-234.ec2.internal
      uid: e6fa8542-59db-469e-ad82-e6a91092625b
    resourceVersion: "21331"
    uid: 65316003-b098-4ada-98df-9061e437a319
  spec:
    sourcePod: network-check-source-757774bcb8-sp7zj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-22T17:06:16Z"
      message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.250073ms
      message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:34:16Z"
    - latency: 2.219879ms
      message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:33:16Z"
    - latency: 2.771013ms
      message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:32:16Z"
    - latency: 2.176377ms
      message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:31:16Z"
    - latency: 2.237266ms
      message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:30:16Z"
    - latency: 2.404666ms
      message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:29:16Z"
    - latency: 2.200671ms
      message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:28:16Z"
    - latency: 2.322115ms
      message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:27:16Z"
    - latency: 2.275041ms
      message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:26:16Z"
    - latency: 2.150309ms
      message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-22T16:59:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-234-to-network-check-target-ip-10-0-135-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-234.ec2.internal
      uid: e6fa8542-59db-469e-ad82-e6a91092625b
    resourceVersion: "21329"
    uid: a6519e03-9094-4298-81b4-c8d1f5ea518a
  spec:
    sourcePod: network-check-source-757774bcb8-sp7zj
    targetEndpoint: 10.132.0.7:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-22T17:06:16Z"
      message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.132.0.7:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.202668ms
      message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.132.0.7:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:34:16Z"
    - latency: 1.18ms
      message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.132.0.7:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:33:16Z"
    - latency: 728.206µs
      message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.132.0.7:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:32:16Z"
    - latency: 814.41µs
      message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.132.0.7:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:31:16Z"
    - latency: 782.521µs
      message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.132.0.7:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:30:16Z"
    - latency: 784.004µs
      message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.132.0.7:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:29:16Z"
    - latency: 779.958µs
      message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.132.0.7:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:28:16Z"
    - latency: 1.005826ms
      message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.132.0.7:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:27:16Z"
    - latency: 983.949µs
      message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.132.0.7:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:26:16Z"
    - latency: 1.568456ms
      message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.132.0.7:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-22T16:59:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-234-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-234.ec2.internal
      uid: e6fa8542-59db-469e-ad82-e6a91092625b
    resourceVersion: "19832"
    uid: 20950491-1b19-457f-a7dd-d67c0653046a
  spec:
    sourcePod: network-check-source-757774bcb8-sp7zj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-22T17:05:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 864.048µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:29:16Z"
    - latency: 1.874996ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:29:16Z"
    - latency: 1.037588ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:28:16Z"
    - latency: 1.729406ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:28:16Z"
    - latency: 966.987µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:27:16Z"
    - latency: 1.907241ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:27:16Z"
    - latency: 868.491µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:26:16Z"
    - latency: 1.898324ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:26:16Z"
    - latency: 1.007076ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-22T17:25:16Z"
    - latency: 1.875642ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-22T17:25:16Z"
kind: List
metadata:
  resourceVersion: ""