apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:27:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-101-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-101.ec2.internal
      uid: 2b4603f9-d8c2-4147-919a-4298e38a84a2
    resourceVersion: "77835"
    uid: 8d2f83c3-e418-4448-8cc8-01c07db58ebd
  spec:
    sourcePod: network-check-source-7cbc45fddc-729fd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:34:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.040508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:30:24Z"
    - latency: 1.252309ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:29:24Z"
    - latency: 1.10724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:28:24Z"
    - latency: 1.852557ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:27:24Z"
    - latency: 1.111351ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:26:24Z"
    - latency: 1.043307ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:25:24Z"
    - latency: 1.106289ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:24:24Z"
    - latency: 1.045186ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:23:24Z"
    - latency: 1.639318ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:22:24Z"
    - latency: 990.827µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:21:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:27:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-101-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-101.ec2.internal
      uid: 2b4603f9-d8c2-4147-919a-4298e38a84a2
    resourceVersion: "80485"
    uid: aa09513c-4010-4ad3-919a-c59bf6e4d5be
  spec:
    sourcePod: network-check-source-7cbc45fddc-729fd
    targetEndpoint: a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:33:24Z"
      message: 'load-balancer-api-external: tcp connection to a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.571615ms
      message: 'load-balancer-api-external: tcp connection to a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:33:24Z"
    - latency: 9.532191ms
      message: 'load-balancer-api-external: resolved host name a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:33:24Z"
    - latency: 5.079901ms
      message: 'load-balancer-api-external: tcp connection to a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:32:24Z"
    - latency: 15.068968ms
      message: 'load-balancer-api-external: resolved host name a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:32:24Z"
    - latency: 9.688423ms
      message: 'load-balancer-api-external: tcp connection to a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:31:24Z"
    - latency: 9.01726ms
      message: 'load-balancer-api-external: resolved host name a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:31:24Z"
    - latency: 5.372807ms
      message: 'load-balancer-api-external: tcp connection to a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:30:24Z"
    - latency: 9.998654ms
      message: 'load-balancer-api-external: resolved host name a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:30:24Z"
    - latency: 7.194275ms
      message: 'load-balancer-api-external: tcp connection to a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:29:24Z"
    - latency: 9.823223ms
      message: 'load-balancer-api-external: resolved host name a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:29:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:27:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-101-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-101.ec2.internal
      uid: 2b4603f9-d8c2-4147-919a-4298e38a84a2
    resourceVersion: "80486"
    uid: fda7c51c-5690-4c61-bf04-06473b32809a
  spec:
    sourcePod: network-check-source-7cbc45fddc-729fd
    targetEndpoint: a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:33:24Z"
      message: 'load-balancer-api-internal: tcp connection to a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.550253ms
      message: 'load-balancer-api-internal: tcp connection to a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:33:24Z"
    - latency: 9.561073ms
      message: 'load-balancer-api-internal: resolved host name a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:33:24Z"
    - latency: 5.081194ms
      message: 'load-balancer-api-internal: tcp connection to a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:32:24Z"
    - latency: 15.130194ms
      message: 'load-balancer-api-internal: resolved host name a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:32:24Z"
    - latency: 7.954514ms
      message: 'load-balancer-api-internal: tcp connection to a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:31:24Z"
    - latency: 8.953751ms
      message: 'load-balancer-api-internal: resolved host name a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:31:24Z"
    - latency: 5.327342ms
      message: 'load-balancer-api-internal: tcp connection to a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:30:24Z"
    - latency: 10.048171ms
      message: 'load-balancer-api-internal: resolved host name a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:30:24Z"
    - latency: 6.689897ms
      message: 'load-balancer-api-internal: tcp connection to a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:29:24Z"
    - latency: 9.878227ms
      message: 'load-balancer-api-internal: resolved host name a7fcdc15a722d441d84d411110ab9c85-cc4f6123aed674b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:29:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:27:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-101-to-network-check-target-ip-10-0-130-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-101.ec2.internal
      uid: 2b4603f9-d8c2-4147-919a-4298e38a84a2
    resourceVersion: "77832"
    uid: 018ba8e0-1fee-45f7-915c-9328902ed604
  spec:
    sourcePod: network-check-source-7cbc45fddc-729fd
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:34:24Z"
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 975.771µs
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:30:24Z"
    - latency: 1.016322ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:29:24Z"
    - latency: 1.031215ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:28:24Z"
    - latency: 1.549537ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:27:24Z"
    - latency: 1.083889ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:26:24Z"
    - latency: 1.01383ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:25:24Z"
    - latency: 1.773822ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:24:24Z"
    - latency: 1.246077ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:23:24Z"
    - latency: 1.286574ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:22:24Z"
    - latency: 1.022688ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:21:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:27:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-101-to-network-check-target-ip-10-0-133-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-101.ec2.internal
      uid: 2b4603f9-d8c2-4147-919a-4298e38a84a2
    resourceVersion: "77833"
    uid: 7b75bacf-01fa-4f83-a5a5-62d91efe91de
  spec:
    sourcePod: network-check-source-7cbc45fddc-729fd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:34:24Z"
      message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.37349ms
      message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:30:24Z"
    - latency: 3.043965ms
      message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:29:24Z"
    - latency: 2.799225ms
      message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:28:24Z"
    - latency: 2.859713ms
      message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:27:24Z"
    - latency: 2.533982ms
      message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:26:24Z"
    - latency: 2.313146ms
      message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:25:24Z"
    - latency: 2.825202ms
      message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:24:24Z"
    - latency: 2.769071ms
      message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:23:24Z"
    - latency: 3.131006ms
      message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:22:24Z"
    - latency: 2.650051ms
      message: 'network-check-target-ip-10-0-133-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:21:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:27:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-101-to-network-check-target-ip-10-0-142-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-101.ec2.internal
      uid: 2b4603f9-d8c2-4147-919a-4298e38a84a2
    resourceVersion: "77834"
    uid: 5e9b01c4-e227-4226-8812-c3d44d50db4e
  spec:
    sourcePod: network-check-source-7cbc45fddc-729fd
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:34:24Z"
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.10694ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:30:24Z"
    - latency: 2.276187ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:29:24Z"
    - latency: 2.777442ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:28:24Z"
    - latency: 2.884935ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:27:24Z"
    - latency: 2.618633ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:26:24Z"
    - latency: 2.483635ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:25:24Z"
    - latency: 2.944555ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:24:24Z"
    - latency: 2.363213ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:23:24Z"
    - latency: 2.494524ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:22:24Z"
    - latency: 2.61789ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:21:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:27:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-101-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-101.ec2.internal
      uid: 2b4603f9-d8c2-4147-919a-4298e38a84a2
    resourceVersion: "80483"
    uid: 67b45293-543d-4b3a-8e39-11d03b7d1c44
  spec:
    sourcePod: network-check-source-7cbc45fddc-729fd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:33:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 943.609µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:33:24Z"
    - latency: 1.893264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:33:24Z"
    - latency: 1.210345ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:32:24Z"
    - latency: 2.366085ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:32:24Z"
    - latency: 1.004791ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:31:24Z"
    - latency: 1.992537ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:31:24Z"
    - latency: 1.274024ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:30:24Z"
    - latency: 1.998251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:30:24Z"
    - latency: 1.458248ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:29:24Z"
    - latency: 1.877929ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:29:24Z"
kind: List
metadata:
  resourceVersion: ""