apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:58:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: 45016917-3a90-4472-9a66-0d3cd2e3fa19
    resourceVersion: "23048"
    uid: 9a058fea-b890-4fcd-bc82-7e3d7965ae5b
  spec:
    sourcePod: network-check-source-7cbc45fddc-sgjwg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:05:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 999.05µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:26:56Z"
    - latency: 986.489µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:25:56Z"
    - latency: 844.949µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:24:56Z"
    - latency: 801.691µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:23:56Z"
    - latency: 1.217661ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:22:56Z"
    - latency: 783.459µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:21:56Z"
    - latency: 1.101323ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:20:56Z"
    - latency: 1.060036ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:19:56Z"
    - latency: 1.64282ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:18:56Z"
    - latency: 1.278468ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:17:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:58:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: 45016917-3a90-4472-9a66-0d3cd2e3fa19
    resourceVersion: "23715"
    uid: 58092b4a-2c06-40f7-9ac0-e147e74db4ea
  spec:
    sourcePod: network-check-source-7cbc45fddc-sgjwg
    targetEndpoint: a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:04:56Z"
      message: 'load-balancer-api-external: tcp connection to a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.08694ms
      message: 'load-balancer-api-external: tcp connection to a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:28:56Z"
    - latency: 8.430445ms
      message: 'load-balancer-api-external: resolved host name a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:28:56Z"
    - latency: 5.129813ms
      message: 'load-balancer-api-external: tcp connection to a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:27:56Z"
    - latency: 8.394875ms
      message: 'load-balancer-api-external: resolved host name a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:27:56Z"
    - latency: 4.254197ms
      message: 'load-balancer-api-external: tcp connection to a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:26:56Z"
    - latency: 8.166577ms
      message: 'load-balancer-api-external: resolved host name a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:26:56Z"
    - latency: 6.388796ms
      message: 'load-balancer-api-external: tcp connection to a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:25:56Z"
    - latency: 8.702975ms
      message: 'load-balancer-api-external: resolved host name a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:25:56Z"
    - latency: 3.362341ms
      message: 'load-balancer-api-external: tcp connection to a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:24:56Z"
    - latency: 7.583453ms
      message: 'load-balancer-api-external: resolved host name a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:24:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:58:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: 45016917-3a90-4472-9a66-0d3cd2e3fa19
    resourceVersion: "23716"
    uid: d85cbb45-998e-43a3-b4a4-a6c17f11c6e3
  spec:
    sourcePod: network-check-source-7cbc45fddc-sgjwg
    targetEndpoint: a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:04:56Z"
      message: 'load-balancer-api-internal: tcp connection to a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.135371ms
      message: 'load-balancer-api-internal: tcp connection to a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:28:56Z"
    - latency: 8.458976ms
      message: 'load-balancer-api-internal: resolved host name a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:28:56Z"
    - latency: 5.14066ms
      message: 'load-balancer-api-internal: tcp connection to a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:27:56Z"
    - latency: 8.422533ms
      message: 'load-balancer-api-internal: resolved host name a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:27:56Z"
    - latency: 5.673486ms
      message: 'load-balancer-api-internal: tcp connection to a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:26:56Z"
    - latency: 8.213147ms
      message: 'load-balancer-api-internal: resolved host name a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:26:56Z"
    - latency: 5.36508ms
      message: 'load-balancer-api-internal: tcp connection to a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:25:56Z"
    - latency: 8.74073ms
      message: 'load-balancer-api-internal: resolved host name a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:25:56Z"
    - latency: 4.640633ms
      message: 'load-balancer-api-internal: tcp connection to a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:24:56Z"
    - latency: 7.615494ms
      message: 'load-balancer-api-internal: resolved host name a39f7d11ec80041ffb4a2aafdd8036f2-69ad7f6e27cf3c44.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:24:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:58:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-network-check-target-ip-10-0-136-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: 45016917-3a90-4472-9a66-0d3cd2e3fa19
    resourceVersion: "23046"
    uid: a9e82d27-7ef3-4f52-bfc8-5546d7b67e7f
  spec:
    sourcePod: network-check-source-7cbc45fddc-sgjwg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:05:56Z"
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.044939ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:26:56Z"
    - latency: 1.994196ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:25:56Z"
    - latency: 2.024891ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:24:56Z"
    - latency: 2.012082ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:23:56Z"
    - latency: 2.098445ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:22:56Z"
    - latency: 1.793584ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:21:56Z"
    - latency: 2.536978ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:20:56Z"
    - latency: 5.947911ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:19:56Z"
    - latency: 2.117674ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:18:56Z"
    - latency: 2.138941ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:17:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:58:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-network-check-target-ip-10-0-139-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: 45016917-3a90-4472-9a66-0d3cd2e3fa19
    resourceVersion: "23045"
    uid: 8297fb72-801e-4c02-ab77-cfaa3d8202d0
  spec:
    sourcePod: network-check-source-7cbc45fddc-sgjwg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:05:56Z"
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 682.103µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:26:56Z"
    - latency: 798.381µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:25:56Z"
    - latency: 754.845µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:24:56Z"
    - latency: 821.581µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:23:56Z"
    - latency: 764.006µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:22:56Z"
    - latency: 794.182µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:21:56Z"
    - latency: 1.191136ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:20:56Z"
    - latency: 766.636µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:19:56Z"
    - latency: 1.001029ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:18:56Z"
    - latency: 933.049µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:17:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:58:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-network-check-target-ip-10-0-143-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: 45016917-3a90-4472-9a66-0d3cd2e3fa19
    resourceVersion: "23047"
    uid: ccc3a7f5-b4da-4837-b584-e3f94ad6f924
  spec:
    sourcePod: network-check-source-7cbc45fddc-sgjwg
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:05:56Z"
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.211751ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:26:56Z"
    - latency: 2.289045ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:25:56Z"
    - latency: 2.243979ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:24:56Z"
    - latency: 2.221368ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:23:56Z"
    - latency: 2.001435ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:22:56Z"
    - latency: 2.072738ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:21:56Z"
    - latency: 2.117446ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:20:56Z"
    - latency: 2.0855ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:19:56Z"
    - latency: 2.452929ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:18:56Z"
    - latency: 2.188122ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:17:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:58:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: 45016917-3a90-4472-9a66-0d3cd2e3fa19
    resourceVersion: "23713"
    uid: 7cbdc9de-c439-46b5-a932-913960d00f66
  spec:
    sourcePod: network-check-source-7cbc45fddc-sgjwg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:04:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.605µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:28:56Z"
    - latency: 1.581005ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:28:56Z"
    - latency: 986.952µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:27:56Z"
    - latency: 2.153713ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:27:56Z"
    - latency: 837.874µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:26:56Z"
    - latency: 1.655447ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:26:56Z"
    - latency: 4.300498ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:25:56Z"
    - latency: 1.677925ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:25:56Z"
    - latency: 923.915µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:24:56Z"
    - latency: 1.722251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:24:56Z"
kind: List
metadata:
  resourceVersion: ""