apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:58:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-11-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-11.ec2.internal
      uid: a30f4a6a-9441-4710-9842-15a342d80117
    resourceVersion: "64158"
    uid: 996e1b2b-0b9c-4c60-8a9b-2338b06d5027
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lrr94
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:06:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 978.73µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:41:00Z"
    - latency: 1.418511ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:40:00Z"
    - latency: 1.053598ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:39:00Z"
    - latency: 999.834µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:38:00Z"
    - latency: 1.167919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:37:00Z"
    - latency: 934.745µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:36:00Z"
    - latency: 1.141636ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:35:00Z"
    - latency: 957.79µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:34:00Z"
    - latency: 1.102867ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:33:00Z"
    - latency: 1.582734ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:32:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:58:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-11-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-11.ec2.internal
      uid: a30f4a6a-9441-4710-9842-15a342d80117
    resourceVersion: "64160"
    uid: 720a8a4a-05c8-4be9-9828-fa837bfb81d1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lrr94
    targetEndpoint: a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:05:00Z"
      message: 'load-balancer-api-external: tcp connection to a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.613818ms
      message: 'load-balancer-api-external: tcp connection to a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:41:00Z"
    - latency: 7.379754ms
      message: 'load-balancer-api-external: resolved host name a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:41:00Z"
    - latency: 4.706609ms
      message: 'load-balancer-api-external: tcp connection to a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:40:00Z"
    - latency: 9.148383ms
      message: 'load-balancer-api-external: resolved host name a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:40:00Z"
    - latency: 3.457827ms
      message: 'load-balancer-api-external: tcp connection to a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:39:00Z"
    - latency: 8.210549ms
      message: 'load-balancer-api-external: resolved host name a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:39:00Z"
    - latency: 3.227698ms
      message: 'load-balancer-api-external: tcp connection to a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:38:00Z"
    - latency: 10.557702ms
      message: 'load-balancer-api-external: resolved host name a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:38:00Z"
    - latency: 5.799998ms
      message: 'load-balancer-api-external: tcp connection to a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:37:00Z"
    - latency: 9.041472ms
      message: 'load-balancer-api-external: resolved host name a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:37:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:58:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-11-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-11.ec2.internal
      uid: a30f4a6a-9441-4710-9842-15a342d80117
    resourceVersion: "64159"
    uid: 9fc91bea-a9ee-44e9-a0c4-7366b4dbb4be
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lrr94
    targetEndpoint: a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:05:00Z"
      message: 'load-balancer-api-internal: tcp connection to a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.223425ms
      message: 'load-balancer-api-internal: tcp connection to a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:41:00Z"
    - latency: 7.272771ms
      message: 'load-balancer-api-internal: resolved host name a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:41:00Z"
    - latency: 4.576809ms
      message: 'load-balancer-api-internal: tcp connection to a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:40:00Z"
    - latency: 9.072835ms
      message: 'load-balancer-api-internal: resolved host name a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:40:00Z"
    - latency: 4.793475ms
      message: 'load-balancer-api-internal: tcp connection to a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:39:00Z"
    - latency: 8.111708ms
      message: 'load-balancer-api-internal: resolved host name a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:39:00Z"
    - latency: 3.571153ms
      message: 'load-balancer-api-internal: tcp connection to a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:38:00Z"
    - latency: 10.605811ms
      message: 'load-balancer-api-internal: resolved host name a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:38:00Z"
    - latency: 4.153314ms
      message: 'load-balancer-api-internal: tcp connection to a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:37:00Z"
    - latency: 8.939551ms
      message: 'load-balancer-api-internal: resolved host name a4a82bbaa16f8479f8fd27dff8669936-68c8b335b3a64a8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:37:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:58:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-11-to-network-check-target-ip-10-0-141-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-11.ec2.internal
      uid: a30f4a6a-9441-4710-9842-15a342d80117
    resourceVersion: "64155"
    uid: 52aac17e-ee75-4c13-820d-174cea2b456a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lrr94
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:06:00Z"
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.309653ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:41:00Z"
    - latency: 2.576608ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:40:00Z"
    - latency: 2.365386ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:39:00Z"
    - latency: 1.968403ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:38:00Z"
    - latency: 2.744429ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:37:00Z"
    - latency: 2.363535ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:36:00Z"
    - latency: 2.54482ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:35:00Z"
    - latency: 2.453699ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:34:00Z"
    - latency: 2.494014ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:33:00Z"
    - latency: 2.468791ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:32:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:58:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-11-to-network-check-target-ip-10-0-142-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-11.ec2.internal
      uid: a30f4a6a-9441-4710-9842-15a342d80117
    resourceVersion: "64154"
    uid: 218049db-358b-4889-a7f9-571c599f6a1f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lrr94
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:06:00Z"
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.182957ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:41:00Z"
    - latency: 1.031111ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:40:00Z"
    - latency: 1.231617ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:39:00Z"
    - latency: 1.217772ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:38:00Z"
    - latency: 775.107µs
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:37:00Z"
    - latency: 1.091833ms
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:36:00Z"
    - latency: 872.066µs
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:35:00Z"
    - latency: 888.185µs
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:34:00Z"
    - latency: 999.756µs
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:33:00Z"
    - latency: 860.512µs
      message: 'network-check-target-ip-10-0-142-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:32:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:58:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-11-to-network-check-target-ip-10-0-143-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-11.ec2.internal
      uid: a30f4a6a-9441-4710-9842-15a342d80117
    resourceVersion: "64156"
    uid: cae7aede-ccc6-4f58-a537-e729d1ebcc11
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lrr94
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:06:00Z"
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.691955ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:41:00Z"
    - latency: 2.178599ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:40:00Z"
    - latency: 2.15047ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:39:00Z"
    - latency: 2.362807ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:38:00Z"
    - latency: 2.221486ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:37:00Z"
    - latency: 2.483405ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:36:00Z"
    - latency: 2.494218ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:35:00Z"
    - latency: 2.377948ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:34:00Z"
    - latency: 2.40067ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:33:00Z"
    - latency: 2.361173ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:32:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T14:58:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-11-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-11.ec2.internal
      uid: a30f4a6a-9441-4710-9842-15a342d80117
    resourceVersion: "64157"
    uid: 972f86a6-2236-46b1-87e0-b945e55463c3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lrr94
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:05:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 931.166µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:41:00Z"
    - latency: 2.109907ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:41:00Z"
    - latency: 794.822µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:40:00Z"
    - latency: 2.025687ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:40:00Z"
    - latency: 1.054763ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:39:00Z"
    - latency: 1.711171ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:39:00Z"
    - latency: 953.885µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:38:00Z"
    - latency: 1.720558ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:38:00Z"
    - latency: 854.578µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:37:00Z"
    - latency: 1.777983ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:37:00Z"
kind: List
metadata:
  resourceVersion: ""