apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-151-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-151.ec2.internal
      uid: 50b0f706-3634-431e-a701-08fc016ff292
    resourceVersion: "39536"
    uid: 8796859b-02c3-4a17-8c71-1af0ffdaf493
  spec:
    sourcePod: network-check-source-7cbc45fddc-txn98
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:08:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.333µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:50:47Z"
    - latency: 955.641µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:49:47Z"
    - latency: 836.244µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:47Z"
    - latency: 1.351041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:47Z"
    - latency: 972.905µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:47Z"
    - latency: 878.229µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:45:47Z"
    - latency: 938.327µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:44:47Z"
    - latency: 1.055869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:43:47Z"
    - latency: 999.469µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:42:47Z"
    - latency: 821.381µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-151-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-151.ec2.internal
      uid: 50b0f706-3634-431e-a701-08fc016ff292
    resourceVersion: "38980"
    uid: 17729591-281a-4d8f-ae9b-e8d8c2773234
  spec:
    sourcePod: network-check-source-7cbc45fddc-txn98
    targetEndpoint: a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:07:47Z"
      message: 'load-balancer-api-external: tcp connection to a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.457854ms
      message: 'load-balancer-api-external: tcp connection to a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:49:47Z"
    - latency: 8.304087ms
      message: 'load-balancer-api-external: resolved host name a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:49:47Z"
    - latency: 4.853188ms
      message: 'load-balancer-api-external: tcp connection to a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:47Z"
    - latency: 8.370595ms
      message: 'load-balancer-api-external: resolved host name a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:48:47Z"
    - latency: 4.98679ms
      message: 'load-balancer-api-external: tcp connection to a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:47Z"
    - latency: 7.796108ms
      message: 'load-balancer-api-external: resolved host name a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:47:47Z"
    - latency: 4.521019ms
      message: 'load-balancer-api-external: tcp connection to a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:47Z"
    - latency: 8.512965ms
      message: 'load-balancer-api-external: resolved host name a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:46:47Z"
    - latency: 4.380287ms
      message: 'load-balancer-api-external: tcp connection to a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:45:47Z"
    - latency: 7.8561ms
      message: 'load-balancer-api-external: resolved host name a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:45:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-151-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-151.ec2.internal
      uid: 50b0f706-3634-431e-a701-08fc016ff292
    resourceVersion: "38979"
    uid: 9439feb9-7e7b-41c0-be51-ad0dcbd5152f
  spec:
    sourcePod: network-check-source-7cbc45fddc-txn98
    targetEndpoint: a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:07:47Z"
      message: 'load-balancer-api-internal: tcp connection to a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.480188ms
      message: 'load-balancer-api-internal: tcp connection to a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:49:47Z"
    - latency: 8.385603ms
      message: 'load-balancer-api-internal: resolved host name a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:49:47Z"
    - latency: 4.776765ms
      message: 'load-balancer-api-internal: tcp connection to a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:47Z"
    - latency: 8.338882ms
      message: 'load-balancer-api-internal: resolved host name a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:48:47Z"
    - latency: 4.928463ms
      message: 'load-balancer-api-internal: tcp connection to a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:47Z"
    - latency: 7.830244ms
      message: 'load-balancer-api-internal: resolved host name a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:47:47Z"
    - latency: 4.473123ms
      message: 'load-balancer-api-internal: tcp connection to a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:47Z"
    - latency: 8.601137ms
      message: 'load-balancer-api-internal: resolved host name a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:46:47Z"
    - latency: 5.533261ms
      message: 'load-balancer-api-internal: tcp connection to a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:45:47Z"
    - latency: 7.909242ms
      message: 'load-balancer-api-internal: resolved host name a510764274f7845118e62325a35fc9f7-36d522a67121177b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:45:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-151-to-network-check-target-ip-10-0-128-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-151.ec2.internal
      uid: 50b0f706-3634-431e-a701-08fc016ff292
    resourceVersion: "39535"
    uid: 5ae46277-37b4-461e-af1e-44cb8d5e3f0b
  spec:
    sourcePod: network-check-source-7cbc45fddc-txn98
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:08:47Z"
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.454067ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:50:47Z"
    - latency: 2.068871ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:49:47Z"
    - latency: 2.284607ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:47Z"
    - latency: 2.048371ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:47Z"
    - latency: 1.853151ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:47Z"
    - latency: 1.959195ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:45:47Z"
    - latency: 2.244869ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:44:47Z"
    - latency: 2.052851ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:43:47Z"
    - latency: 1.828869ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:42:47Z"
    - latency: 2.048492ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-151-to-network-check-target-ip-10-0-133-151
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-151.ec2.internal
      uid: 50b0f706-3634-431e-a701-08fc016ff292
    resourceVersion: "39533"
    uid: be8c08fc-455d-4f98-a09f-3ebdc0a1f8aa
  spec:
    sourcePod: network-check-source-7cbc45fddc-txn98
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:08:47Z"
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.274744ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:50:47Z"
    - latency: 1.023141ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:49:47Z"
    - latency: 1.395234ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:47Z"
    - latency: 1.442613ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:47Z"
    - latency: 872.739µs
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:47Z"
    - latency: 1.560183ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:45:47Z"
    - latency: 874.533µs
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:44:47Z"
    - latency: 878.185µs
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:43:47Z"
    - latency: 876.724µs
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:42:47Z"
    - latency: 889.583µs
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-151-to-network-check-target-ip-10-0-137-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-151.ec2.internal
      uid: 50b0f706-3634-431e-a701-08fc016ff292
    resourceVersion: "39534"
    uid: cebdfddc-987a-4875-8ebb-8b8a492d8311
  spec:
    sourcePod: network-check-source-7cbc45fddc-txn98
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:08:47Z"
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.908923ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:50:47Z"
    - latency: 2.432528ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:49:47Z"
    - latency: 2.356104ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:47Z"
    - latency: 2.536942ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:47Z"
    - latency: 2.321709ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:47Z"
    - latency: 2.535415ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:45:47Z"
    - latency: 2.420658ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:44:47Z"
    - latency: 2.382477ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:43:47Z"
    - latency: 2.266676ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:42:47Z"
    - latency: 2.364518ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-151-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-151.ec2.internal
      uid: 50b0f706-3634-431e-a701-08fc016ff292
    resourceVersion: "38978"
    uid: f5a4abd6-4e99-4e30-852e-91a4a6f55e81
  spec:
    sourcePod: network-check-source-7cbc45fddc-txn98
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:07:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.243µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:49:47Z"
    - latency: 1.691917ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:49:47Z"
    - latency: 868.337µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:47Z"
    - latency: 1.939111ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:48:47Z"
    - latency: 902.861µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:47Z"
    - latency: 1.711177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:47:47Z"
    - latency: 1.110242ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:47Z"
    - latency: 1.69621ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:46:47Z"
    - latency: 829.922µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:45:47Z"
    - latency: 2.055368ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:45:47Z"
kind: List
metadata:
  resourceVersion: ""