apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-143-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-143.ec2.internal
      uid: f09d6f50-8bea-4ad3-8e94-e35be205fe7c
    resourceVersion: "89449"
    uid: 5f76983c-08e1-425f-9242-a3cc6ed966f9
  spec:
    sourcePod: network-check-source-6f8b768455-gpxl8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.114206ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:59:48Z"
    - latency: 940.211µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:58:48Z"
    - latency: 858.394µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:57:48Z"
    - latency: 1.177991ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:56:48Z"
    - latency: 1.058267ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:55:48Z"
    - latency: 1.113338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:54:48Z"
    - latency: 1.007031ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:53:48Z"
    - latency: 847.829µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:52:48Z"
    - latency: 1.199433ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:51:48Z"
    - latency: 944.92µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:50:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-143-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-143.ec2.internal
      uid: f09d6f50-8bea-4ad3-8e94-e35be205fe7c
    resourceVersion: "91302"
    uid: 19e596a8-dbe5-4d6d-9961-d4cdaa083c08
  spec:
    sourcePod: network-check-source-6f8b768455-gpxl8
    targetEndpoint: a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:55:48Z"
      message: 'load-balancer-api-external: tcp connection to a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.31889ms
      message: 'load-balancer-api-external: tcp connection to a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:01:48Z"
    - latency: 8.291066ms
      message: 'load-balancer-api-external: resolved host name a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:01:48Z"
    - latency: 6.722447ms
      message: 'load-balancer-api-external: tcp connection to a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:00:48Z"
    - latency: 8.069882ms
      message: 'load-balancer-api-external: resolved host name a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:00:48Z"
    - latency: 4.996525ms
      message: 'load-balancer-api-external: tcp connection to a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:59:48Z"
    - latency: 8.4237ms
      message: 'load-balancer-api-external: resolved host name a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:59:48Z"
    - latency: 4.750553ms
      message: 'load-balancer-api-external: tcp connection to a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:58:48Z"
    - latency: 7.248554ms
      message: 'load-balancer-api-external: resolved host name a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:58:48Z"
    - latency: 5.810042ms
      message: 'load-balancer-api-external: tcp connection to a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:57:48Z"
    - latency: 9.273356ms
      message: 'load-balancer-api-external: resolved host name a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:57:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-143-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-143.ec2.internal
      uid: f09d6f50-8bea-4ad3-8e94-e35be205fe7c
    resourceVersion: "91303"
    uid: 36311bfe-a39f-4ba8-942c-b4824dd54575
  spec:
    sourcePod: network-check-source-6f8b768455-gpxl8
    targetEndpoint: a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:55:48Z"
      message: 'load-balancer-api-internal: tcp connection to a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.351727ms
      message: 'load-balancer-api-internal: tcp connection to a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:01:48Z"
    - latency: 8.33901ms
      message: 'load-balancer-api-internal: resolved host name a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:01:48Z"
    - latency: 6.618495ms
      message: 'load-balancer-api-internal: tcp connection to a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:00:48Z"
    - latency: 8.095654ms
      message: 'load-balancer-api-internal: resolved host name a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:00:48Z"
    - latency: 5.037135ms
      message: 'load-balancer-api-internal: tcp connection to a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:59:48Z"
    - latency: 8.467433ms
      message: 'load-balancer-api-internal: resolved host name a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:59:48Z"
    - latency: 5.088508ms
      message: 'load-balancer-api-internal: tcp connection to a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:58:48Z"
    - latency: 7.285576ms
      message: 'load-balancer-api-internal: resolved host name a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:58:48Z"
    - latency: 5.758383ms
      message: 'load-balancer-api-internal: tcp connection to a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:57:48Z"
    - latency: 9.289565ms
      message: 'load-balancer-api-internal: resolved host name a1ccbe3732cb4480682f4764df939773-f3dbbac3d1eec288.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:57:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-143-to-network-check-target-ip-10-0-133-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-143.ec2.internal
      uid: f09d6f50-8bea-4ad3-8e94-e35be205fe7c
    resourceVersion: "89448"
    uid: 2dde3934-27e1-4b8c-9d8c-53ca1f1bc9b5
  spec:
    sourcePod: network-check-source-6f8b768455-gpxl8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:48Z"
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.711668ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:59:48Z"
    - latency: 2.607502ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:58:48Z"
    - latency: 2.013314ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:57:48Z"
    - latency: 2.346163ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:56:48Z"
    - latency: 1.985697ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:55:48Z"
    - latency: 2.501046ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:54:48Z"
    - latency: 2.399008ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:53:48Z"
    - latency: 2.483659ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:52:48Z"
    - latency: 2.116313ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:51:48Z"
    - latency: 2.439975ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:50:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-143-to-network-check-target-ip-10-0-141-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-143.ec2.internal
      uid: f09d6f50-8bea-4ad3-8e94-e35be205fe7c
    resourceVersion: "89446"
    uid: 2c95e3ed-9b86-4cec-97b3-2cf9ecf54bc6
  spec:
    sourcePod: network-check-source-6f8b768455-gpxl8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:48Z"
      message: 'network-check-target-ip-10-0-141-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.178µs
      message: 'network-check-target-ip-10-0-141-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:59:48Z"
    - latency: 743.908µs
      message: 'network-check-target-ip-10-0-141-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:58:48Z"
    - latency: 745.588µs
      message: 'network-check-target-ip-10-0-141-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:57:48Z"
    - latency: 896.266µs
      message: 'network-check-target-ip-10-0-141-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:56:48Z"
    - latency: 1.086255ms
      message: 'network-check-target-ip-10-0-141-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:55:48Z"
    - latency: 876.09µs
      message: 'network-check-target-ip-10-0-141-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:54:48Z"
    - latency: 828.093µs
      message: 'network-check-target-ip-10-0-141-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:53:48Z"
    - latency: 719.492µs
      message: 'network-check-target-ip-10-0-141-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:52:48Z"
    - latency: 826.332µs
      message: 'network-check-target-ip-10-0-141-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:51:48Z"
    - latency: 951.664µs
      message: 'network-check-target-ip-10-0-141-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:50:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-143-to-network-check-target-ip-10-0-142-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-143.ec2.internal
      uid: f09d6f50-8bea-4ad3-8e94-e35be205fe7c
    resourceVersion: "89447"
    uid: 1714e064-38f6-44c5-b04b-d3cc790a2666
  spec:
    sourcePod: network-check-source-6f8b768455-gpxl8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:48Z"
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.638325ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:59:48Z"
    - latency: 2.393087ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:58:48Z"
    - latency: 2.351046ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:57:48Z"
    - latency: 2.346116ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:56:48Z"
    - latency: 2.503465ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:55:48Z"
    - latency: 2.203534ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:54:48Z"
    - latency: 2.599795ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:53:48Z"
    - latency: 2.725954ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:52:48Z"
    - latency: 2.482507ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:51:48Z"
    - latency: 2.396218ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:50:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-143-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-143.ec2.internal
      uid: f09d6f50-8bea-4ad3-8e94-e35be205fe7c
    resourceVersion: "91300"
    uid: 42254bff-bde6-4325-90df-d168f7b654e2
  spec:
    sourcePod: network-check-source-6f8b768455-gpxl8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:55:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.128µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:01:48Z"
    - latency: 1.69375ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:01:48Z"
    - latency: 924.816µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:00:48Z"
    - latency: 1.619057ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:00:48Z"
    - latency: 989.644µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:59:48Z"
    - latency: 1.828715ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:59:48Z"
    - latency: 1.181136ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:58:48Z"
    - latency: 1.557701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:58:48Z"
    - latency: 821.245µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:57:48Z"
    - latency: 2.194406ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:57:48Z"
kind: List
metadata:
  resourceVersion: ""