apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:21:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-235-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-235.ec2.internal
      uid: 267c1bb2-a13f-451c-8914-e19616fa14d6
    resourceVersion: "53312"
    uid: f3c5a263-6a40-4e77-bb34-68412340ab4f
  spec:
    sourcePod: network-check-source-6f8b768455-q44g9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:28:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.073675ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:49:09Z"
    - latency: 1.380134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:48:09Z"
    - latency: 1.464157ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:47:09Z"
    - latency: 1.301815ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:46:09Z"
    - latency: 970.287µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:45:09Z"
    - latency: 1.167322ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:44:09Z"
    - latency: 1.174473ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:43:09Z"
    - latency: 1.654541ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:42:09Z"
    - latency: 1.089705ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:41:09Z"
    - latency: 964.892µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:40:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:21:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-235-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-235.ec2.internal
      uid: 267c1bb2-a13f-451c-8914-e19616fa14d6
    resourceVersion: "54778"
    uid: e09a4f3b-6f55-4fcb-a79a-87b96de11d7f
  spec:
    sourcePod: network-check-source-6f8b768455-q44g9
    targetEndpoint: a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:27:09Z"
      message: 'load-balancer-api-external: tcp connection to a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.310817ms
      message: 'load-balancer-api-external: tcp connection to a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:51:09Z"
    - latency: 10.903536ms
      message: 'load-balancer-api-external: resolved host name a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:51:09Z"
    - latency: 3.779777ms
      message: 'load-balancer-api-external: tcp connection to a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:50:09Z"
    - latency: 12.629705ms
      message: 'load-balancer-api-external: resolved host name a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:50:09Z"
    - latency: 4.70243ms
      message: 'load-balancer-api-external: tcp connection to a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:49:09Z"
    - latency: 12.467529ms
      message: 'load-balancer-api-external: resolved host name a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:49:09Z"
    - latency: 4.924931ms
      message: 'load-balancer-api-external: tcp connection to a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:48:09Z"
    - latency: 10.999533ms
      message: 'load-balancer-api-external: resolved host name a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:48:09Z"
    - latency: 4.623103ms
      message: 'load-balancer-api-external: tcp connection to a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:47:09Z"
    - latency: 8.667849ms
      message: 'load-balancer-api-external: resolved host name a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:47:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:21:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-235-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-235.ec2.internal
      uid: 267c1bb2-a13f-451c-8914-e19616fa14d6
    resourceVersion: "54777"
    uid: f6ae29da-e77d-4fa2-881f-bd797208095d
  spec:
    sourcePod: network-check-source-6f8b768455-q44g9
    targetEndpoint: a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:27:09Z"
      message: 'load-balancer-api-internal: tcp connection to a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.746629ms
      message: 'load-balancer-api-internal: tcp connection to a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:51:09Z"
    - latency: 10.975803ms
      message: 'load-balancer-api-internal: resolved host name a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:51:09Z"
    - latency: 3.798123ms
      message: 'load-balancer-api-internal: tcp connection to a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:50:09Z"
    - latency: 12.705461ms
      message: 'load-balancer-api-internal: resolved host name a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:50:09Z"
    - latency: 4.726163ms
      message: 'load-balancer-api-internal: tcp connection to a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:49:09Z"
    - latency: 12.556693ms
      message: 'load-balancer-api-internal: resolved host name a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:49:09Z"
    - latency: 3.725346ms
      message: 'load-balancer-api-internal: tcp connection to a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:48:09Z"
    - latency: 11.022027ms
      message: 'load-balancer-api-internal: resolved host name a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:48:09Z"
    - latency: 4.036451ms
      message: 'load-balancer-api-internal: tcp connection to a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:47:09Z"
    - latency: 8.56698ms
      message: 'load-balancer-api-internal: resolved host name a2b9cc20bac294f1cbe2b8ac1a0ac70d-f52f8a83e8b2418f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:47:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:21:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-235-to-network-check-target-ip-10-0-132-115
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-235.ec2.internal
      uid: 267c1bb2-a13f-451c-8914-e19616fa14d6
    resourceVersion: "53311"
    uid: 6f878511-0fb7-4828-91fa-b3e7590aa5d6
  spec:
    sourcePod: network-check-source-6f8b768455-q44g9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:28:09Z"
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.398011ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:49:09Z"
    - latency: 2.274699ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:48:09Z"
    - latency: 2.523527ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:47:09Z"
    - latency: 2.508648ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:46:09Z"
    - latency: 1.94397ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:45:09Z"
    - latency: 1.984701ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:44:09Z"
    - latency: 2.245743ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:43:09Z"
    - latency: 2.530244ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:42:09Z"
    - latency: 2.572957ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:41:09Z"
    - latency: 2.215089ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:40:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:21:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-235-to-network-check-target-ip-10-0-132-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-235.ec2.internal
      uid: 267c1bb2-a13f-451c-8914-e19616fa14d6
    resourceVersion: "53309"
    uid: 1b784b62-89e6-465e-8e16-b43068a2f239
  spec:
    sourcePod: network-check-source-6f8b768455-q44g9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:28:09Z"
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.577833ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:49:09Z"
    - latency: 2.435792ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:48:09Z"
    - latency: 2.501891ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:47:09Z"
    - latency: 2.298091ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:46:09Z"
    - latency: 2.622656ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:45:09Z"
    - latency: 2.222264ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:44:09Z"
    - latency: 2.451345ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:43:09Z"
    - latency: 2.298244ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:42:09Z"
    - latency: 2.683494ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:41:09Z"
    - latency: 2.365655ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:40:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:21:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-235-to-network-check-target-ip-10-0-142-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-235.ec2.internal
      uid: 267c1bb2-a13f-451c-8914-e19616fa14d6
    resourceVersion: "53310"
    uid: f21444d7-d927-4ad5-b08b-24da3a7bd199
  spec:
    sourcePod: network-check-source-6f8b768455-q44g9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:28:09Z"
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.114571ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:49:09Z"
    - latency: 928.101µs
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:48:09Z"
    - latency: 1.163324ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:47:09Z"
    - latency: 986.066µs
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:46:09Z"
    - latency: 1.004905ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:45:09Z"
    - latency: 1.153092ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:44:09Z"
    - latency: 1.044593ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:43:09Z"
    - latency: 909.194µs
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:42:09Z"
    - latency: 994.045µs
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:41:09Z"
    - latency: 2.467728ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:40:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:21:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-235-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-235.ec2.internal
      uid: 267c1bb2-a13f-451c-8914-e19616fa14d6
    resourceVersion: "54775"
    uid: 155c8861-d882-4893-b635-103442f46926
  spec:
    sourcePod: network-check-source-6f8b768455-q44g9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:27:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.298298ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:51:09Z"
    - latency: 1.936769ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:51:09Z"
    - latency: 1.034674ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:50:09Z"
    - latency: 1.955751ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:50:09Z"
    - latency: 902.533µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:49:09Z"
    - latency: 2.2882ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:49:09Z"
    - latency: 1.272764ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:48:09Z"
    - latency: 2.140379ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:48:09Z"
    - latency: 1.325914ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:47:09Z"
    - latency: 2.094188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:47:09Z"
kind: List
metadata:
  resourceVersion: ""