apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T15:26:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-93-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-93.ec2.internal
      uid: da72d6f4-108d-46c1-a97f-49a6c5763c2f
    resourceVersion: "60591"
    uid: 0fcff5eb-e75e-4d73-aa9b-51876974d17e
  spec:
    sourcePod: network-check-source-869dcfcdcd-qtd84
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T15:33:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.309048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:08:40Z"
    - latency: 1.247109ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:07:40Z"
    - latency: 1.175994ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:06:40Z"
    - latency: 1.07212ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:05:40Z"
    - latency: 1.2663ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:04:40Z"
    - latency: 940.303µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:03:40Z"
    - latency: 1.075727ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:02:40Z"
    - latency: 1.058064ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:01:40Z"
    - latency: 1.012167ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:00:40Z"
    - latency: 1.759253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:59:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T15:26:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-93-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-93.ec2.internal
      uid: da72d6f4-108d-46c1-a97f-49a6c5763c2f
    resourceVersion: "60593"
    uid: e5aced61-3f57-4a74-9449-9baead97158c
  spec:
    sourcePod: network-check-source-869dcfcdcd-qtd84
    targetEndpoint: a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T15:32:40Z"
      message: 'load-balancer-api-external: tcp connection to a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.413496ms
      message: 'load-balancer-api-external: tcp connection to a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:08:40Z"
    - latency: 9.011234ms
      message: 'load-balancer-api-external: resolved host name a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:08:40Z"
    - latency: 4.849132ms
      message: 'load-balancer-api-external: tcp connection to a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:07:40Z"
    - latency: 7.68199ms
      message: 'load-balancer-api-external: resolved host name a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:07:40Z"
    - latency: 4.367687ms
      message: 'load-balancer-api-external: tcp connection to a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:06:40Z"
    - latency: 7.20856ms
      message: 'load-balancer-api-external: resolved host name a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:06:40Z"
    - latency: 4.118886ms
      message: 'load-balancer-api-external: tcp connection to a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:05:40Z"
    - latency: 7.578818ms
      message: 'load-balancer-api-external: resolved host name a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:05:40Z"
    - latency: 4.145612ms
      message: 'load-balancer-api-external: tcp connection to a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:04:40Z"
    - latency: 7.750153ms
      message: 'load-balancer-api-external: resolved host name a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:04:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T15:26:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-93-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-93.ec2.internal
      uid: da72d6f4-108d-46c1-a97f-49a6c5763c2f
    resourceVersion: "60592"
    uid: d106d0b6-bbff-41fe-bbff-a400aabbf085
  spec:
    sourcePod: network-check-source-869dcfcdcd-qtd84
    targetEndpoint: a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T15:32:40Z"
      message: 'load-balancer-api-internal: tcp connection to a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.675208ms
      message: 'load-balancer-api-internal: tcp connection to a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:08:40Z"
    - latency: 9.036296ms
      message: 'load-balancer-api-internal: resolved host name a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:08:40Z"
    - latency: 4.854456ms
      message: 'load-balancer-api-internal: tcp connection to a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:07:40Z"
    - latency: 7.618019ms
      message: 'load-balancer-api-internal: resolved host name a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:07:40Z"
    - latency: 4.381542ms
      message: 'load-balancer-api-internal: tcp connection to a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:06:40Z"
    - latency: 7.130451ms
      message: 'load-balancer-api-internal: resolved host name a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:06:40Z"
    - latency: 4.096254ms
      message: 'load-balancer-api-internal: tcp connection to a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:05:40Z"
    - latency: 7.606225ms
      message: 'load-balancer-api-internal: resolved host name a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:05:40Z"
    - latency: 4.149479ms
      message: 'load-balancer-api-internal: tcp connection to a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:04:40Z"
    - latency: 7.796448ms
      message: 'load-balancer-api-internal: resolved host name a8d7f619d03db497897ae855af992244-98466104810a3f59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:04:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T15:26:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-93-to-network-check-target-ip-10-0-137-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-93.ec2.internal
      uid: da72d6f4-108d-46c1-a97f-49a6c5763c2f
    resourceVersion: "60587"
    uid: ea230597-e566-4135-a5cd-620a3f6fe700
  spec:
    sourcePod: network-check-source-869dcfcdcd-qtd84
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T15:33:40Z"
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.594267ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:08:40Z"
    - latency: 1.507622ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:07:40Z"
    - latency: 951µs
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:06:40Z"
    - latency: 1.365796ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:05:40Z"
    - latency: 1.530573ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:04:40Z"
    - latency: 1.139871ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:03:40Z"
    - latency: 868.51µs
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:02:40Z"
    - latency: 844.622µs
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:01:40Z"
    - latency: 934.151µs
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:00:40Z"
    - latency: 3.742693ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:59:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T15:26:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-93-to-network-check-target-ip-10-0-139-109
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-93.ec2.internal
      uid: da72d6f4-108d-46c1-a97f-49a6c5763c2f
    resourceVersion: "60588"
    uid: f310846b-378c-4a40-adc0-89a6b0a77cd2
  spec:
    sourcePod: network-check-source-869dcfcdcd-qtd84
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T15:33:40Z"
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.176446ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:08:40Z"
    - latency: 2.267057ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:07:40Z"
    - latency: 2.228957ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:06:40Z"
    - latency: 2.067072ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:05:40Z"
    - latency: 2.496779ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:04:40Z"
    - latency: 2.167916ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:03:40Z"
    - latency: 2.231197ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:02:40Z"
    - latency: 2.266818ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:01:40Z"
    - latency: 2.165101ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:00:40Z"
    - latency: 3.701509ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:59:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T15:26:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-93-to-network-check-target-ip-10-0-140-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-93.ec2.internal
      uid: da72d6f4-108d-46c1-a97f-49a6c5763c2f
    resourceVersion: "60590"
    uid: 905e98fa-277c-4bd6-84ee-c2052feedc59
  spec:
    sourcePod: network-check-source-869dcfcdcd-qtd84
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T15:33:40Z"
      message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.390207ms
      message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:08:40Z"
    - latency: 2.398556ms
      message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:07:40Z"
    - latency: 2.245614ms
      message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:06:40Z"
    - latency: 2.337473ms
      message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:05:40Z"
    - latency: 2.135172ms
      message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:04:40Z"
    - latency: 2.207566ms
      message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:03:40Z"
    - latency: 2.17701ms
      message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:02:40Z"
    - latency: 2.333913ms
      message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:01:40Z"
    - latency: 2.702452ms
      message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:00:40Z"
    - latency: 3.07003ms
      message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:59:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T15:26:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-93-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-93.ec2.internal
      uid: da72d6f4-108d-46c1-a97f-49a6c5763c2f
    resourceVersion: "60589"
    uid: 7ccd911d-be2c-4af6-be9e-2d0cfb716b90
  spec:
    sourcePod: network-check-source-869dcfcdcd-qtd84
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T15:32:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.258µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:08:40Z"
    - latency: 1.966757ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:08:40Z"
    - latency: 937.88µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:07:40Z"
    - latency: 2.352108ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:07:40Z"
    - latency: 1.014146ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:06:40Z"
    - latency: 1.793335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:06:40Z"
    - latency: 1.005365ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:05:40Z"
    - latency: 2.217035ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:05:40Z"
    - latency: 867.099µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T16:04:40Z"
    - latency: 2.398256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T16:04:40Z"
kind: List
metadata:
  resourceVersion: ""