apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:26:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-97-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-97.ec2.internal
      uid: ff3df9a0-cf8c-4003-a367-351d1b51bbaf
    resourceVersion: "64463"
    uid: 6529b1c8-80eb-4173-9fa7-40424b9891d1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nd8d8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T08:33:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.141802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:08:47Z"
    - latency: 1.860908ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:07:47Z"
    - latency: 858.924µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:06:47Z"
    - latency: 749.571µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:05:47Z"
    - latency: 1.301492ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:04:47Z"
    - latency: 1.068738ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:03:47Z"
    - latency: 1.71646ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:02:47Z"
    - latency: 1.005363ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:01:47Z"
    - latency: 955.723µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:00:47Z"
    - latency: 879.663µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T08:59:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:26:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-97-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-97.ec2.internal
      uid: ff3df9a0-cf8c-4003-a367-351d1b51bbaf
    resourceVersion: "64464"
    uid: caf78fca-47c4-4016-949f-d19af09c8875
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nd8d8
    targetEndpoint: a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T08:32:47Z"
      message: 'load-balancer-api-external: tcp connection to a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.822622ms
      message: 'load-balancer-api-external: tcp connection to a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:08:47Z"
    - latency: 7.854997ms
      message: 'load-balancer-api-external: resolved host name a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:08:47Z"
    - latency: 5.114609ms
      message: 'load-balancer-api-external: tcp connection to a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:07:47Z"
    - latency: 9.324277ms
      message: 'load-balancer-api-external: resolved host name a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:07:47Z"
    - latency: 4.255207ms
      message: 'load-balancer-api-external: tcp connection to a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:06:47Z"
    - latency: 7.039509ms
      message: 'load-balancer-api-external: resolved host name a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:06:47Z"
    - latency: 4.346477ms
      message: 'load-balancer-api-external: tcp connection to a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:05:47Z"
    - latency: 8.407582ms
      message: 'load-balancer-api-external: resolved host name a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:05:47Z"
    - latency: 5.450198ms
      message: 'load-balancer-api-external: tcp connection to a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:04:47Z"
    - latency: 6.712231ms
      message: 'load-balancer-api-external: resolved host name a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:04:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:26:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-97-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-97.ec2.internal
      uid: ff3df9a0-cf8c-4003-a367-351d1b51bbaf
    resourceVersion: "64465"
    uid: e91cf1c1-acc6-4a8a-8470-5e2fb7f02069
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nd8d8
    targetEndpoint: a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T08:32:47Z"
      message: 'load-balancer-api-internal: tcp connection to a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.67898ms
      message: 'load-balancer-api-internal: tcp connection to a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:08:47Z"
    - latency: 7.807209ms
      message: 'load-balancer-api-internal: resolved host name a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:08:47Z"
    - latency: 5.128951ms
      message: 'load-balancer-api-internal: tcp connection to a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:07:47Z"
    - latency: 9.285138ms
      message: 'load-balancer-api-internal: resolved host name a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:07:47Z"
    - latency: 4.140882ms
      message: 'load-balancer-api-internal: tcp connection to a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:06:47Z"
    - latency: 7.062497ms
      message: 'load-balancer-api-internal: resolved host name a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:06:47Z"
    - latency: 4.323865ms
      message: 'load-balancer-api-internal: tcp connection to a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:05:47Z"
    - latency: 8.370256ms
      message: 'load-balancer-api-internal: resolved host name a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:05:47Z"
    - latency: 5.829425ms
      message: 'load-balancer-api-internal: tcp connection to a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:04:47Z"
    - latency: 6.777544ms
      message: 'load-balancer-api-internal: resolved host name a220af5d986b54a58ade8c84ffd549f2-37e3537d9388caf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:04:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:26:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-97-to-network-check-target-ip-10-0-131-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-97.ec2.internal
      uid: ff3df9a0-cf8c-4003-a367-351d1b51bbaf
    resourceVersion: "64461"
    uid: 45dfb549-d160-4522-9ef4-ad535beefa44
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nd8d8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T08:33:47Z"
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.125378ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:08:47Z"
    - latency: 2.233409ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:07:47Z"
    - latency: 2.094405ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:06:47Z"
    - latency: 2.025463ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:05:47Z"
    - latency: 1.76886ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:04:47Z"
    - latency: 1.612967ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:03:47Z"
    - latency: 2.191482ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:02:47Z"
    - latency: 2.195477ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:01:47Z"
    - latency: 2.234185ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:00:47Z"
    - latency: 2.274712ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T08:59:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:26:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-97-to-network-check-target-ip-10-0-137-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-97.ec2.internal
      uid: ff3df9a0-cf8c-4003-a367-351d1b51bbaf
    resourceVersion: "64460"
    uid: 5f21d126-743f-41ee-878f-ff5db093c707
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nd8d8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T08:33:47Z"
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.240154ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:08:47Z"
    - latency: 2.496171ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:07:47Z"
    - latency: 2.580944ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:06:47Z"
    - latency: 2.459901ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:05:47Z"
    - latency: 2.395729ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:04:47Z"
    - latency: 2.075142ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:03:47Z"
    - latency: 2.28316ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:02:47Z"
    - latency: 2.538341ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:01:47Z"
    - latency: 2.646215ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:00:47Z"
    - latency: 3.070087ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T08:59:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:26:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-97-to-network-check-target-ip-10-0-142-97
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-97.ec2.internal
      uid: ff3df9a0-cf8c-4003-a367-351d1b51bbaf
    resourceVersion: "64459"
    uid: 36c67a2e-f484-4946-8474-a0eb411f2386
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nd8d8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T08:33:47Z"
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.373907ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:08:47Z"
    - latency: 1.050752ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:07:47Z"
    - latency: 870.237µs
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:06:47Z"
    - latency: 1.040497ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:05:47Z"
    - latency: 896.438µs
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:04:47Z"
    - latency: 886.888µs
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:03:47Z"
    - latency: 866.278µs
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:02:47Z"
    - latency: 934.681µs
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:01:47Z"
    - latency: 1.089887ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:00:47Z"
    - latency: 793.208µs
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T08:59:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T08:26:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-97-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-97.ec2.internal
      uid: ff3df9a0-cf8c-4003-a367-351d1b51bbaf
    resourceVersion: "64462"
    uid: ae7d9009-7342-41bb-b793-0b8e4bb12128
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nd8d8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T08:32:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.014565ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:08:47Z"
    - latency: 2.71902ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:08:47Z"
    - latency: 1.11536ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:07:47Z"
    - latency: 1.977792ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:07:47Z"
    - latency: 1.352222ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:06:47Z"
    - latency: 2.132222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:06:47Z"
    - latency: 994.51µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:05:47Z"
    - latency: 1.76558ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:05:47Z"
    - latency: 1.014578ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T09:04:47Z"
    - latency: 1.791657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T09:04:47Z"
kind: List
metadata:
  resourceVersion: ""