apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:02:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-3-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-3.ec2.internal
      uid: d538eeff-cb07-4109-869c-a51a91b21afc
    resourceVersion: "170544"
    uid: 2da2badd-4aa7-4593-99c7-eb57d290076d
  spec:
    sourcePod: network-check-source-6f78d59f99-j5tcr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:09: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.980637ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:12:36Z"
    - latency: 1.473432ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:11:36Z"
    - latency: 5.938352ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:10:36Z"
    - latency: 1.203933ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:09:36Z"
    - latency: 1.361678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:08:36Z"
    - latency: 1.03774ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:07:36Z"
    - latency: 1.014553ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:06:36Z"
    - latency: 1.027193ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:05:36Z"
    - latency: 1.112021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:04:36Z"
    - latency: 932.655µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:03:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:02:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-3-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-3.ec2.internal
      uid: d538eeff-cb07-4109-869c-a51a91b21afc
    resourceVersion: "172891"
    uid: 9551f975-feb6-46c3-a602-88f6888e6cdc
  spec:
    sourcePod: network-check-source-6f78d59f99-j5tcr
    targetEndpoint: aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:08:36Z"
      message: 'load-balancer-api-external: tcp connection to aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.147886ms
      message: 'load-balancer-api-external: tcp connection to aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:14:36Z"
    - latency: 7.771869ms
      message: 'load-balancer-api-external: resolved host name aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:14:36Z"
    - latency: 17.021478ms
      message: 'load-balancer-api-external: tcp connection to aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:13:36Z"
    - latency: 7.035988ms
      message: 'load-balancer-api-external: resolved host name aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:13:36Z"
    - latency: 17.329129ms
      message: 'load-balancer-api-external: tcp connection to aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:12:36Z"
    - latency: 7.789736ms
      message: 'load-balancer-api-external: resolved host name aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:12:36Z"
    - latency: 16.20019ms
      message: 'load-balancer-api-external: tcp connection to aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:11:36Z"
    - latency: 8.995762ms
      message: 'load-balancer-api-external: resolved host name aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:11:36Z"
    - latency: 17.407942ms
      message: 'load-balancer-api-external: tcp connection to aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:10:36Z"
    - latency: 12.758705ms
      message: 'load-balancer-api-external: resolved host name aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:10:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:02:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-3-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-3.ec2.internal
      uid: d538eeff-cb07-4109-869c-a51a91b21afc
    resourceVersion: "172890"
    uid: 78047d42-b3fb-47b8-bada-47ec312b6c07
  spec:
    sourcePod: network-check-source-6f78d59f99-j5tcr
    targetEndpoint: aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:08:36Z"
      message: 'load-balancer-api-internal: tcp connection to aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.38932ms
      message: 'load-balancer-api-internal: tcp connection to aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:14:36Z"
    - latency: 7.716269ms
      message: 'load-balancer-api-internal: resolved host name aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:14:36Z"
    - latency: 16.951628ms
      message: 'load-balancer-api-internal: tcp connection to aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:13:36Z"
    - latency: 7.057566ms
      message: 'load-balancer-api-internal: resolved host name aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:13:36Z"
    - latency: 17.345917ms
      message: 'load-balancer-api-internal: tcp connection to aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:12:36Z"
    - latency: 8.047185ms
      message: 'load-balancer-api-internal: resolved host name aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:12:36Z"
    - latency: 16.183069ms
      message: 'load-balancer-api-internal: tcp connection to aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:11:36Z"
    - latency: 8.95601ms
      message: 'load-balancer-api-internal: resolved host name aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:11:36Z"
    - latency: 17.368097ms
      message: 'load-balancer-api-internal: tcp connection to aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:10:36Z"
    - latency: 13.079807ms
      message: 'load-balancer-api-internal: resolved host name aef1746b9f86c4560bbb06cecfbdfe7a-cf179457bdef5363.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:10:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:02:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-3-to-network-check-target-ip-10-0-137-72
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-3.ec2.internal
      uid: d538eeff-cb07-4109-869c-a51a91b21afc
    resourceVersion: "170542"
    uid: 83c112ab-d063-485c-ac91-4af29a39edc1
  spec:
    sourcePod: network-check-source-6f78d59f99-j5tcr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:09:36Z"
      message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.155385ms
      message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:12:36Z"
    - latency: 1.917063ms
      message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:11:36Z"
    - latency: 4.676559ms
      message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:10:36Z"
    - latency: 1.883846ms
      message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:09:36Z"
    - latency: 1.753789ms
      message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:08:36Z"
    - latency: 1.72625ms
      message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:07:36Z"
    - latency: 1.8317ms
      message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:06:36Z"
    - latency: 1.83259ms
      message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:05:36Z"
    - latency: 2.006357ms
      message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:04:36Z"
    - latency: 2.066891ms
      message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:03:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:02:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-3-to-network-check-target-ip-10-0-140-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-3.ec2.internal
      uid: d538eeff-cb07-4109-869c-a51a91b21afc
    resourceVersion: "170540"
    uid: 63b9475f-5919-4c48-9579-cc46d33aabde
  spec:
    sourcePod: network-check-source-6f78d59f99-j5tcr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:09:36Z"
      message: 'network-check-target-ip-10-0-140-179: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.375151ms
      message: 'network-check-target-ip-10-0-140-179: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:12:36Z"
    - latency: 2.554759ms
      message: 'network-check-target-ip-10-0-140-179: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:11:36Z"
    - latency: 5.757094ms
      message: 'network-check-target-ip-10-0-140-179: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:10:36Z"
    - latency: 2.524175ms
      message: 'network-check-target-ip-10-0-140-179: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:09:36Z"
    - latency: 2.84938ms
      message: 'network-check-target-ip-10-0-140-179: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:08:36Z"
    - latency: 2.361517ms
      message: 'network-check-target-ip-10-0-140-179: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:07:36Z"
    - latency: 2.707214ms
      message: 'network-check-target-ip-10-0-140-179: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:06:36Z"
    - latency: 2.358376ms
      message: 'network-check-target-ip-10-0-140-179: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:05:36Z"
    - latency: 2.459676ms
      message: 'network-check-target-ip-10-0-140-179: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:04:36Z"
    - latency: 2.255664ms
      message: 'network-check-target-ip-10-0-140-179: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:03:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:02:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-3-to-network-check-target-ip-10-0-142-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-3.ec2.internal
      uid: d538eeff-cb07-4109-869c-a51a91b21afc
    resourceVersion: "170539"
    uid: 728ed1c8-2058-4f2d-b3f2-a591086983c0
  spec:
    sourcePod: network-check-source-6f78d59f99-j5tcr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:09:36Z"
      message: 'network-check-target-ip-10-0-142-3: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 989.993µs
      message: 'network-check-target-ip-10-0-142-3: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:12:36Z"
    - latency: 1.617496ms
      message: 'network-check-target-ip-10-0-142-3: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:11:36Z"
    - latency: 1.499813ms
      message: 'network-check-target-ip-10-0-142-3: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:10:36Z"
    - latency: 993.85µs
      message: 'network-check-target-ip-10-0-142-3: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:09:36Z"
    - latency: 909.022µs
      message: 'network-check-target-ip-10-0-142-3: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:08:36Z"
    - latency: 1.017038ms
      message: 'network-check-target-ip-10-0-142-3: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:07:36Z"
    - latency: 1.01443ms
      message: 'network-check-target-ip-10-0-142-3: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:06:36Z"
    - latency: 868.575µs
      message: 'network-check-target-ip-10-0-142-3: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:05:36Z"
    - latency: 1.306527ms
      message: 'network-check-target-ip-10-0-142-3: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:04:36Z"
    - latency: 1.32206ms
      message: 'network-check-target-ip-10-0-142-3: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:03:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:02:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-3-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-3.ec2.internal
      uid: d538eeff-cb07-4109-869c-a51a91b21afc
    resourceVersion: "172889"
    uid: 95507487-512a-436a-ae5a-a85a434bf8a2
  spec:
    sourcePod: network-check-source-6f78d59f99-j5tcr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:08:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.983µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:14:36Z"
    - latency: 2.263708ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:14:36Z"
    - latency: 866.794µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:13:36Z"
    - latency: 1.836329ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:13:36Z"
    - latency: 1.045095ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:12:36Z"
    - latency: 2.537298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:12:36Z"
    - latency: 1.003466ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:11:36Z"
    - latency: 2.150241ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:11:36Z"
    - latency: 1.088562ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:10:36Z"
    - latency: 6.503447ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:10:36Z"
kind: List
metadata:
  resourceVersion: ""