apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:00:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-221-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-221.ec2.internal
      uid: 4389fe70-c3c9-472e-9aa9-e2f202329e4e
    resourceVersion: "67000"
    uid: e561143e-c6a3-49a9-99d8-c9aa94c46b56
  spec:
    sourcePod: network-check-source-6f8b768455-lzdl4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:07:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.002152ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:35:53Z"
    - latency: 1.208089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:34:53Z"
    - latency: 1.4383ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:33:53Z"
    - latency: 947.918µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:32:53Z"
    - latency: 1.426351ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:31:53Z"
    - latency: 960.703µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:30:53Z"
    - latency: 1.010735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:29:53Z"
    - latency: 1.013738ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:28:53Z"
    - latency: 1.008786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:27:53Z"
    - latency: 1.362724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:26:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:00:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-221-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-221.ec2.internal
      uid: 4389fe70-c3c9-472e-9aa9-e2f202329e4e
    resourceVersion: "67957"
    uid: bc8adb54-a460-46bd-ad2b-a667a31c342d
  spec:
    sourcePod: network-check-source-6f8b768455-lzdl4
    targetEndpoint: a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:06:53Z"
      message: 'load-balancer-api-external: tcp connection to a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.682304ms
      message: 'load-balancer-api-external: tcp connection to a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:36:53Z"
    - latency: 20.318041ms
      message: 'load-balancer-api-external: resolved host name a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:36:53Z"
    - latency: 4.197652ms
      message: 'load-balancer-api-external: tcp connection to a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:35:53Z"
    - latency: 8.296831ms
      message: 'load-balancer-api-external: resolved host name a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:35:53Z"
    - latency: 4.76188ms
      message: 'load-balancer-api-external: tcp connection to a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:34:53Z"
    - latency: 9.079553ms
      message: 'load-balancer-api-external: resolved host name a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:34:53Z"
    - latency: 5.520083ms
      message: 'load-balancer-api-external: tcp connection to a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:33:53Z"
    - latency: 15.486123ms
      message: 'load-balancer-api-external: resolved host name a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:33:53Z"
    - latency: 4.410726ms
      message: 'load-balancer-api-external: tcp connection to a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:32:53Z"
    - latency: 8.827398ms
      message: 'load-balancer-api-external: resolved host name a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:32:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:00:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-221-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-221.ec2.internal
      uid: 4389fe70-c3c9-472e-9aa9-e2f202329e4e
    resourceVersion: "67956"
    uid: a5a29729-07f6-4d61-bdb8-76a3441649f4
  spec:
    sourcePod: network-check-source-6f8b768455-lzdl4
    targetEndpoint: a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:06:53Z"
      message: 'load-balancer-api-internal: tcp connection to a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.698203ms
      message: 'load-balancer-api-internal: tcp connection to a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:36:53Z"
    - latency: 20.279666ms
      message: 'load-balancer-api-internal: resolved host name a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:36:53Z"
    - latency: 4.124879ms
      message: 'load-balancer-api-internal: tcp connection to a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:35:53Z"
    - latency: 8.252207ms
      message: 'load-balancer-api-internal: resolved host name a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:35:53Z"
    - latency: 4.43342ms
      message: 'load-balancer-api-internal: tcp connection to a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:34:53Z"
    - latency: 9.067058ms
      message: 'load-balancer-api-internal: resolved host name a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:34:53Z"
    - latency: 5.440784ms
      message: 'load-balancer-api-internal: tcp connection to a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:33:53Z"
    - latency: 15.528629ms
      message: 'load-balancer-api-internal: resolved host name a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:33:53Z"
    - latency: 4.524495ms
      message: 'load-balancer-api-internal: tcp connection to a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:32:53Z"
    - latency: 8.787393ms
      message: 'load-balancer-api-internal: resolved host name a42a921c2b0af4fc1a9bb6e41f51f822-cd5aadca895c8449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:32:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:00:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-221-to-network-check-target-ip-10-0-131-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-221.ec2.internal
      uid: 4389fe70-c3c9-472e-9aa9-e2f202329e4e
    resourceVersion: "66998"
    uid: 7451c8e3-3720-4cae-b854-ff0b25c9dd0e
  spec:
    sourcePod: network-check-source-6f8b768455-lzdl4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:07:53Z"
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.142542ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:35:53Z"
    - latency: 2.544108ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:34:53Z"
    - latency: 2.532828ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:33:53Z"
    - latency: 2.443565ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:32:53Z"
    - latency: 2.35724ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:31:53Z"
    - latency: 2.671912ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:30:53Z"
    - latency: 2.185814ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:29:53Z"
    - latency: 2.475418ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:28:53Z"
    - latency: 3.111819ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:27:53Z"
    - latency: 2.70478ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:26:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:00:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-221-to-network-check-target-ip-10-0-138-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-221.ec2.internal
      uid: 4389fe70-c3c9-472e-9aa9-e2f202329e4e
    resourceVersion: "66997"
    uid: 668129a4-4596-46b1-8560-1a24df35b94b
  spec:
    sourcePod: network-check-source-6f8b768455-lzdl4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:07:53Z"
      message: 'network-check-target-ip-10-0-138-221: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.845µs
      message: 'network-check-target-ip-10-0-138-221: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:35:53Z"
    - latency: 940.376µs
      message: 'network-check-target-ip-10-0-138-221: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:34:53Z"
    - latency: 862.965µs
      message: 'network-check-target-ip-10-0-138-221: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:33:53Z"
    - latency: 887.073µs
      message: 'network-check-target-ip-10-0-138-221: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:32:53Z"
    - latency: 1.195326ms
      message: 'network-check-target-ip-10-0-138-221: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:31:53Z"
    - latency: 1.000432ms
      message: 'network-check-target-ip-10-0-138-221: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:30:53Z"
    - latency: 1.164054ms
      message: 'network-check-target-ip-10-0-138-221: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:29:53Z"
    - latency: 960.876µs
      message: 'network-check-target-ip-10-0-138-221: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:28:53Z"
    - latency: 1.402868ms
      message: 'network-check-target-ip-10-0-138-221: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:27:53Z"
    - latency: 1.616762ms
      message: 'network-check-target-ip-10-0-138-221: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:26:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:00:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-221-to-network-check-target-ip-10-0-142-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-221.ec2.internal
      uid: 4389fe70-c3c9-472e-9aa9-e2f202329e4e
    resourceVersion: "66999"
    uid: 00e1eac7-b323-411d-8e6b-7425899ce78f
  spec:
    sourcePod: network-check-source-6f8b768455-lzdl4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:07:53Z"
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.185616ms
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:35:53Z"
    - latency: 2.583241ms
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:34:53Z"
    - latency: 2.356293ms
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:33:53Z"
    - latency: 2.255255ms
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:32:53Z"
    - latency: 2.324468ms
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:31:53Z"
    - latency: 2.329518ms
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:30:53Z"
    - latency: 2.290043ms
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:29:53Z"
    - latency: 2.652078ms
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:28:53Z"
    - latency: 2.44804ms
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:27:53Z"
    - latency: 2.553173ms
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:26:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:00:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-221-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-221.ec2.internal
      uid: 4389fe70-c3c9-472e-9aa9-e2f202329e4e
    resourceVersion: "67955"
    uid: b49cc142-a25d-46cc-8b14-d37c0fca9000
  spec:
    sourcePod: network-check-source-6f8b768455-lzdl4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:06:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.096606ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:36:53Z"
    - latency: 1.802637ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:36:53Z"
    - latency: 960.534µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:35:53Z"
    - latency: 1.715127ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:35:53Z"
    - latency: 1.528866ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:34:53Z"
    - latency: 1.878657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:34:53Z"
    - latency: 920.502µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:33:53Z"
    - latency: 2.233239ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:33:53Z"
    - latency: 972.837µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:32:53Z"
    - latency: 1.921723ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:32:53Z"
kind: List
metadata:
  resourceVersion: ""