apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T18:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: d6097777-4c6f-4a65-91cf-07b8e7f60d21
    resourceVersion: "67287"
    uid: d4cb6142-6edb-4e95-a06b-04550fee7c42
  spec:
    sourcePod: network-check-source-6f8b768455-9qdtz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T19:04:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.0677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:32:36Z"
    - latency: 1.048019ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:31:36Z"
    - latency: 885.96µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:30:36Z"
    - latency: 991.948µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:29:36Z"
    - latency: 1.035267ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:28:36Z"
    - latency: 1.12773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:27:36Z"
    - latency: 1.065752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:26:36Z"
    - latency: 871.314µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:25:36Z"
    - latency: 1.060671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:24:36Z"
    - latency: 1.198833ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:23:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T18:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: d6097777-4c6f-4a65-91cf-07b8e7f60d21
    resourceVersion: "68251"
    uid: 457b4a20-ea7d-49b2-a349-d3a2336c6d87
  spec:
    sourcePod: network-check-source-6f8b768455-9qdtz
    targetEndpoint: a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T19:03:36Z"
      message: 'load-balancer-api-external: tcp connection to a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.979845ms
      message: 'load-balancer-api-external: tcp connection to a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:33:36Z"
    - latency: 13.640293ms
      message: 'load-balancer-api-external: resolved host name a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:33:36Z"
    - latency: 4.138347ms
      message: 'load-balancer-api-external: tcp connection to a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:32:36Z"
    - latency: 9.64832ms
      message: 'load-balancer-api-external: resolved host name a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:32:36Z"
    - latency: 5.327159ms
      message: 'load-balancer-api-external: tcp connection to a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:31:36Z"
    - latency: 8.906093ms
      message: 'load-balancer-api-external: resolved host name a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:31:36Z"
    - latency: 5.454882ms
      message: 'load-balancer-api-external: tcp connection to a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:30:36Z"
    - latency: 6.828948ms
      message: 'load-balancer-api-external: resolved host name a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:30:36Z"
    - latency: 3.392189ms
      message: 'load-balancer-api-external: tcp connection to a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:29:36Z"
    - latency: 9.176942ms
      message: 'load-balancer-api-external: resolved host name a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:29:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T18:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: d6097777-4c6f-4a65-91cf-07b8e7f60d21
    resourceVersion: "68250"
    uid: b62a3ea9-d822-4cac-85f9-b6663bc15339
  spec:
    sourcePod: network-check-source-6f8b768455-9qdtz
    targetEndpoint: a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T19:03:36Z"
      message: 'load-balancer-api-internal: tcp connection to a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.067423ms
      message: 'load-balancer-api-internal: tcp connection to a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:33:36Z"
    - latency: 13.61778ms
      message: 'load-balancer-api-internal: resolved host name a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:33:36Z"
    - latency: 4.105803ms
      message: 'load-balancer-api-internal: tcp connection to a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:32:36Z"
    - latency: 9.673337ms
      message: 'load-balancer-api-internal: resolved host name a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:32:36Z"
    - latency: 5.313067ms
      message: 'load-balancer-api-internal: tcp connection to a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:31:36Z"
    - latency: 8.927688ms
      message: 'load-balancer-api-internal: resolved host name a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:31:36Z"
    - latency: 5.446722ms
      message: 'load-balancer-api-internal: tcp connection to a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:30:36Z"
    - latency: 6.729592ms
      message: 'load-balancer-api-internal: resolved host name a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:30:36Z"
    - latency: 5.532192ms
      message: 'load-balancer-api-internal: tcp connection to a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:29:36Z"
    - latency: 9.240998ms
      message: 'load-balancer-api-internal: resolved host name a2b9d954e541547f0a5d8d94572a0106-4bb30bc06ad36064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:29:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T18:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-network-check-target-ip-10-0-135-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: d6097777-4c6f-4a65-91cf-07b8e7f60d21
    resourceVersion: "67285"
    uid: d78902c0-8a18-4295-aa4d-60cff5bb220b
  spec:
    sourcePod: network-check-source-6f8b768455-9qdtz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T19:04:36Z"
      message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.996837ms
      message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:32:36Z"
    - latency: 2.325534ms
      message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:31:36Z"
    - latency: 2.020008ms
      message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:30:36Z"
    - latency: 2.368783ms
      message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:29:36Z"
    - latency: 2.626858ms
      message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:28:36Z"
    - latency: 2.239705ms
      message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:27:36Z"
    - latency: 2.338923ms
      message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:26:36Z"
    - latency: 1.936121ms
      message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:25:36Z"
    - latency: 2.378138ms
      message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:24:36Z"
    - latency: 2.761692ms
      message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:23:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T18:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-network-check-target-ip-10-0-140-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: d6097777-4c6f-4a65-91cf-07b8e7f60d21
    resourceVersion: "67284"
    uid: 54a9a214-f209-4204-b50c-f1370f49cb78
  spec:
    sourcePod: network-check-source-6f8b768455-9qdtz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T19:04:36Z"
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.148164ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:32:36Z"
    - latency: 985.788µs
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:31:36Z"
    - latency: 922.733µs
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:30:36Z"
    - latency: 925.035µs
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:29:36Z"
    - latency: 965.651µs
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:28:36Z"
    - latency: 1.003232ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:27:36Z"
    - latency: 1.013217ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:26:36Z"
    - latency: 1.004454ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:25:36Z"
    - latency: 1.012285ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:24:36Z"
    - latency: 1.062533ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:23:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T18:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-network-check-target-ip-10-0-143-252
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: d6097777-4c6f-4a65-91cf-07b8e7f60d21
    resourceVersion: "67286"
    uid: 570d1fca-87b9-453f-969a-2f7726005b53
  spec:
    sourcePod: network-check-source-6f8b768455-9qdtz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T19:04:36Z"
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.521541ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:32:36Z"
    - latency: 2.511222ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:31:36Z"
    - latency: 2.397567ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:30:36Z"
    - latency: 2.457742ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:29:36Z"
    - latency: 2.406079ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:28:36Z"
    - latency: 2.282077ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:27:36Z"
    - latency: 2.066723ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:26:36Z"
    - latency: 1.928489ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:25:36Z"
    - latency: 2.437184ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:24:36Z"
    - latency: 2.441713ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:23:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T18:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: d6097777-4c6f-4a65-91cf-07b8e7f60d21
    resourceVersion: "68248"
    uid: 5eed993d-ea37-4fa1-bb8f-b6ba739c6333
  spec:
    sourcePod: network-check-source-6f8b768455-9qdtz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T19:03:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 986.875µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:33:36Z"
    - latency: 1.762208ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:33:36Z"
    - latency: 1.0271ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:32:36Z"
    - latency: 2.062788ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:32:36Z"
    - latency: 990.617µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:31:36Z"
    - latency: 1.730238ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:31:36Z"
    - latency: 1.03339ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:30:36Z"
    - latency: 1.805694ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:30:36Z"
    - latency: 1.235711ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T19:29:36Z"
    - latency: 1.750199ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T19:29:36Z"
kind: List
metadata:
  resourceVersion: ""