apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-111-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-111.ec2.internal
      uid: e98dd954-c1a1-4c02-9bab-1061074e40c2
    resourceVersion: "54030"
    uid: 2d372833-be8c-49e4-9bf9-2151c76fc889
  spec:
    sourcePod: network-check-source-989f8b8dc-qdsht
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:43:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.163554ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:11:19Z"
    - latency: 900.317µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:10:19Z"
    - latency: 953.967µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:09:19Z"
    - latency: 1.088901ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:08:19Z"
    - latency: 971.387µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:07:19Z"
    - latency: 1.086521ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:06:19Z"
    - latency: 1.015102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:05:19Z"
    - latency: 793.326µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:04:19Z"
    - latency: 945.795µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:03:19Z"
    - latency: 1.523842ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:02:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-111-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-111.ec2.internal
      uid: e98dd954-c1a1-4c02-9bab-1061074e40c2
    resourceVersion: "54988"
    uid: 25c9964b-2a80-47fb-a30d-91f74fd8155f
  spec:
    sourcePod: network-check-source-989f8b8dc-qdsht
    targetEndpoint: a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:42:19Z"
      message: 'load-balancer-api-external: tcp connection to a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.90671ms
      message: 'load-balancer-api-external: tcp connection to a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:12:19Z"
    - latency: 7.826597ms
      message: 'load-balancer-api-external: resolved host name a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:12:19Z"
    - latency: 3.704789ms
      message: 'load-balancer-api-external: tcp connection to a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:11:19Z"
    - latency: 9.459487ms
      message: 'load-balancer-api-external: resolved host name a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:11:19Z"
    - latency: 4.466107ms
      message: 'load-balancer-api-external: tcp connection to a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:10:19Z"
    - latency: 9.058081ms
      message: 'load-balancer-api-external: resolved host name a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:10:19Z"
    - latency: 4.328962ms
      message: 'load-balancer-api-external: tcp connection to a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:09:19Z"
    - latency: 11.359376ms
      message: 'load-balancer-api-external: resolved host name a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:09:19Z"
    - latency: 4.135059ms
      message: 'load-balancer-api-external: tcp connection to a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:08:19Z"
    - latency: 8.283052ms
      message: 'load-balancer-api-external: resolved host name a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:08:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-111-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-111.ec2.internal
      uid: e98dd954-c1a1-4c02-9bab-1061074e40c2
    resourceVersion: "54989"
    uid: 66e74b43-d294-4ed0-855e-d2c7434910ae
  spec:
    sourcePod: network-check-source-989f8b8dc-qdsht
    targetEndpoint: a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:42:19Z"
      message: 'load-balancer-api-internal: tcp connection to a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.956359ms
      message: 'load-balancer-api-internal: tcp connection to a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:12:19Z"
    - latency: 7.90041ms
      message: 'load-balancer-api-internal: resolved host name a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:12:19Z"
    - latency: 4.122565ms
      message: 'load-balancer-api-internal: tcp connection to a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:11:19Z"
    - latency: 9.546042ms
      message: 'load-balancer-api-internal: resolved host name a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:11:19Z"
    - latency: 4.415601ms
      message: 'load-balancer-api-internal: tcp connection to a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:10:19Z"
    - latency: 9.137448ms
      message: 'load-balancer-api-internal: resolved host name a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:10:19Z"
    - latency: 4.346461ms
      message: 'load-balancer-api-internal: tcp connection to a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:09:19Z"
    - latency: 11.383026ms
      message: 'load-balancer-api-internal: resolved host name a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:09:19Z"
    - latency: 5.326708ms
      message: 'load-balancer-api-internal: tcp connection to a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:08:19Z"
    - latency: 8.335841ms
      message: 'load-balancer-api-internal: resolved host name a0f841f068f6a4b2fa5c8a3e479c0049-c6e31529795b865d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:08:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-111-to-network-check-target-ip-10-0-133-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-111.ec2.internal
      uid: e98dd954-c1a1-4c02-9bab-1061074e40c2
    resourceVersion: "54028"
    uid: c25106e6-5660-4548-b932-e41de5c4acb1
  spec:
    sourcePod: network-check-source-989f8b8dc-qdsht
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:43:19Z"
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.174281ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:11:19Z"
    - latency: 2.141655ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:10:19Z"
    - latency: 2.161264ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:09:19Z"
    - latency: 1.919342ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:08:19Z"
    - latency: 2.182518ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:07:19Z"
    - latency: 2.26717ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:06:19Z"
    - latency: 2.348153ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:05:19Z"
    - latency: 2.521116ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:04:19Z"
    - latency: 1.987102ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:03:19Z"
    - latency: 2.07048ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:02:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-111-to-network-check-target-ip-10-0-137-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-111.ec2.internal
      uid: e98dd954-c1a1-4c02-9bab-1061074e40c2
    resourceVersion: "54029"
    uid: 3fab83e3-bc75-4d66-aa81-34c29f59b379
  spec:
    sourcePod: network-check-source-989f8b8dc-qdsht
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:43:19Z"
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.034634ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:11:19Z"
    - latency: 2.224654ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:10:19Z"
    - latency: 1.892059ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:09:19Z"
    - latency: 1.680847ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:08:19Z"
    - latency: 2.024617ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:07:19Z"
    - latency: 1.915756ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:06:19Z"
    - latency: 1.866681ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:05:19Z"
    - latency: 1.939779ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:04:19Z"
    - latency: 1.704488ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:03:19Z"
    - latency: 2.045538ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:02:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-111-to-network-check-target-ip-10-0-140-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-111.ec2.internal
      uid: e98dd954-c1a1-4c02-9bab-1061074e40c2
    resourceVersion: "54027"
    uid: ca912c27-5993-4b2b-88ca-b549993f159c
  spec:
    sourcePod: network-check-source-989f8b8dc-qdsht
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:43:19Z"
      message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 971.395µs
      message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:11:19Z"
    - latency: 1.5891ms
      message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:10:19Z"
    - latency: 890.545µs
      message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:09:19Z"
    - latency: 1.492296ms
      message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:08:19Z"
    - latency: 797.334µs
      message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:07:19Z"
    - latency: 815.248µs
      message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:06:19Z"
    - latency: 941.308µs
      message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:05:19Z"
    - latency: 752.184µs
      message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:04:19Z"
    - latency: 1.172524ms
      message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:03:19Z"
    - latency: 866.359µs
      message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:02:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-111-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-111.ec2.internal
      uid: e98dd954-c1a1-4c02-9bab-1061074e40c2
    resourceVersion: "54987"
    uid: a9b08b19-5d8f-4435-81fd-a24ef88af782
  spec:
    sourcePod: network-check-source-989f8b8dc-qdsht
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:42:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 992.292µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:12:19Z"
    - latency: 1.877286ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:12:19Z"
    - latency: 875.478µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:11:19Z"
    - latency: 1.930762ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:11:19Z"
    - latency: 939.836µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:10:19Z"
    - latency: 2.39517ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:10:19Z"
    - latency: 828.557µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:09:19Z"
    - latency: 2.420834ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:09:19Z"
    - latency: 1.033844ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:08:19Z"
    - latency: 1.661956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:08:19Z"
kind: List
metadata:
  resourceVersion: ""