apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-219-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-219.ec2.internal
      uid: cd05e7d3-7cab-4643-bb08-b437aa227b3d
    resourceVersion: "64266"
    uid: 065377b0-78ea-48ef-a21a-c00d5812cd5d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xjg6k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T19:41:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.193745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:16:06Z"
    - latency: 1.190966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:15:06Z"
    - latency: 905.225µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:14:06Z"
    - latency: 1.274677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:13:06Z"
    - latency: 870.483µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:12:06Z"
    - latency: 1.10342ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:11:06Z"
    - latency: 1.037432ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:10:06Z"
    - latency: 1.187953ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:09:06Z"
    - latency: 1.104281ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:08:06Z"
    - latency: 899.688µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:07:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-219-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-219.ec2.internal
      uid: cd05e7d3-7cab-4643-bb08-b437aa227b3d
    resourceVersion: "64267"
    uid: 619bf8e0-08d0-408e-bab8-f1ab13e989c3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xjg6k
    targetEndpoint: a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T19:40:06Z"
      message: 'load-balancer-api-external: tcp connection to a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.897548ms
      message: 'load-balancer-api-external: tcp connection to a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:16:06Z"
    - latency: 8.194793ms
      message: 'load-balancer-api-external: resolved host name a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:16:06Z"
    - latency: 5.841495ms
      message: 'load-balancer-api-external: tcp connection to a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:15:06Z"
    - latency: 6.697151ms
      message: 'load-balancer-api-external: resolved host name a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:15:06Z"
    - latency: 5.4849ms
      message: 'load-balancer-api-external: tcp connection to a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:14:06Z"
    - latency: 6.671568ms
      message: 'load-balancer-api-external: resolved host name a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:14:06Z"
    - latency: 3.013614ms
      message: 'load-balancer-api-external: tcp connection to a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:13:06Z"
    - latency: 6.560685ms
      message: 'load-balancer-api-external: resolved host name a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:13:06Z"
    - latency: 4.474505ms
      message: 'load-balancer-api-external: tcp connection to a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:12:06Z"
    - latency: 6.739733ms
      message: 'load-balancer-api-external: resolved host name a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:12:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-219-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-219.ec2.internal
      uid: cd05e7d3-7cab-4643-bb08-b437aa227b3d
    resourceVersion: "64268"
    uid: 80d839e6-15d2-4c02-a047-02fd1c12527e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xjg6k
    targetEndpoint: a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T19:40:06Z"
      message: 'load-balancer-api-internal: tcp connection to a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.947653ms
      message: 'load-balancer-api-internal: tcp connection to a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:16:06Z"
    - latency: 8.166704ms
      message: 'load-balancer-api-internal: resolved host name a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:16:06Z"
    - latency: 6.315687ms
      message: 'load-balancer-api-internal: tcp connection to a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:15:06Z"
    - latency: 6.661379ms
      message: 'load-balancer-api-internal: resolved host name a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:15:06Z"
    - latency: 4.48304ms
      message: 'load-balancer-api-internal: tcp connection to a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:14:06Z"
    - latency: 6.622914ms
      message: 'load-balancer-api-internal: resolved host name a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:14:06Z"
    - latency: 4.810239ms
      message: 'load-balancer-api-internal: tcp connection to a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:13:06Z"
    - latency: 6.53216ms
      message: 'load-balancer-api-internal: resolved host name a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:13:06Z"
    - latency: 4.444031ms
      message: 'load-balancer-api-internal: tcp connection to a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:12:06Z"
    - latency: 6.721314ms
      message: 'load-balancer-api-internal: resolved host name a91c32ceb6b1e44189a52fd1f6eeb01b-5096a304208d5b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:12:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-219-to-network-check-target-ip-10-0-128-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-219.ec2.internal
      uid: cd05e7d3-7cab-4643-bb08-b437aa227b3d
    resourceVersion: "64264"
    uid: 83e00030-f4e0-448f-bebc-b4e331124740
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xjg6k
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T19:41:06Z"
      message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.24669ms
      message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:16:06Z"
    - latency: 2.171549ms
      message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:15:06Z"
    - latency: 2.421946ms
      message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:14:06Z"
    - latency: 2.419074ms
      message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:13:06Z"
    - latency: 2.103045ms
      message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:12:06Z"
    - latency: 2.327687ms
      message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:11:06Z"
    - latency: 2.338455ms
      message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:10:06Z"
    - latency: 2.359745ms
      message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:09:06Z"
    - latency: 2.238727ms
      message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:08:06Z"
    - latency: 2.347692ms
      message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:07:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-219-to-network-check-target-ip-10-0-132-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-219.ec2.internal
      uid: cd05e7d3-7cab-4643-bb08-b437aa227b3d
    resourceVersion: "64262"
    uid: c50a66e5-51b7-4681-864f-072a1e7c3f9d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xjg6k
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T19:41:06Z"
      message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.249199ms
      message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:16:06Z"
    - latency: 911.186µs
      message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:15:06Z"
    - latency: 1.161507ms
      message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:14:06Z"
    - latency: 908.939µs
      message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:13:06Z"
    - latency: 775.883µs
      message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:12:06Z"
    - latency: 1.009719ms
      message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:11:06Z"
    - latency: 958.246µs
      message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:10:06Z"
    - latency: 972.768µs
      message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:09:06Z"
    - latency: 1.164209ms
      message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:08:06Z"
    - latency: 1.077531ms
      message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:07:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-219-to-network-check-target-ip-10-0-132-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-219.ec2.internal
      uid: cd05e7d3-7cab-4643-bb08-b437aa227b3d
    resourceVersion: "64263"
    uid: 2654ad7d-d7cc-444f-972d-b02b515f5314
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xjg6k
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T19:41:06Z"
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.052786ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:16:06Z"
    - latency: 2.024311ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:15:06Z"
    - latency: 1.849825ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:14:06Z"
    - latency: 2.175191ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:13:06Z"
    - latency: 1.898547ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:12:06Z"
    - latency: 1.952544ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:11:06Z"
    - latency: 1.972802ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:10:06Z"
    - latency: 1.978738ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:09:06Z"
    - latency: 2.139933ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:08:06Z"
    - latency: 1.986381ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:07:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-219-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-219.ec2.internal
      uid: cd05e7d3-7cab-4643-bb08-b437aa227b3d
    resourceVersion: "64265"
    uid: e23205ea-6697-4466-9d4c-10a770b1e638
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xjg6k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T19:40:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 812.072µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:16:06Z"
    - latency: 2.114536ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:16:06Z"
    - latency: 909.198µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:15:06Z"
    - latency: 1.835119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:15:06Z"
    - latency: 1.09755ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:14:06Z"
    - latency: 1.879004ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:14:06Z"
    - latency: 919.547µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:13:06Z"
    - latency: 1.836075ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:13:06Z"
    - latency: 769.809µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:12:06Z"
    - latency: 1.948109ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:12:06Z"
kind: List
metadata:
  resourceVersion: ""