apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T13:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-252-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-252.ec2.internal
      uid: 53e029c8-472c-4920-8793-3bca4787050e
    resourceVersion: "70941"
    uid: 2998274c-b214-4301-ad64-fd1ca7703383
  spec:
    sourcePod: network-check-source-6f8b768455-xwgbl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T13:49:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.009607ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:31:50Z"
    - latency: 998.577µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:30:50Z"
    - latency: 1.162366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:29:50Z"
    - latency: 1.217609ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:28:50Z"
    - latency: 1.041047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:27:50Z"
    - latency: 975.688µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:26:50Z"
    - latency: 847.651µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:25:50Z"
    - latency: 1.601011ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:24:50Z"
    - latency: 1.22043ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:23:50Z"
    - latency: 1.547719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:22:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T13:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-252-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-252.ec2.internal
      uid: 53e029c8-472c-4920-8793-3bca4787050e
    resourceVersion: "70324"
    uid: 4249afca-db85-4a2c-905c-a148c5111de3
  spec:
    sourcePod: network-check-source-6f8b768455-xwgbl
    targetEndpoint: ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T13:48:50Z"
      message: 'load-balancer-api-external: tcp connection to ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.140878ms
      message: 'load-balancer-api-external: tcp connection to ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:30:50Z"
    - latency: 6.83977ms
      message: 'load-balancer-api-external: resolved host name ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:30:50Z"
    - latency: 4.45825ms
      message: 'load-balancer-api-external: tcp connection to ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:29:50Z"
    - latency: 6.685959ms
      message: 'load-balancer-api-external: resolved host name ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:29:50Z"
    - latency: 4.044305ms
      message: 'load-balancer-api-external: tcp connection to ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:28:50Z"
    - latency: 6.246004ms
      message: 'load-balancer-api-external: resolved host name ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:28:50Z"
    - latency: 4.664486ms
      message: 'load-balancer-api-external: tcp connection to ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:27:50Z"
    - latency: 6.000208ms
      message: 'load-balancer-api-external: resolved host name ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:27:50Z"
    - latency: 5.852187ms
      message: 'load-balancer-api-external: tcp connection to ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:26:50Z"
    - latency: 7.524558ms
      message: 'load-balancer-api-external: resolved host name ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:26:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T13:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-252-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-252.ec2.internal
      uid: 53e029c8-472c-4920-8793-3bca4787050e
    resourceVersion: "70323"
    uid: 33cf7c97-4db2-4c16-9b5c-eac23afedad4
  spec:
    sourcePod: network-check-source-6f8b768455-xwgbl
    targetEndpoint: ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T13:48:50Z"
      message: 'load-balancer-api-internal: tcp connection to ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.134226ms
      message: 'load-balancer-api-internal: tcp connection to ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:30:50Z"
    - latency: 6.760122ms
      message: 'load-balancer-api-internal: resolved host name ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:30:50Z"
    - latency: 6.341164ms
      message: 'load-balancer-api-internal: tcp connection to ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:29:50Z"
    - latency: 6.6237ms
      message: 'load-balancer-api-internal: resolved host name ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:29:50Z"
    - latency: 4.054356ms
      message: 'load-balancer-api-internal: tcp connection to ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:28:50Z"
    - latency: 6.156697ms
      message: 'load-balancer-api-internal: resolved host name ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:28:50Z"
    - latency: 4.628484ms
      message: 'load-balancer-api-internal: tcp connection to ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:27:50Z"
    - latency: 5.950805ms
      message: 'load-balancer-api-internal: resolved host name ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:27:50Z"
    - latency: 5.904617ms
      message: 'load-balancer-api-internal: tcp connection to ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:26:50Z"
    - latency: 7.440221ms
      message: 'load-balancer-api-internal: resolved host name ab9f78a3f639440b9a2255693869afc6-93a6808d1f3a4c54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:26:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T13:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-252-to-network-check-target-ip-10-0-128-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-252.ec2.internal
      uid: 53e029c8-472c-4920-8793-3bca4787050e
    resourceVersion: "70939"
    uid: 89f96f9c-355a-423e-98d6-442426e6a43f
  spec:
    sourcePod: network-check-source-6f8b768455-xwgbl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T13:49:50Z"
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.344752ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:31:50Z"
    - latency: 2.237014ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:30:50Z"
    - latency: 2.376745ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:29:50Z"
    - latency: 2.355269ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:28:50Z"
    - latency: 2.170805ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:27:50Z"
    - latency: 3.147583ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:26:50Z"
    - latency: 2.276009ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:25:50Z"
    - latency: 2.462899ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:24:50Z"
    - latency: 2.237268ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:23:50Z"
    - latency: 2.327268ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:22:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T13:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-252-to-network-check-target-ip-10-0-134-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-252.ec2.internal
      uid: 53e029c8-472c-4920-8793-3bca4787050e
    resourceVersion: "70940"
    uid: ba83bdda-f4ce-4cff-8d8c-ea234cea6c6e
  spec:
    sourcePod: network-check-source-6f8b768455-xwgbl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T13:49:50Z"
      message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.264279ms
      message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:31:50Z"
    - latency: 1.933492ms
      message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:30:50Z"
    - latency: 2.110394ms
      message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:29:50Z"
    - latency: 2.071206ms
      message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:28:50Z"
    - latency: 2.199537ms
      message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:27:50Z"
    - latency: 2.277849ms
      message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:26:50Z"
    - latency: 1.976523ms
      message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:25:50Z"
    - latency: 2.753871ms
      message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:24:50Z"
    - latency: 2.234475ms
      message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:23:50Z"
    - latency: 2.332183ms
      message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:22:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T13:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-252-to-network-check-target-ip-10-0-138-252
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-252.ec2.internal
      uid: 53e029c8-472c-4920-8793-3bca4787050e
    resourceVersion: "70938"
    uid: 7e41f0e5-a480-462f-be69-86eefcc08673
  spec:
    sourcePod: network-check-source-6f8b768455-xwgbl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T13:49:50Z"
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 838.273µs
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:31:50Z"
    - latency: 924.583µs
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:30:50Z"
    - latency: 984.807µs
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:29:50Z"
    - latency: 1.575028ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:28:50Z"
    - latency: 984.645µs
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:27:50Z"
    - latency: 1.014163ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:26:50Z"
    - latency: 1.118126ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:25:50Z"
    - latency: 1.943833ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:24:50Z"
    - latency: 942.209µs
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:23:50Z"
    - latency: 1.047673ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:22:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T13:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-252-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-252.ec2.internal
      uid: 53e029c8-472c-4920-8793-3bca4787050e
    resourceVersion: "70322"
    uid: 19b932ed-6b44-4caf-bbb5-417ffa88443d
  spec:
    sourcePod: network-check-source-6f8b768455-xwgbl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T13:48:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.042919ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:30:50Z"
    - latency: 1.821545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:30:50Z"
    - latency: 1.205383ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:29:50Z"
    - latency: 2.120347ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:29:50Z"
    - latency: 1.087ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:28:50Z"
    - latency: 1.817435ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:28:50Z"
    - latency: 969.871µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:27:50Z"
    - latency: 1.751811ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:27:50Z"
    - latency: 1.897051ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T14:26:50Z"
    - latency: 2.028667ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T14:26:50Z"
kind: List
metadata:
  resourceVersion: ""