apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T21:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-168-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-168.ec2.internal
      uid: e58af5f3-c6a2-4bb6-aee7-514799578816
    resourceVersion: "29152"
    uid: c3b86848-96ae-41a2-b7d3-6641971edf55
  spec:
    sourcePod: network-check-source-6f8b768455-f6sqx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T22:02:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.746µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:09:35Z"
    - latency: 978.9µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:08:35Z"
    - latency: 870.554µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:07:35Z"
    - latency: 1.184791ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:06:35Z"
    - latency: 1.171038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:05:35Z"
    - latency: 794.779µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:04:35Z"
    - latency: 1.258337ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:03:35Z"
    - latency: 916.291µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:02:35Z"
    - latency: 1.148055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:01:35Z"
    - latency: 1.037816ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:00:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T21:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-168-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-168.ec2.internal
      uid: e58af5f3-c6a2-4bb6-aee7-514799578816
    resourceVersion: "31702"
    uid: 7e0c4eff-860d-416b-bf54-c17bb09ada6a
  spec:
    sourcePod: network-check-source-6f8b768455-f6sqx
    targetEndpoint: a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T22:01:35Z"
      message: 'load-balancer-api-external: tcp connection to a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.32868ms
      message: 'load-balancer-api-external: tcp connection to a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:13:35Z"
    - latency: 7.299165ms
      message: 'load-balancer-api-external: resolved host name a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:13:35Z"
    - latency: 4.889642ms
      message: 'load-balancer-api-external: tcp connection to a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:12:35Z"
    - latency: 5.934128ms
      message: 'load-balancer-api-external: resolved host name a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:12:35Z"
    - latency: 5.060455ms
      message: 'load-balancer-api-external: tcp connection to a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:11:35Z"
    - latency: 7.386802ms
      message: 'load-balancer-api-external: resolved host name a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:11:35Z"
    - latency: 5.421595ms
      message: 'load-balancer-api-external: tcp connection to a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:10:35Z"
    - latency: 6.83233ms
      message: 'load-balancer-api-external: resolved host name a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:10:35Z"
    - latency: 5.334349ms
      message: 'load-balancer-api-external: tcp connection to a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:09:35Z"
    - latency: 8.468485ms
      message: 'load-balancer-api-external: resolved host name a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:09:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T21:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-168-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-168.ec2.internal
      uid: e58af5f3-c6a2-4bb6-aee7-514799578816
    resourceVersion: "31703"
    uid: 2e942f4a-135b-4d8e-a40f-3a8d532d164e
  spec:
    sourcePod: network-check-source-6f8b768455-f6sqx
    targetEndpoint: a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T22:01:35Z"
      message: 'load-balancer-api-internal: tcp connection to a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.521181ms
      message: 'load-balancer-api-internal: tcp connection to a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:13:35Z"
    - latency: 7.489234ms
      message: 'load-balancer-api-internal: resolved host name a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:13:35Z"
    - latency: 5.192537ms
      message: 'load-balancer-api-internal: tcp connection to a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:12:35Z"
    - latency: 5.879039ms
      message: 'load-balancer-api-internal: resolved host name a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:12:35Z"
    - latency: 5.225545ms
      message: 'load-balancer-api-internal: tcp connection to a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:11:35Z"
    - latency: 7.349744ms
      message: 'load-balancer-api-internal: resolved host name a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:11:35Z"
    - latency: 5.473754ms
      message: 'load-balancer-api-internal: tcp connection to a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:10:35Z"
    - latency: 6.776679ms
      message: 'load-balancer-api-internal: resolved host name a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:10:35Z"
    - latency: 5.291978ms
      message: 'load-balancer-api-internal: tcp connection to a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:09:35Z"
    - latency: 8.565926ms
      message: 'load-balancer-api-internal: resolved host name a72faedd85b39424497b482293d4b147-9d37fbf702bfef30.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:09:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T21:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-168-to-network-check-target-ip-10-0-129-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-168.ec2.internal
      uid: e58af5f3-c6a2-4bb6-aee7-514799578816
    resourceVersion: "29150"
    uid: 3cd33d1a-ec2b-43f6-bdbe-6e3cd912f9dd
  spec:
    sourcePod: network-check-source-6f8b768455-f6sqx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T22:02:35Z"
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.669995ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:09:35Z"
    - latency: 2.300142ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:08:35Z"
    - latency: 2.628945ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:07:35Z"
    - latency: 2.227359ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:06:35Z"
    - latency: 2.19797ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:05:35Z"
    - latency: 2.237276ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:04:35Z"
    - latency: 2.411655ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:03:35Z"
    - latency: 2.074795ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:02:35Z"
    - latency: 2.179584ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:01:35Z"
    - latency: 2.18616ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:00:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T21:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-168-to-network-check-target-ip-10-0-138-103
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-168.ec2.internal
      uid: e58af5f3-c6a2-4bb6-aee7-514799578816
    resourceVersion: "29151"
    uid: cfcd5e4e-ebf3-4b05-9342-919c6a3b0cec
  spec:
    sourcePod: network-check-source-6f8b768455-f6sqx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T22:02:35Z"
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.45644ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:09:35Z"
    - latency: 2.822899ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:08:35Z"
    - latency: 2.101111ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:07:35Z"
    - latency: 2.10796ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:06:35Z"
    - latency: 2.075745ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:05:35Z"
    - latency: 1.949074ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:04:35Z"
    - latency: 2.509902ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:03:35Z"
    - latency: 1.834667ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:02:35Z"
    - latency: 1.659001ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:01:35Z"
    - latency: 1.897189ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:00:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T21:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-168-to-network-check-target-ip-10-0-142-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-168.ec2.internal
      uid: e58af5f3-c6a2-4bb6-aee7-514799578816
    resourceVersion: "29149"
    uid: e702c83e-e0ee-4b9e-a90c-2643a32d868d
  spec:
    sourcePod: network-check-source-6f8b768455-f6sqx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T22:02:35Z"
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 982.679µs
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:09:35Z"
    - latency: 870.303µs
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:08:35Z"
    - latency: 976.734µs
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:07:35Z"
    - latency: 859.183µs
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:06:35Z"
    - latency: 863.077µs
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:05:35Z"
    - latency: 879.377µs
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:04:35Z"
    - latency: 1.154286ms
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:03:35Z"
    - latency: 889.284µs
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:02:35Z"
    - latency: 950.112µs
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:01:35Z"
    - latency: 894.369µs
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:00:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T21:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-168-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-168.ec2.internal
      uid: e58af5f3-c6a2-4bb6-aee7-514799578816
    resourceVersion: "31701"
    uid: 25712732-0e8c-477f-8c12-ddea701ca51a
  spec:
    sourcePod: network-check-source-6f8b768455-f6sqx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T22:01:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.001961ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:13:35Z"
    - latency: 2.714119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:13:35Z"
    - latency: 1.158184ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:12:35Z"
    - latency: 1.799556ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:12:35Z"
    - latency: 928.85µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:11:35Z"
    - latency: 1.750428ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:11:35Z"
    - latency: 1.396589ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:10:35Z"
    - latency: 1.693908ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:10:35Z"
    - latency: 1.265227ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T22:09:35Z"
    - latency: 1.819247ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T22:09:35Z"
kind: List
metadata:
  resourceVersion: ""