apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:54:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-126-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-126.ec2.internal
      uid: 16bbb2c7-9635-491f-a3c4-d8e0341cdfdc
    resourceVersion: "60546"
    uid: 5fccff8b-755c-419e-baed-90a9b3a65689
  spec:
    sourcePod: network-check-source-869dcfcdcd-f79ht
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:01:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.151929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:36:10Z"
    - latency: 815.565µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:10Z"
    - latency: 1.010501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:10Z"
    - latency: 1.074742ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:10Z"
    - latency: 963.911µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:10Z"
    - latency: 801.209µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:31:10Z"
    - latency: 1.014007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:30:10Z"
    - latency: 781.345µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:29:10Z"
    - latency: 964.822µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:28:10Z"
    - latency: 1.089119ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:27:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:54:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-126-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-126.ec2.internal
      uid: 16bbb2c7-9635-491f-a3c4-d8e0341cdfdc
    resourceVersion: "60547"
    uid: c7ed365a-df5b-41cd-a5db-18e9df4097cd
  spec:
    sourcePod: network-check-source-869dcfcdcd-f79ht
    targetEndpoint: aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:00:10Z"
      message: 'load-balancer-api-external: tcp connection to aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.040084ms
      message: 'load-balancer-api-external: tcp connection to aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:36:10Z"
    - latency: 6.796472ms
      message: 'load-balancer-api-external: resolved host name aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:36:10Z"
    - latency: 4.544744ms
      message: 'load-balancer-api-external: tcp connection to aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:10Z"
    - latency: 7.63509ms
      message: 'load-balancer-api-external: resolved host name aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:35:10Z"
    - latency: 4.079196ms
      message: 'load-balancer-api-external: tcp connection to aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:10Z"
    - latency: 8.756518ms
      message: 'load-balancer-api-external: resolved host name aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:34:10Z"
    - latency: 4.363328ms
      message: 'load-balancer-api-external: tcp connection to aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:10Z"
    - latency: 8.379495ms
      message: 'load-balancer-api-external: resolved host name aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:33:10Z"
    - latency: 4.038314ms
      message: 'load-balancer-api-external: tcp connection to aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:10Z"
    - latency: 10.960626ms
      message: 'load-balancer-api-external: resolved host name aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:32:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:54:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-126-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-126.ec2.internal
      uid: 16bbb2c7-9635-491f-a3c4-d8e0341cdfdc
    resourceVersion: "60548"
    uid: a613e0a2-c959-4e82-a18c-00f1edcdbc22
  spec:
    sourcePod: network-check-source-869dcfcdcd-f79ht
    targetEndpoint: aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:00:10Z"
      message: 'load-balancer-api-internal: tcp connection to aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.022525ms
      message: 'load-balancer-api-internal: tcp connection to aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:36:10Z"
    - latency: 6.733642ms
      message: 'load-balancer-api-internal: resolved host name aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:36:10Z"
    - latency: 4.550846ms
      message: 'load-balancer-api-internal: tcp connection to aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:10Z"
    - latency: 7.663ms
      message: 'load-balancer-api-internal: resolved host name aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:35:10Z"
    - latency: 4.119462ms
      message: 'load-balancer-api-internal: tcp connection to aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:10Z"
    - latency: 8.701358ms
      message: 'load-balancer-api-internal: resolved host name aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:34:10Z"
    - latency: 4.35771ms
      message: 'load-balancer-api-internal: tcp connection to aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:10Z"
    - latency: 8.454085ms
      message: 'load-balancer-api-internal: resolved host name aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:33:10Z"
    - latency: 4.244337ms
      message: 'load-balancer-api-internal: tcp connection to aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:10Z"
    - latency: 10.920783ms
      message: 'load-balancer-api-internal: resolved host name aabc2e18cc2bb4434842741c17388f25-5a02c7ef88721b64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:32:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:54:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-126-to-network-check-target-ip-10-0-130-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-126.ec2.internal
      uid: 16bbb2c7-9635-491f-a3c4-d8e0341cdfdc
    resourceVersion: "60544"
    uid: a003154f-f655-47ab-9e75-1c341e6d98ba
  spec:
    sourcePod: network-check-source-869dcfcdcd-f79ht
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:01:10Z"
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.469446ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:36:10Z"
    - latency: 2.530245ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:10Z"
    - latency: 2.426919ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:10Z"
    - latency: 2.707722ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:10Z"
    - latency: 2.436492ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:10Z"
    - latency: 2.433074ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:31:10Z"
    - latency: 2.657206ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:30:10Z"
    - latency: 2.300939ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:29:10Z"
    - latency: 2.465003ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:28:10Z"
    - latency: 2.448803ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:27:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:54:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-126-to-network-check-target-ip-10-0-141-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-126.ec2.internal
      uid: 16bbb2c7-9635-491f-a3c4-d8e0341cdfdc
    resourceVersion: "60543"
    uid: 6dc18a51-62c7-4017-ba38-322c0a435e91
  spec:
    sourcePod: network-check-source-869dcfcdcd-f79ht
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:01:10Z"
      message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.251602ms
      message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:36:10Z"
    - latency: 2.549405ms
      message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:10Z"
    - latency: 2.089083ms
      message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:10Z"
    - latency: 2.320221ms
      message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:10Z"
    - latency: 2.474156ms
      message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:10Z"
    - latency: 2.554582ms
      message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:31:10Z"
    - latency: 2.256648ms
      message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:30:10Z"
    - latency: 2.329424ms
      message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:29:10Z"
    - latency: 2.613291ms
      message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:28:10Z"
    - latency: 2.238317ms
      message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:27:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:54:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-126-to-network-check-target-ip-10-0-142-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-126.ec2.internal
      uid: 16bbb2c7-9635-491f-a3c4-d8e0341cdfdc
    resourceVersion: "60542"
    uid: a1857cb2-4819-4776-9607-8d657affe32e
  spec:
    sourcePod: network-check-source-869dcfcdcd-f79ht
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:01:10Z"
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.992µs
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:36:10Z"
    - latency: 1.255388ms
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:10Z"
    - latency: 917.546µs
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:10Z"
    - latency: 876.24µs
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:10Z"
    - latency: 800.142µs
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:10Z"
    - latency: 901.935µs
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:31:10Z"
    - latency: 908.163µs
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:30:10Z"
    - latency: 903.409µs
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:29:10Z"
    - latency: 845.586µs
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:28:10Z"
    - latency: 900.744µs
      message: 'network-check-target-ip-10-0-142-126: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:27:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:54:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-126-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-126.ec2.internal
      uid: 16bbb2c7-9635-491f-a3c4-d8e0341cdfdc
    resourceVersion: "60545"
    uid: 94b5bf72-1fce-438c-ad39-482e20f845c4
  spec:
    sourcePod: network-check-source-869dcfcdcd-f79ht
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:00:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 815.138µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:36:10Z"
    - latency: 1.945647ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:36:10Z"
    - latency: 892.825µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:10Z"
    - latency: 1.605382ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:35:10Z"
    - latency: 880.332µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:10Z"
    - latency: 1.678508ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:34:10Z"
    - latency: 910.689µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:10Z"
    - latency: 1.743816ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:33:10Z"
    - latency: 775.46µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:10Z"
    - latency: 1.643148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:32:10Z"
kind: List
metadata:
  resourceVersion: ""