apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-133-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-133.ec2.internal
      uid: 3049428e-52dc-46c5-b6d9-6ff5d43e57f9
    resourceVersion: "32890"
    uid: cc757646-c954-447f-a5dd-f0b4a4885b2d
  spec:
    sourcePod: network-check-source-dbd9cf844-kldp8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T23:02:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 963.315µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:09:12Z"
    - latency: 1.227164ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:08:12Z"
    - latency: 1.102477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:07:12Z"
    - latency: 1.383998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:06:12Z"
    - latency: 1.1445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:05:12Z"
    - latency: 1.105878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:04:12Z"
    - latency: 1.500965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:03:12Z"
    - latency: 1.262031ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:02:12Z"
    - latency: 924.481µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:01:12Z"
    - latency: 1.065021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-133-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-133.ec2.internal
      uid: 3049428e-52dc-46c5-b6d9-6ff5d43e57f9
    resourceVersion: "36602"
    uid: 36335e49-03c3-4d6e-b5a2-565d6c089100
  spec:
    sourcePod: network-check-source-dbd9cf844-kldp8
    targetEndpoint: a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T23:01:12Z"
      message: 'load-balancer-api-external: tcp connection to a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.464106ms
      message: 'load-balancer-api-external: tcp connection to a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:13:12Z"
    - latency: 7.287363ms
      message: 'load-balancer-api-external: resolved host name a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:13:12Z"
    - latency: 4.323462ms
      message: 'load-balancer-api-external: tcp connection to a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:12:12Z"
    - latency: 6.546009ms
      message: 'load-balancer-api-external: resolved host name a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:12:12Z"
    - latency: 6.238262ms
      message: 'load-balancer-api-external: tcp connection to a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:11:12Z"
    - latency: 6.713683ms
      message: 'load-balancer-api-external: resolved host name a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:11:12Z"
    - latency: 5.888118ms
      message: 'load-balancer-api-external: tcp connection to a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:10:12Z"
    - latency: 6.93667ms
      message: 'load-balancer-api-external: resolved host name a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:10:12Z"
    - latency: 6.00209ms
      message: 'load-balancer-api-external: tcp connection to a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:09:12Z"
    - latency: 7.837693ms
      message: 'load-balancer-api-external: resolved host name a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:09:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-133-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-133.ec2.internal
      uid: 3049428e-52dc-46c5-b6d9-6ff5d43e57f9
    resourceVersion: "36601"
    uid: 58207724-2bcf-4b97-8f56-673f3fd27b6f
  spec:
    sourcePod: network-check-source-dbd9cf844-kldp8
    targetEndpoint: a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T23:01:12Z"
      message: 'load-balancer-api-internal: tcp connection to a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.532454ms
      message: 'load-balancer-api-internal: tcp connection to a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:13:12Z"
    - latency: 7.374574ms
      message: 'load-balancer-api-internal: resolved host name a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:13:12Z"
    - latency: 5.553486ms
      message: 'load-balancer-api-internal: tcp connection to a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:12:12Z"
    - latency: 6.271899ms
      message: 'load-balancer-api-internal: resolved host name a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:12:12Z"
    - latency: 4.064405ms
      message: 'load-balancer-api-internal: tcp connection to a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:11:12Z"
    - latency: 6.784807ms
      message: 'load-balancer-api-internal: resolved host name a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:11:12Z"
    - latency: 5.874751ms
      message: 'load-balancer-api-internal: tcp connection to a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:10:12Z"
    - latency: 6.991477ms
      message: 'load-balancer-api-internal: resolved host name a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:10:12Z"
    - latency: 6.015072ms
      message: 'load-balancer-api-internal: tcp connection to a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:09:12Z"
    - latency: 7.906628ms
      message: 'load-balancer-api-internal: resolved host name a742e7681b3f44a85b3e1a6dc6e1dc09-36c1d57d35c09a7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:09:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-133-to-network-check-target-ip-10-0-138-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-133.ec2.internal
      uid: 3049428e-52dc-46c5-b6d9-6ff5d43e57f9
    resourceVersion: "32889"
    uid: 8c5a7704-e21a-4c9d-ac2c-5179057a1c60
  spec:
    sourcePod: network-check-source-dbd9cf844-kldp8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T23:02:12Z"
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.613324ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:09:12Z"
    - latency: 2.448136ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:08:12Z"
    - latency: 2.097838ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:07:12Z"
    - latency: 2.208069ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:06:12Z"
    - latency: 2.159804ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:05:12Z"
    - latency: 2.39498ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:04:12Z"
    - latency: 2.589269ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:03:12Z"
    - latency: 2.335171ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:02:12Z"
    - latency: 2.075604ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:01:12Z"
    - latency: 2.092656ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-133-to-network-check-target-ip-10-0-141-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-133.ec2.internal
      uid: 3049428e-52dc-46c5-b6d9-6ff5d43e57f9
    resourceVersion: "32887"
    uid: eba2b1c2-95b4-4f79-8dea-61ffe5edf9bf
  spec:
    sourcePod: network-check-source-dbd9cf844-kldp8
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T23:02:12Z"
      message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.73435ms
      message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:09:12Z"
    - latency: 1.17092ms
      message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:08:12Z"
    - latency: 954.686µs
      message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:07:12Z"
    - latency: 927.734µs
      message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:06:12Z"
    - latency: 962.274µs
      message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:05:12Z"
    - latency: 1.068183ms
      message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:04:12Z"
    - latency: 1.099446ms
      message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:03:12Z"
    - latency: 1.007849ms
      message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:02:12Z"
    - latency: 959.44µs
      message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:01:12Z"
    - latency: 958.594µs
      message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-133-to-network-check-target-ip-10-0-141-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-133.ec2.internal
      uid: 3049428e-52dc-46c5-b6d9-6ff5d43e57f9
    resourceVersion: "32888"
    uid: c2e49fda-648c-45c1-bf00-4d62a8fce050
  spec:
    sourcePod: network-check-source-dbd9cf844-kldp8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T23:02:12Z"
      message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.690631ms
      message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:09:12Z"
    - latency: 2.526ms
      message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:08:12Z"
    - latency: 2.303698ms
      message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:07:12Z"
    - latency: 2.205259ms
      message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:06:12Z"
    - latency: 2.006693ms
      message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:05:12Z"
    - latency: 2.503668ms
      message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:04:12Z"
    - latency: 2.386136ms
      message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:03:12Z"
    - latency: 2.386779ms
      message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:02:12Z"
    - latency: 2.318854ms
      message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:01:12Z"
    - latency: 2.385033ms
      message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:55:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-133-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-133.ec2.internal
      uid: 3049428e-52dc-46c5-b6d9-6ff5d43e57f9
    resourceVersion: "36599"
    uid: c2aea8ec-9739-471a-a2aa-c65187430c66
  spec:
    sourcePod: network-check-source-dbd9cf844-kldp8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T23:01:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.99µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:13:12Z"
    - latency: 1.645013ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:13:12Z"
    - latency: 959.421µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:12:12Z"
    - latency: 1.805859ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:12:12Z"
    - latency: 1.013057ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:11:12Z"
    - latency: 1.652074ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:11:12Z"
    - latency: 882.228µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:10:12Z"
    - latency: 1.883267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:10:12Z"
    - latency: 919.522µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T23:09:12Z"
    - latency: 2.601441ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T23:09:12Z"
kind: List
metadata:
  resourceVersion: ""