apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-36-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-36.ec2.internal
      uid: a0da827d-4b0d-430f-9ddd-745d94280840
    resourceVersion: "31434"
    uid: 7ac8102b-f3f7-417e-899d-a6b8946fa725
  spec:
    sourcePod: network-check-source-7f44b6dd87-9lllh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:28:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 950.304µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:03:09Z"
    - latency: 797.647µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:02:09Z"
    - latency: 1.007699ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:01:09Z"
    - latency: 946.744µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:00:09Z"
    - latency: 976.718µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:59:09Z"
    - latency: 1.272518ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:58:09Z"
    - latency: 986.824µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:57:09Z"
    - latency: 1.016166ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:56:09Z"
    - latency: 1.017823ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:55:09Z"
    - latency: 872.205µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:54:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-36-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-36.ec2.internal
      uid: a0da827d-4b0d-430f-9ddd-745d94280840
    resourceVersion: "31435"
    uid: 6f045a1f-072f-4b71-9661-ba8228e53a69
  spec:
    sourcePod: network-check-source-7f44b6dd87-9lllh
    targetEndpoint: a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:27:09Z"
      message: 'load-balancer-api-external: tcp connection to a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.990057ms
      message: 'load-balancer-api-external: tcp connection to a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:03:09Z"
    - latency: 7.288364ms
      message: 'load-balancer-api-external: resolved host name a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:03:09Z"
    - latency: 4.684299ms
      message: 'load-balancer-api-external: tcp connection to a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:02:09Z"
    - latency: 7.5893ms
      message: 'load-balancer-api-external: resolved host name a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:02:09Z"
    - latency: 4.257175ms
      message: 'load-balancer-api-external: tcp connection to a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:01:09Z"
    - latency: 7.551959ms
      message: 'load-balancer-api-external: resolved host name a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:01:09Z"
    - latency: 3.96132ms
      message: 'load-balancer-api-external: tcp connection to a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:00:09Z"
    - latency: 7.258103ms
      message: 'load-balancer-api-external: resolved host name a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:00:09Z"
    - latency: 4.104335ms
      message: 'load-balancer-api-external: tcp connection to a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:59:09Z"
    - latency: 7.788886ms
      message: 'load-balancer-api-external: resolved host name a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:59:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-36-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-36.ec2.internal
      uid: a0da827d-4b0d-430f-9ddd-745d94280840
    resourceVersion: "31436"
    uid: 231bf0a4-0277-4858-8e78-bb6b89eda595
  spec:
    sourcePod: network-check-source-7f44b6dd87-9lllh
    targetEndpoint: a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:27:09Z"
      message: 'load-balancer-api-internal: tcp connection to a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.021026ms
      message: 'load-balancer-api-internal: tcp connection to a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:03:09Z"
    - latency: 7.254685ms
      message: 'load-balancer-api-internal: resolved host name a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:03:09Z"
    - latency: 4.83824ms
      message: 'load-balancer-api-internal: tcp connection to a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:02:09Z"
    - latency: 7.49618ms
      message: 'load-balancer-api-internal: resolved host name a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:02:09Z"
    - latency: 3.851531ms
      message: 'load-balancer-api-internal: tcp connection to a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:01:09Z"
    - latency: 7.607818ms
      message: 'load-balancer-api-internal: resolved host name a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:01:09Z"
    - latency: 3.973915ms
      message: 'load-balancer-api-internal: tcp connection to a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:00:09Z"
    - latency: 7.352644ms
      message: 'load-balancer-api-internal: resolved host name a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:00:09Z"
    - latency: 4.040858ms
      message: 'load-balancer-api-internal: tcp connection to a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:59:09Z"
    - latency: 7.74854ms
      message: 'load-balancer-api-internal: resolved host name a6b7f0f9388f84880aa836a57ee171dd-35cb021b94eed9fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:59:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-36-to-network-check-target-ip-10-0-128-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-36.ec2.internal
      uid: a0da827d-4b0d-430f-9ddd-745d94280840
    resourceVersion: "31432"
    uid: e61e16f7-6a8f-4df5-a922-c5282966e464
  spec:
    sourcePod: network-check-source-7f44b6dd87-9lllh
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:28:09Z"
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.869039ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:03:09Z"
    - latency: 1.97736ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:02:09Z"
    - latency: 1.790526ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:01:09Z"
    - latency: 1.840526ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:00:09Z"
    - latency: 1.810672ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:59:09Z"
    - latency: 1.950518ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:58:09Z"
    - latency: 1.901608ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:57:09Z"
    - latency: 1.761303ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:56:09Z"
    - latency: 1.819345ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:55:09Z"
    - latency: 1.956525ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:54:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-36-to-network-check-target-ip-10-0-131-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-36.ec2.internal
      uid: a0da827d-4b0d-430f-9ddd-745d94280840
    resourceVersion: "31430"
    uid: 47bbc125-3f54-4bb0-8bc6-0e00bac3d3c1
  spec:
    sourcePod: network-check-source-7f44b6dd87-9lllh
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:28:09Z"
      message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 747.375µs
      message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:03:09Z"
    - latency: 951.853µs
      message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:02:09Z"
    - latency: 1.099638ms
      message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:01:09Z"
    - latency: 1.280015ms
      message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:00:09Z"
    - latency: 796.012µs
      message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:59:09Z"
    - latency: 1.239938ms
      message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:58:09Z"
    - latency: 1.191134ms
      message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:57:09Z"
    - latency: 1.321874ms
      message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:56:09Z"
    - latency: 768.506µs
      message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:55:09Z"
    - latency: 784.731µs
      message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:54:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-36-to-network-check-target-ip-10-0-141-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-36.ec2.internal
      uid: a0da827d-4b0d-430f-9ddd-745d94280840
    resourceVersion: "31431"
    uid: 143d31fc-b0d6-46d5-9e11-506aa9c53599
  spec:
    sourcePod: network-check-source-7f44b6dd87-9lllh
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:28:09Z"
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.153651ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:03:09Z"
    - latency: 1.804427ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:02:09Z"
    - latency: 2.164204ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:01:09Z"
    - latency: 1.963872ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:00:09Z"
    - latency: 2.051508ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:59:09Z"
    - latency: 2.304685ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:58:09Z"
    - latency: 2.192486ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:57:09Z"
    - latency: 2.195078ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:56:09Z"
    - latency: 2.228529ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:55:09Z"
    - latency: 2.44222ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:54:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-36-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-36.ec2.internal
      uid: a0da827d-4b0d-430f-9ddd-745d94280840
    resourceVersion: "31433"
    uid: bb0ebab4-d113-47a5-8bd8-5e624b21d8ee
  spec:
    sourcePod: network-check-source-7f44b6dd87-9lllh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:27:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 758.136µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:03:09Z"
    - latency: 1.466182ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:03:09Z"
    - latency: 1.020695ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:02:09Z"
    - latency: 1.518059ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:02:09Z"
    - latency: 900.957µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:01:09Z"
    - latency: 1.767136ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:01:09Z"
    - latency: 953.606µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:00:09Z"
    - latency: 1.650913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:00:09Z"
    - latency: 1.109677ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:59:09Z"
    - latency: 1.465399ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:59:09Z"
kind: List
metadata:
  resourceVersion: ""