apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:13:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: 40f81ffb-c325-4e0d-8f70-f0677edc2687
    resourceVersion: "53630"
    uid: 1c5b5451-c2c5-4942-a333-8abde18d1cd9
  spec:
    sourcePod: network-check-source-685456655f-t94zs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:20:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 836.416µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:41:46Z"
    - latency: 907.083µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:40:46Z"
    - latency: 821.636µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:39:46Z"
    - latency: 828.736µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:38:46Z"
    - latency: 1.048626ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:37:46Z"
    - latency: 1.159488ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:36:46Z"
    - latency: 785.784µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:35:46Z"
    - latency: 985.12µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:34:46Z"
    - latency: 1.041191ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:33:46Z"
    - latency: 974.463µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:32:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:13:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: 40f81ffb-c325-4e0d-8f70-f0677edc2687
    resourceVersion: "55030"
    uid: cdbb7ed4-b713-459c-b4f8-a98948542ffb
  spec:
    sourcePod: network-check-source-685456655f-t94zs
    targetEndpoint: a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:19:46Z"
      message: 'load-balancer-api-external: tcp connection to a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.734155ms
      message: 'load-balancer-api-external: tcp connection to a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:43:46Z"
    - latency: 8.604831ms
      message: 'load-balancer-api-external: resolved host name a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:43:46Z"
    - latency: 5.187843ms
      message: 'load-balancer-api-external: tcp connection to a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:42:46Z"
    - latency: 6.505302ms
      message: 'load-balancer-api-external: resolved host name a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:42:46Z"
    - latency: 5.087719ms
      message: 'load-balancer-api-external: tcp connection to a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:41:46Z"
    - latency: 8.174493ms
      message: 'load-balancer-api-external: resolved host name a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:41:46Z"
    - latency: 6.971254ms
      message: 'load-balancer-api-external: tcp connection to a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:40:46Z"
    - latency: 6.609244ms
      message: 'load-balancer-api-external: resolved host name a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:40:46Z"
    - latency: 5.489839ms
      message: 'load-balancer-api-external: tcp connection to a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:39:46Z"
    - latency: 7.62595ms
      message: 'load-balancer-api-external: resolved host name a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:39:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:13:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: 40f81ffb-c325-4e0d-8f70-f0677edc2687
    resourceVersion: "55031"
    uid: 1bc26842-feae-4a19-9b42-889699fe0fca
  spec:
    sourcePod: network-check-source-685456655f-t94zs
    targetEndpoint: a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:19:46Z"
      message: 'load-balancer-api-internal: tcp connection to a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.781292ms
      message: 'load-balancer-api-internal: tcp connection to a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:43:46Z"
    - latency: 8.690612ms
      message: 'load-balancer-api-internal: resolved host name a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:43:46Z"
    - latency: 5.219332ms
      message: 'load-balancer-api-internal: tcp connection to a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:42:46Z"
    - latency: 6.590684ms
      message: 'load-balancer-api-internal: resolved host name a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:42:46Z"
    - latency: 4.932543ms
      message: 'load-balancer-api-internal: tcp connection to a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:41:46Z"
    - latency: 8.250205ms
      message: 'load-balancer-api-internal: resolved host name a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:41:46Z"
    - latency: 12.867173ms
      message: 'load-balancer-api-internal: tcp connection to a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:40:46Z"
    - latency: 6.590084ms
      message: 'load-balancer-api-internal: resolved host name a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:40:46Z"
    - latency: 5.479353ms
      message: 'load-balancer-api-internal: tcp connection to a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:39:46Z"
    - latency: 7.705322ms
      message: 'load-balancer-api-internal: resolved host name a17d847ba999f4d2aa53d5ca129d5645-0377d80e7101ede3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:39:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:13:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-network-check-target-ip-10-0-139-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: 40f81ffb-c325-4e0d-8f70-f0677edc2687
    resourceVersion: "53628"
    uid: 190dcb8e-b587-4b4c-bf80-a55cf75d9f2b
  spec:
    sourcePod: network-check-source-685456655f-t94zs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:20:46Z"
      message: 'network-check-target-ip-10-0-139-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.820053ms
      message: 'network-check-target-ip-10-0-139-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:41:46Z"
    - latency: 1.921104ms
      message: 'network-check-target-ip-10-0-139-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:40:46Z"
    - latency: 1.955877ms
      message: 'network-check-target-ip-10-0-139-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:39:46Z"
    - latency: 1.563957ms
      message: 'network-check-target-ip-10-0-139-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:38:46Z"
    - latency: 1.760113ms
      message: 'network-check-target-ip-10-0-139-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:37:46Z"
    - latency: 1.861912ms
      message: 'network-check-target-ip-10-0-139-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:36:46Z"
    - latency: 1.680332ms
      message: 'network-check-target-ip-10-0-139-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:35:46Z"
    - latency: 1.95717ms
      message: 'network-check-target-ip-10-0-139-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:34:46Z"
    - latency: 2.140473ms
      message: 'network-check-target-ip-10-0-139-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:33:46Z"
    - latency: 1.849711ms
      message: 'network-check-target-ip-10-0-139-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:32:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:13:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-network-check-target-ip-10-0-140-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: 40f81ffb-c325-4e0d-8f70-f0677edc2687
    resourceVersion: "53627"
    uid: 42d06a6e-f4e5-47d3-8b3b-0fddce0e3e93
  spec:
    sourcePod: network-check-source-685456655f-t94zs
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:20:46Z"
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 809.226µs
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:41:46Z"
    - latency: 1.066776ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:40:46Z"
    - latency: 1.439584ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:39:46Z"
    - latency: 983.148µs
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:38:46Z"
    - latency: 1.008457ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:37:46Z"
    - latency: 1.504099ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:36:46Z"
    - latency: 1.091197ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:35:46Z"
    - latency: 1.308828ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:34:46Z"
    - latency: 1.004747ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:33:46Z"
    - latency: 1.026495ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:32:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:13:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-network-check-target-ip-10-0-142-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: 40f81ffb-c325-4e0d-8f70-f0677edc2687
    resourceVersion: "53629"
    uid: b7f01fcc-baa8-4a6d-9b30-d1d3853646f6
  spec:
    sourcePod: network-check-source-685456655f-t94zs
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:20:46Z"
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.124726ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:41:46Z"
    - latency: 2.226349ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:40:46Z"
    - latency: 2.189861ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:39:46Z"
    - latency: 2.245149ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:38:46Z"
    - latency: 2.11212ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:37:46Z"
    - latency: 2.201995ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:36:46Z"
    - latency: 2.032529ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:35:46Z"
    - latency: 2.241519ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:34:46Z"
    - latency: 2.104947ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:33:46Z"
    - latency: 2.205705ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:32:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:13:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: 40f81ffb-c325-4e0d-8f70-f0677edc2687
    resourceVersion: "55029"
    uid: 016ea2dc-54e3-471f-a14a-caef59cf352a
  spec:
    sourcePod: network-check-source-685456655f-t94zs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:19:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 858.32µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:43:46Z"
    - latency: 1.809458ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:43:46Z"
    - latency: 923.053µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:42:46Z"
    - latency: 2.137025ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:42:46Z"
    - latency: 737.092µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:41:46Z"
    - latency: 2.280858ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:41:46Z"
    - latency: 1.045653ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:40:46Z"
    - latency: 1.91998ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:40:46Z"
    - latency: 827.809µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:39:46Z"
    - latency: 1.972946ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:39:46Z"
kind: List
metadata:
  resourceVersion: ""