apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T16:53:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: 9f7e7ceb-3ae8-4872-98c7-307de666aaef
    resourceVersion: "31937"
    uid: a147473c-ccce-475c-9c39-5b270bf6bdfe
  spec:
    sourcePod: network-check-source-dbd9cf844-j6d7k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T17:00:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.263µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:07:24Z"
    - latency: 936.104µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:06:24Z"
    - latency: 1.038303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:05:24Z"
    - latency: 967.436µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:04:24Z"
    - latency: 888.115µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:03:24Z"
    - latency: 1.101741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:02:24Z"
    - latency: 1.017118ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:01:24Z"
    - latency: 903.182µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:00:24Z"
    - latency: 1.03779ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T16:59:24Z"
    - latency: 949.035µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T16:58:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T16:53:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: 9f7e7ceb-3ae8-4872-98c7-307de666aaef
    resourceVersion: "30001"
    uid: 48235ddb-47e6-45a1-b268-7bdb315574d8
  spec:
    sourcePod: network-check-source-dbd9cf844-j6d7k
    targetEndpoint: acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T16:59:24Z"
      message: 'load-balancer-api-external: tcp connection to acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.140689ms
      message: 'load-balancer-api-external: tcp connection to acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:05:24Z"
    - latency: 7.234437ms
      message: 'load-balancer-api-external: resolved host name acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:05:24Z"
    - latency: 4.843275ms
      message: 'load-balancer-api-external: tcp connection to acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:04:24Z"
    - latency: 7.587052ms
      message: 'load-balancer-api-external: resolved host name acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:04:24Z"
    - latency: 6.736675ms
      message: 'load-balancer-api-external: tcp connection to acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:03:24Z"
    - latency: 6.999283ms
      message: 'load-balancer-api-external: resolved host name acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:03:24Z"
    - latency: 4.398324ms
      message: 'load-balancer-api-external: tcp connection to acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:02:24Z"
    - latency: 8.919815ms
      message: 'load-balancer-api-external: resolved host name acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:02:24Z"
    - latency: 5.000189ms
      message: 'load-balancer-api-external: tcp connection to acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:01:24Z"
    - latency: 6.980615ms
      message: 'load-balancer-api-external: resolved host name acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:01:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T16:53:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: 9f7e7ceb-3ae8-4872-98c7-307de666aaef
    resourceVersion: "30002"
    uid: d9e7475d-21a5-4160-9126-500efd7917b6
  spec:
    sourcePod: network-check-source-dbd9cf844-j6d7k
    targetEndpoint: acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T16:59:24Z"
      message: 'load-balancer-api-internal: tcp connection to acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.144866ms
      message: 'load-balancer-api-internal: tcp connection to acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:05:24Z"
    - latency: 7.26734ms
      message: 'load-balancer-api-internal: resolved host name acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:05:24Z"
    - latency: 4.84879ms
      message: 'load-balancer-api-internal: tcp connection to acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:04:24Z"
    - latency: 7.606162ms
      message: 'load-balancer-api-internal: resolved host name acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:04:24Z"
    - latency: 6.730113ms
      message: 'load-balancer-api-internal: tcp connection to acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:03:24Z"
    - latency: 7.045874ms
      message: 'load-balancer-api-internal: resolved host name acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:03:24Z"
    - latency: 4.497225ms
      message: 'load-balancer-api-internal: tcp connection to acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:02:24Z"
    - latency: 8.951264ms
      message: 'load-balancer-api-internal: resolved host name acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:02:24Z"
    - latency: 4.408933ms
      message: 'load-balancer-api-internal: tcp connection to acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:01:24Z"
    - latency: 7.001223ms
      message: 'load-balancer-api-internal: resolved host name acce2815c6e714e0ea3ee0a0fcd2ce76-e8b541a747540c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:01:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T16:53:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-network-check-target-ip-10-0-131-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: 9f7e7ceb-3ae8-4872-98c7-307de666aaef
    resourceVersion: "31936"
    uid: c0081478-e7d5-4540-863c-63e9074fa691
  spec:
    sourcePod: network-check-source-dbd9cf844-j6d7k
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T17:00:24Z"
      message: 'network-check-target-ip-10-0-131-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.888981ms
      message: 'network-check-target-ip-10-0-131-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:07:24Z"
    - latency: 2.303673ms
      message: 'network-check-target-ip-10-0-131-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:06:24Z"
    - latency: 2.460749ms
      message: 'network-check-target-ip-10-0-131-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:05:24Z"
    - latency: 2.232799ms
      message: 'network-check-target-ip-10-0-131-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:04:24Z"
    - latency: 2.2467ms
      message: 'network-check-target-ip-10-0-131-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:03:24Z"
    - latency: 2.384416ms
      message: 'network-check-target-ip-10-0-131-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:02:24Z"
    - latency: 2.810435ms
      message: 'network-check-target-ip-10-0-131-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:01:24Z"
    - latency: 2.285975ms
      message: 'network-check-target-ip-10-0-131-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:00:24Z"
    - latency: 2.0791ms
      message: 'network-check-target-ip-10-0-131-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T16:59:24Z"
    - latency: 2.227508ms
      message: 'network-check-target-ip-10-0-131-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T16:58:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T16:53:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-network-check-target-ip-10-0-133-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: 9f7e7ceb-3ae8-4872-98c7-307de666aaef
    resourceVersion: "31935"
    uid: 65dafbde-c1b3-4cff-aa8e-c401512c93d9
  spec:
    sourcePod: network-check-source-dbd9cf844-j6d7k
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T17:00:24Z"
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.0166ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:07:24Z"
    - latency: 2.979354ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:06:24Z"
    - latency: 2.043204ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:05:24Z"
    - latency: 2.526487ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:04:24Z"
    - latency: 2.180518ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:03:24Z"
    - latency: 2.348761ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:02:24Z"
    - latency: 2.264901ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:01:24Z"
    - latency: 2.127199ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:00:24Z"
    - latency: 2.116176ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T16:59:24Z"
    - latency: 2.26416ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T16:58:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T16:53:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-network-check-target-ip-10-0-143-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: 9f7e7ceb-3ae8-4872-98c7-307de666aaef
    resourceVersion: "31934"
    uid: 3eebfca6-7ec1-410a-9605-408d7c6732b6
  spec:
    sourcePod: network-check-source-dbd9cf844-j6d7k
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T17:00:24Z"
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.255709ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:07:24Z"
    - latency: 773.176µs
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:06:24Z"
    - latency: 859.803µs
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:05:24Z"
    - latency: 876.764µs
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:04:24Z"
    - latency: 752.117µs
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:03:24Z"
    - latency: 922.056µs
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:02:24Z"
    - latency: 884.361µs
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:01:24Z"
    - latency: 860.605µs
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:00:24Z"
    - latency: 843.398µs
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T16:59:24Z"
    - latency: 1.096887ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T16:58:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T16:53:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: 9f7e7ceb-3ae8-4872-98c7-307de666aaef
    resourceVersion: "30000"
    uid: c466600f-0a11-438f-9a72-24f4a1aab95d
  spec:
    sourcePod: network-check-source-dbd9cf844-j6d7k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T16:59:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 835.702µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:05:24Z"
    - latency: 1.646219ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:05:24Z"
    - latency: 812.027µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:04:24Z"
    - latency: 1.83766ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:04:24Z"
    - latency: 806.187µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:03:24Z"
    - latency: 1.567587ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:03:24Z"
    - latency: 893.588µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:02:24Z"
    - latency: 1.804579ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:02:24Z"
    - latency: 859.816µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T17:01:24Z"
    - latency: 1.615399ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T17:01:24Z"
kind: List
metadata:
  resourceVersion: ""