apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T11:16:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-89-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-89.ec2.internal
      uid: 4236379b-9562-4ef4-a777-a5b2062b25fb
    resourceVersion: "54563"
    uid: 3551822e-035a-4dc5-9d88-86853082df81
  spec:
    sourcePod: network-check-source-989f8b8dc-wv8nj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T11:23:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.3136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:51:44Z"
    - latency: 1.111059ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:50:44Z"
    - latency: 1.05897ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:49:44Z"
    - latency: 1.095653ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:48:44Z"
    - latency: 1.169751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:47:44Z"
    - latency: 953.985µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:46:44Z"
    - latency: 797.179µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:45:44Z"
    - latency: 1.024866ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:44:44Z"
    - latency: 989.693µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:43:44Z"
    - latency: 1.1997ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:42:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T11:16:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-89-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-89.ec2.internal
      uid: 4236379b-9562-4ef4-a777-a5b2062b25fb
    resourceVersion: "55579"
    uid: cc035fc3-97f6-45a3-ad86-8d02fb615001
  spec:
    sourcePod: network-check-source-989f8b8dc-wv8nj
    targetEndpoint: a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T11:22:44Z"
      message: 'load-balancer-api-external: tcp connection to a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.766085ms
      message: 'load-balancer-api-external: tcp connection to a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:52:44Z"
    - latency: 8.398005ms
      message: 'load-balancer-api-external: resolved host name a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:52:44Z"
    - latency: 6.306364ms
      message: 'load-balancer-api-external: tcp connection to a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:51:44Z"
    - latency: 8.964105ms
      message: 'load-balancer-api-external: resolved host name a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:51:44Z"
    - latency: 4.896369ms
      message: 'load-balancer-api-external: tcp connection to a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:50:44Z"
    - latency: 9.171119ms
      message: 'load-balancer-api-external: resolved host name a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:50:44Z"
    - latency: 5.322896ms
      message: 'load-balancer-api-external: tcp connection to a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:49:44Z"
    - latency: 8.460484ms
      message: 'load-balancer-api-external: resolved host name a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:49:44Z"
    - latency: 3.515631ms
      message: 'load-balancer-api-external: tcp connection to a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:48:44Z"
    - latency: 7.94746ms
      message: 'load-balancer-api-external: resolved host name a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:48:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T11:16:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-89-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-89.ec2.internal
      uid: 4236379b-9562-4ef4-a777-a5b2062b25fb
    resourceVersion: "55580"
    uid: c37049eb-f5bc-47bc-98b5-02b4047663c4
  spec:
    sourcePod: network-check-source-989f8b8dc-wv8nj
    targetEndpoint: a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T11:22:44Z"
      message: 'load-balancer-api-internal: tcp connection to a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.782022ms
      message: 'load-balancer-api-internal: tcp connection to a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:52:44Z"
    - latency: 8.228173ms
      message: 'load-balancer-api-internal: resolved host name a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:52:44Z"
    - latency: 5.203499ms
      message: 'load-balancer-api-internal: tcp connection to a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:51:44Z"
    - latency: 8.833095ms
      message: 'load-balancer-api-internal: resolved host name a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:51:44Z"
    - latency: 4.247032ms
      message: 'load-balancer-api-internal: tcp connection to a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:50:44Z"
    - latency: 9.031908ms
      message: 'load-balancer-api-internal: resolved host name a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:50:44Z"
    - latency: 5.645288ms
      message: 'load-balancer-api-internal: tcp connection to a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:49:44Z"
    - latency: 8.516253ms
      message: 'load-balancer-api-internal: resolved host name a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:49:44Z"
    - latency: 4.667555ms
      message: 'load-balancer-api-internal: tcp connection to a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:48:44Z"
    - latency: 7.887434ms
      message: 'load-balancer-api-internal: resolved host name a9bb111ad5c2f46f283f00b1d3706b5d-f08f2e2576a7fa46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:48:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T11:16:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-89-to-network-check-target-ip-10-0-136-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-89.ec2.internal
      uid: 4236379b-9562-4ef4-a777-a5b2062b25fb
    resourceVersion: "54562"
    uid: 72247097-8bcb-4ae5-b337-ee584b0c561e
  spec:
    sourcePod: network-check-source-989f8b8dc-wv8nj
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T11:23:44Z"
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.591762ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:51:44Z"
    - latency: 2.78453ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:50:44Z"
    - latency: 2.454438ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:49:44Z"
    - latency: 2.672366ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:48:44Z"
    - latency: 2.509433ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:47:44Z"
    - latency: 2.449477ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:46:44Z"
    - latency: 2.495481ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:45:44Z"
    - latency: 2.624278ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:44:44Z"
    - latency: 2.836104ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:43:44Z"
    - latency: 2.607678ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:42:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T11:16:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-89-to-network-check-target-ip-10-0-141-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-89.ec2.internal
      uid: 4236379b-9562-4ef4-a777-a5b2062b25fb
    resourceVersion: "54561"
    uid: 35bd48d4-b7c9-49ae-883d-8af8b70fdee3
  spec:
    sourcePod: network-check-source-989f8b8dc-wv8nj
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T11:23:44Z"
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.984946ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:51:44Z"
    - latency: 2.676986ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:50:44Z"
    - latency: 2.120915ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:49:44Z"
    - latency: 2.000597ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:48:44Z"
    - latency: 1.988815ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:47:44Z"
    - latency: 2.263275ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:46:44Z"
    - latency: 2.195644ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:45:44Z"
    - latency: 2.353306ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:44:44Z"
    - latency: 2.384148ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:43:44Z"
    - latency: 1.972366ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:42:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T11:16:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-89-to-network-check-target-ip-10-0-141-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-89.ec2.internal
      uid: 4236379b-9562-4ef4-a777-a5b2062b25fb
    resourceVersion: "54560"
    uid: 46747950-3df9-40d3-aafb-f84882f6d471
  spec:
    sourcePod: network-check-source-989f8b8dc-wv8nj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T11:23:44Z"
      message: 'network-check-target-ip-10-0-141-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.025µs
      message: 'network-check-target-ip-10-0-141-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:51:44Z"
    - latency: 1.371994ms
      message: 'network-check-target-ip-10-0-141-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:50:44Z"
    - latency: 719.077µs
      message: 'network-check-target-ip-10-0-141-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:49:44Z"
    - latency: 1.187659ms
      message: 'network-check-target-ip-10-0-141-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:48:44Z"
    - latency: 739.297µs
      message: 'network-check-target-ip-10-0-141-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:47:44Z"
    - latency: 786.65µs
      message: 'network-check-target-ip-10-0-141-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:46:44Z"
    - latency: 800.446µs
      message: 'network-check-target-ip-10-0-141-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:45:44Z"
    - latency: 908.249µs
      message: 'network-check-target-ip-10-0-141-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:44:44Z"
    - latency: 929.146µs
      message: 'network-check-target-ip-10-0-141-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:43:44Z"
    - latency: 1.089767ms
      message: 'network-check-target-ip-10-0-141-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:42:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T11:16:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-89-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-89.ec2.internal
      uid: 4236379b-9562-4ef4-a777-a5b2062b25fb
    resourceVersion: "55577"
    uid: 6d3566a7-b0fc-4f73-af4a-dcdc36248162
  spec:
    sourcePod: network-check-source-989f8b8dc-wv8nj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T11:22:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.221034ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:52:44Z"
    - latency: 1.896901ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:52:44Z"
    - latency: 849.91µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:51:44Z"
    - latency: 2.225777ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:51:44Z"
    - latency: 743.769µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:50:44Z"
    - latency: 1.764392ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:50:44Z"
    - latency: 768.954µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:49:44Z"
    - latency: 1.664289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:49:44Z"
    - latency: 957.365µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T11:48:44Z"
    - latency: 1.817012ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T11:48:44Z"
kind: List
metadata:
  resourceVersion: ""