apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-172-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-172.ec2.internal
      uid: 65411579-452b-42fc-9f23-03d030477d19
    resourceVersion: "61203"
    uid: 0531d3f8-1277-436f-b366-aab7e9f02b14
  spec:
    sourcePod: network-check-source-869dcfcdcd-swtn2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:16:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.268745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:51:53Z"
    - latency: 907.004µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:50:53Z"
    - latency: 1.458533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:49:53Z"
    - latency: 1.121705ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:48:53Z"
    - latency: 1.513071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:47:53Z"
    - latency: 1.434314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:46:53Z"
    - latency: 1.000668ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:45:53Z"
    - latency: 877.862µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:44:53Z"
    - latency: 1.077843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:43:53Z"
    - latency: 1.068538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:42:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-172-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-172.ec2.internal
      uid: 65411579-452b-42fc-9f23-03d030477d19
    resourceVersion: "61204"
    uid: e01a861c-bec8-42bd-b839-819e2b43d15b
  spec:
    sourcePod: network-check-source-869dcfcdcd-swtn2
    targetEndpoint: ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:15:53Z"
      message: 'load-balancer-api-external: tcp connection to ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.147643ms
      message: 'load-balancer-api-external: tcp connection to ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:51:53Z"
    - latency: 6.824466ms
      message: 'load-balancer-api-external: resolved host name ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:51:53Z"
    - latency: 4.165183ms
      message: 'load-balancer-api-external: tcp connection to ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:50:53Z"
    - latency: 7.068333ms
      message: 'load-balancer-api-external: resolved host name ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:50:53Z"
    - latency: 5.4539ms
      message: 'load-balancer-api-external: tcp connection to ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:49:53Z"
    - latency: 6.732125ms
      message: 'load-balancer-api-external: resolved host name ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:49:53Z"
    - latency: 4.450232ms
      message: 'load-balancer-api-external: tcp connection to ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:48:53Z"
    - latency: 6.795163ms
      message: 'load-balancer-api-external: resolved host name ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:48:53Z"
    - latency: 5.477886ms
      message: 'load-balancer-api-external: tcp connection to ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:47:53Z"
    - latency: 7.110758ms
      message: 'load-balancer-api-external: resolved host name ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:47:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-172-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-172.ec2.internal
      uid: 65411579-452b-42fc-9f23-03d030477d19
    resourceVersion: "61205"
    uid: 55a99ce0-1221-4be5-a13a-c2295c4fd7b1
  spec:
    sourcePod: network-check-source-869dcfcdcd-swtn2
    targetEndpoint: ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:15:53Z"
      message: 'load-balancer-api-internal: tcp connection to ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.282179ms
      message: 'load-balancer-api-internal: tcp connection to ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:51:53Z"
    - latency: 6.850107ms
      message: 'load-balancer-api-internal: resolved host name ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:51:53Z"
    - latency: 6.879238ms
      message: 'load-balancer-api-internal: tcp connection to ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:50:53Z"
    - latency: 7.106548ms
      message: 'load-balancer-api-internal: resolved host name ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:50:53Z"
    - latency: 4.491147ms
      message: 'load-balancer-api-internal: tcp connection to ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:49:53Z"
    - latency: 6.756059ms
      message: 'load-balancer-api-internal: resolved host name ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:49:53Z"
    - latency: 3.675404ms
      message: 'load-balancer-api-internal: tcp connection to ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:48:53Z"
    - latency: 6.862087ms
      message: 'load-balancer-api-internal: resolved host name ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:48:53Z"
    - latency: 5.672574ms
      message: 'load-balancer-api-internal: tcp connection to ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:47:53Z"
    - latency: 7.178477ms
      message: 'load-balancer-api-internal: resolved host name ab3d44176f38a4a9fbac92743b69b2d9-b4e93a751f924083.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:47:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-172-to-network-check-target-ip-10-0-128-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-172.ec2.internal
      uid: 65411579-452b-42fc-9f23-03d030477d19
    resourceVersion: "61201"
    uid: fa9a7002-a9e5-4f37-b57e-e0b095ed2305
  spec:
    sourcePod: network-check-source-869dcfcdcd-swtn2
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:16:53Z"
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.320755ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:51:53Z"
    - latency: 2.460184ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:50:53Z"
    - latency: 2.604399ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:49:53Z"
    - latency: 2.585202ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:48:53Z"
    - latency: 2.395456ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:47:53Z"
    - latency: 2.123836ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:46:53Z"
    - latency: 2.502184ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:45:53Z"
    - latency: 1.909429ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:44:53Z"
    - latency: 1.915024ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:43:53Z"
    - latency: 2.198149ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:42:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-172-to-network-check-target-ip-10-0-135-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-172.ec2.internal
      uid: 65411579-452b-42fc-9f23-03d030477d19
    resourceVersion: "61199"
    uid: ab2ef814-5298-47c3-bfb7-df37a446512b
  spec:
    sourcePod: network-check-source-869dcfcdcd-swtn2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:16:53Z"
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.262689ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:51:53Z"
    - latency: 1.448544ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:50:53Z"
    - latency: 811.566µs
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:49:53Z"
    - latency: 1.333039ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:48:53Z"
    - latency: 1.168613ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:47:53Z"
    - latency: 868.008µs
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:46:53Z"
    - latency: 1.021997ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:45:53Z"
    - latency: 771.314µs
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:44:53Z"
    - latency: 906.234µs
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:43:53Z"
    - latency: 903.575µs
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:42:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-172-to-network-check-target-ip-10-0-137-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-172.ec2.internal
      uid: 65411579-452b-42fc-9f23-03d030477d19
    resourceVersion: "61202"
    uid: 611b7008-1b0c-4aa5-88fa-97fc825013ab
  spec:
    sourcePod: network-check-source-869dcfcdcd-swtn2
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:16:53Z"
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.352648ms
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:51:53Z"
    - latency: 2.623821ms
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:50:53Z"
    - latency: 2.469598ms
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:49:53Z"
    - latency: 2.169812ms
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:48:53Z"
    - latency: 2.428897ms
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:47:53Z"
    - latency: 2.579703ms
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:46:53Z"
    - latency: 2.603444ms
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:45:53Z"
    - latency: 2.165464ms
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:44:53Z"
    - latency: 2.395301ms
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:43:53Z"
    - latency: 2.63716ms
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:42:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-172-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-172.ec2.internal
      uid: 65411579-452b-42fc-9f23-03d030477d19
    resourceVersion: "61200"
    uid: 497ad994-3fee-4001-a706-373e7dafbe8f
  spec:
    sourcePod: network-check-source-869dcfcdcd-swtn2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:15:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 902.12µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:51:53Z"
    - latency: 2.010218ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:51:53Z"
    - latency: 921.602µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:50:53Z"
    - latency: 1.86074ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:50:53Z"
    - latency: 863.437µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:49:53Z"
    - latency: 1.762364ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:49:53Z"
    - latency: 1.036998ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:48:53Z"
    - latency: 2.077025ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:48:53Z"
    - latency: 1.392065ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:47:53Z"
    - latency: 2.047125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:47:53Z"
kind: List
metadata:
  resourceVersion: ""