apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:16:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-66-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-66.ec2.internal
      uid: 4833299f-5292-4520-838b-6e7027db5e68
    resourceVersion: "78080"
    uid: 3ca9ef50-bf3c-4b78-b9ae-4da432bf98fc
  spec:
    sourcePod: network-check-source-7cbc45fddc-kn5mt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:23:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.071789ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:19:46Z"
    - latency: 986.871µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:18:46Z"
    - latency: 972.497µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:17:46Z"
    - latency: 1.014859ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:16:46Z"
    - latency: 1.656504ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:15:46Z"
    - latency: 1.106599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:14:46Z"
    - latency: 1.260829ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:13:46Z"
    - latency: 1.093374ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:12:46Z"
    - latency: 1.044614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:11:46Z"
    - latency: 1.305704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:10:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:16:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-66-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-66.ec2.internal
      uid: 4833299f-5292-4520-838b-6e7027db5e68
    resourceVersion: "74513"
    uid: 0df11ded-e9bf-4fcd-a411-44bd31c7ab92
  spec:
    sourcePod: network-check-source-7cbc45fddc-kn5mt
    targetEndpoint: a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:22:46Z"
      message: 'load-balancer-api-external: tcp connection to a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.452965ms
      message: 'load-balancer-api-external: tcp connection to a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:16:46Z"
    - latency: 8.184986ms
      message: 'load-balancer-api-external: resolved host name a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:16:46Z"
    - latency: 3.975079ms
      message: 'load-balancer-api-external: tcp connection to a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:15:46Z"
    - latency: 12.615709ms
      message: 'load-balancer-api-external: resolved host name a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:15:46Z"
    - latency: 4.454882ms
      message: 'load-balancer-api-external: tcp connection to a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:14:46Z"
    - latency: 9.227591ms
      message: 'load-balancer-api-external: resolved host name a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:14:46Z"
    - latency: 4.907236ms
      message: 'load-balancer-api-external: tcp connection to a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:13:46Z"
    - latency: 8.56773ms
      message: 'load-balancer-api-external: resolved host name a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:13:46Z"
    - latency: 6.472605ms
      message: 'load-balancer-api-external: tcp connection to a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:12:46Z"
    - latency: 15.860038ms
      message: 'load-balancer-api-external: resolved host name a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:12:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:16:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-66-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-66.ec2.internal
      uid: 4833299f-5292-4520-838b-6e7027db5e68
    resourceVersion: "74514"
    uid: d84a7dbb-2515-40bd-a567-dd83345c0e4d
  spec:
    sourcePod: network-check-source-7cbc45fddc-kn5mt
    targetEndpoint: a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:22:46Z"
      message: 'load-balancer-api-internal: tcp connection to a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.801398ms
      message: 'load-balancer-api-internal: tcp connection to a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:16:46Z"
    - latency: 8.134083ms
      message: 'load-balancer-api-internal: resolved host name a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:16:46Z"
    - latency: 3.963718ms
      message: 'load-balancer-api-internal: tcp connection to a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:15:46Z"
    - latency: 12.6908ms
      message: 'load-balancer-api-internal: resolved host name a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:15:46Z"
    - latency: 4.50738ms
      message: 'load-balancer-api-internal: tcp connection to a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:14:46Z"
    - latency: 9.33812ms
      message: 'load-balancer-api-internal: resolved host name a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:14:46Z"
    - latency: 5.163363ms
      message: 'load-balancer-api-internal: tcp connection to a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:13:46Z"
    - latency: 8.481941ms
      message: 'load-balancer-api-internal: resolved host name a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:13:46Z"
    - latency: 5.737626ms
      message: 'load-balancer-api-internal: tcp connection to a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:12:46Z"
    - latency: 15.984034ms
      message: 'load-balancer-api-internal: resolved host name a0306ea8fabfa41f1bca6d8572f136de-a0b694fd169541f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:12:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:16:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-66-to-network-check-target-ip-10-0-132-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-66.ec2.internal
      uid: 4833299f-5292-4520-838b-6e7027db5e68
    resourceVersion: "78078"
    uid: 99d0a498-5411-4865-8938-28a0dd4a9beb
  spec:
    sourcePod: network-check-source-7cbc45fddc-kn5mt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:23:46Z"
      message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.99404ms
      message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:19:46Z"
    - latency: 2.279696ms
      message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:18:46Z"
    - latency: 2.169172ms
      message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:17:46Z"
    - latency: 2.369747ms
      message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:16:46Z"
    - latency: 2.425124ms
      message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:15:46Z"
    - latency: 2.452279ms
      message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:14:46Z"
    - latency: 2.135066ms
      message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:13:46Z"
    - latency: 2.679811ms
      message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:12:46Z"
    - latency: 2.410784ms
      message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:11:46Z"
    - latency: 2.414968ms
      message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:10:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:16:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-66-to-network-check-target-ip-10-0-132-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-66.ec2.internal
      uid: 4833299f-5292-4520-838b-6e7027db5e68
    resourceVersion: "78079"
    uid: 31ce918b-f707-468e-afc9-9671eebf1b74
  spec:
    sourcePod: network-check-source-7cbc45fddc-kn5mt
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:23:46Z"
      message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.239777ms
      message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:19:46Z"
    - latency: 3.74975ms
      message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:18:46Z"
    - latency: 2.183269ms
      message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:17:46Z"
    - latency: 2.285863ms
      message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:16:46Z"
    - latency: 2.385398ms
      message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:15:46Z"
    - latency: 2.200722ms
      message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:14:46Z"
    - latency: 2.183636ms
      message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:13:46Z"
    - latency: 2.558809ms
      message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:12:46Z"
    - latency: 2.688786ms
      message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:11:46Z"
    - latency: 2.194163ms
      message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:10:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:16:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-66-to-network-check-target-ip-10-0-134-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-66.ec2.internal
      uid: 4833299f-5292-4520-838b-6e7027db5e68
    resourceVersion: "78077"
    uid: 84f0b027-a386-4086-8455-20dd142ac043
  spec:
    sourcePod: network-check-source-7cbc45fddc-kn5mt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:23:46Z"
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.33253ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:19:46Z"
    - latency: 948.975µs
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:18:46Z"
    - latency: 977.773µs
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:17:46Z"
    - latency: 940.528µs
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:16:46Z"
    - latency: 1.181923ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:15:46Z"
    - latency: 1.131071ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:14:46Z"
    - latency: 986.521µs
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:13:46Z"
    - latency: 1.01649ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:12:46Z"
    - latency: 1.087956ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:11:46Z"
    - latency: 864.153µs
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:10:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:16:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-66-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-66.ec2.internal
      uid: 4833299f-5292-4520-838b-6e7027db5e68
    resourceVersion: "74512"
    uid: d3f265ef-59d5-462d-8d51-500d2e4a0f11
  spec:
    sourcePod: network-check-source-7cbc45fddc-kn5mt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:22:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.253338ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:16:46Z"
    - latency: 1.715285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:16:46Z"
    - latency: 902.128µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:15:46Z"
    - latency: 1.786485ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:15:46Z"
    - latency: 981.366µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:14:46Z"
    - latency: 2.107806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:14:46Z"
    - latency: 1.081295ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:13:46Z"
    - latency: 1.869175ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:13:46Z"
    - latency: 1.385392ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:12:46Z"
    - latency: 2.27197ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:12:46Z"
kind: List
metadata:
  resourceVersion: ""