apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:55:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 098d25ab-4a4e-491f-930e-d1111c829791
    resourceVersion: "54302"
    uid: effdcc13-d47f-4023-8dc1-bdd328923d3c
  spec:
    sourcePod: network-check-source-989f8b8dc-wnwbk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:02:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 833.654µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:30:50Z"
    - latency: 985.335µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:29:50Z"
    - latency: 906.8µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:28:50Z"
    - latency: 1.114435ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:27:50Z"
    - latency: 959.533µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:26:50Z"
    - latency: 949.057µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:25:50Z"
    - latency: 797.436µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:24:50Z"
    - latency: 912.668µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:23:50Z"
    - latency: 1.752457ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:22:50Z"
    - latency: 921.409µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:21:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:55:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 098d25ab-4a4e-491f-930e-d1111c829791
    resourceVersion: "55379"
    uid: 2a9b9e6a-d307-4007-838e-365a37ad0212
  spec:
    sourcePod: network-check-source-989f8b8dc-wnwbk
    targetEndpoint: aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:01:50Z"
      message: 'load-balancer-api-external: tcp connection to aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.000041ms
      message: 'load-balancer-api-external: tcp connection to aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:31:50Z"
    - latency: 8.177745ms
      message: 'load-balancer-api-external: resolved host name aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:31:50Z"
    - latency: 6.773445ms
      message: 'load-balancer-api-external: tcp connection to aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:30:50Z"
    - latency: 8.043008ms
      message: 'load-balancer-api-external: resolved host name aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:30:50Z"
    - latency: 5.505102ms
      message: 'load-balancer-api-external: tcp connection to aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:29:50Z"
    - latency: 8.709209ms
      message: 'load-balancer-api-external: resolved host name aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:29:50Z"
    - latency: 4.505473ms
      message: 'load-balancer-api-external: tcp connection to aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:28:50Z"
    - latency: 8.101935ms
      message: 'load-balancer-api-external: resolved host name aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:28:50Z"
    - latency: 4.44315ms
      message: 'load-balancer-api-external: tcp connection to aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:27:50Z"
    - latency: 7.582678ms
      message: 'load-balancer-api-external: resolved host name aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:27:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:55:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 098d25ab-4a4e-491f-930e-d1111c829791
    resourceVersion: "55380"
    uid: f5251ea2-8efe-418b-9a47-3f594fc361fe
  spec:
    sourcePod: network-check-source-989f8b8dc-wnwbk
    targetEndpoint: aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:01:50Z"
      message: 'load-balancer-api-internal: tcp connection to aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.847832ms
      message: 'load-balancer-api-internal: tcp connection to aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:31:50Z"
    - latency: 8.203227ms
      message: 'load-balancer-api-internal: resolved host name aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:31:50Z"
    - latency: 3.953928ms
      message: 'load-balancer-api-internal: tcp connection to aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:30:50Z"
    - latency: 8.117627ms
      message: 'load-balancer-api-internal: resolved host name aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:30:50Z"
    - latency: 8.106194ms
      message: 'load-balancer-api-internal: tcp connection to aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:29:50Z"
    - latency: 8.735693ms
      message: 'load-balancer-api-internal: resolved host name aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:29:50Z"
    - latency: 5.462388ms
      message: 'load-balancer-api-internal: tcp connection to aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:28:50Z"
    - latency: 8.071077ms
      message: 'load-balancer-api-internal: resolved host name aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:28:50Z"
    - latency: 3.36745ms
      message: 'load-balancer-api-internal: tcp connection to aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:27:50Z"
    - latency: 7.616332ms
      message: 'load-balancer-api-internal: resolved host name aa2e83fec9cfc4a28a87df8783090d66-b663ca8bad3ea9ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:27:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:55:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-network-check-target-ip-10-0-132-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 098d25ab-4a4e-491f-930e-d1111c829791
    resourceVersion: "54299"
    uid: ead3659c-2c2d-4d79-a1ea-a8f27f210c7d
  spec:
    sourcePod: network-check-source-989f8b8dc-wnwbk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:02:50Z"
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 938.798µs
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:30:50Z"
    - latency: 1.287193ms
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:29:50Z"
    - latency: 949.424µs
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:28:50Z"
    - latency: 805.525µs
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:27:50Z"
    - latency: 903.082µs
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:26:50Z"
    - latency: 2.063237ms
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:25:50Z"
    - latency: 1.431755ms
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:24:50Z"
    - latency: 1.341558ms
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:23:50Z"
    - latency: 1.327711ms
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:22:50Z"
    - latency: 911.617µs
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:21:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:55:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-network-check-target-ip-10-0-134-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 098d25ab-4a4e-491f-930e-d1111c829791
    resourceVersion: "54300"
    uid: b5098936-1c19-4f91-b04d-9e277d95e001
  spec:
    sourcePod: network-check-source-989f8b8dc-wnwbk
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:02:50Z"
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.40883ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:30:50Z"
    - latency: 2.077922ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:29:50Z"
    - latency: 2.08242ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:28:50Z"
    - latency: 2.346429ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:27:50Z"
    - latency: 2.65454ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:26:50Z"
    - latency: 2.375608ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:25:50Z"
    - latency: 2.032182ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:24:50Z"
    - latency: 2.9752ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:23:50Z"
    - latency: 2.890491ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:22:50Z"
    - latency: 1.95801ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:21:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:55:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-network-check-target-ip-10-0-136-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 098d25ab-4a4e-491f-930e-d1111c829791
    resourceVersion: "54301"
    uid: cb5424e8-7c84-4c4a-90e5-c0b8f432a09e
  spec:
    sourcePod: network-check-source-989f8b8dc-wnwbk
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:02:50Z"
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.045192ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:30:50Z"
    - latency: 2.273662ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:29:50Z"
    - latency: 2.094885ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:28:50Z"
    - latency: 2.257968ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:27:50Z"
    - latency: 2.474958ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:26:50Z"
    - latency: 2.487971ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:25:50Z"
    - latency: 2.099574ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:24:50Z"
    - latency: 2.30551ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:23:50Z"
    - latency: 3.017015ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:22:50Z"
    - latency: 2.869711ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:21:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:55:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 098d25ab-4a4e-491f-930e-d1111c829791
    resourceVersion: "55378"
    uid: 341db7b0-098b-43d0-b5bd-4255adfea0e6
  spec:
    sourcePod: network-check-source-989f8b8dc-wnwbk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:01:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 868.388µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:31:50Z"
    - latency: 1.683557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:31:50Z"
    - latency: 1.133851ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:30:50Z"
    - latency: 1.685086ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:30:50Z"
    - latency: 971.039µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:29:50Z"
    - latency: 2.342559ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:29:50Z"
    - latency: 934.778µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:28:50Z"
    - latency: 1.645684ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:28:50Z"
    - latency: 1.131917ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:27:50Z"
    - latency: 1.780687ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:27:50Z"
kind: List
metadata:
  resourceVersion: ""