apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:23:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-85-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-85.ec2.internal
      uid: 7f25b0b8-a948-4a3d-8bc6-77b5e76ee831
    resourceVersion: "57488"
    uid: dcd7b8b2-5b5f-4da0-8ba7-e076fd576caf
  spec:
    sourcePod: network-check-source-6f8b768455-lc6tw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:30:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.006207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:51:45Z"
    - latency: 1.235181ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:50:45Z"
    - latency: 1.346168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:49:45Z"
    - latency: 1.285777ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:48:45Z"
    - latency: 1.657316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:47:45Z"
    - latency: 1.025375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:46:45Z"
    - latency: 2.533752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:45:45Z"
    - latency: 1.54067ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:44:45Z"
    - latency: 1.409373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:43:45Z"
    - latency: 1.240953ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:42:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:23:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-85-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-85.ec2.internal
      uid: 7f25b0b8-a948-4a3d-8bc6-77b5e76ee831
    resourceVersion: "59338"
    uid: 12db1ba4-a6da-4fc0-a2c6-010e49e17570
  spec:
    sourcePod: network-check-source-6f8b768455-lc6tw
    targetEndpoint: a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:29:45Z"
      message: 'load-balancer-api-external: tcp connection to a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.661767ms
      message: 'load-balancer-api-external: tcp connection to a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:53:45Z"
    - latency: 9.020872ms
      message: 'load-balancer-api-external: resolved host name a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:53:45Z"
    - latency: 4.142767ms
      message: 'load-balancer-api-external: tcp connection to a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:52:45Z"
    - latency: 9.186816ms
      message: 'load-balancer-api-external: resolved host name a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:52:45Z"
    - latency: 4.867274ms
      message: 'load-balancer-api-external: tcp connection to a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:51:45Z"
    - latency: 8.82395ms
      message: 'load-balancer-api-external: resolved host name a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:51:45Z"
    - latency: 3.70933ms
      message: 'load-balancer-api-external: tcp connection to a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:50:45Z"
    - latency: 9.622627ms
      message: 'load-balancer-api-external: resolved host name a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:50:45Z"
    - latency: 3.910713ms
      message: 'load-balancer-api-external: tcp connection to a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:49:45Z"
    - latency: 7.509128ms
      message: 'load-balancer-api-external: resolved host name a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:49:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:23:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-85-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-85.ec2.internal
      uid: 7f25b0b8-a948-4a3d-8bc6-77b5e76ee831
    resourceVersion: "59336"
    uid: 90bb04af-4c47-4c69-a41b-9220254f4a9b
  spec:
    sourcePod: network-check-source-6f8b768455-lc6tw
    targetEndpoint: a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:29:45Z"
      message: 'load-balancer-api-internal: tcp connection to a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.702651ms
      message: 'load-balancer-api-internal: tcp connection to a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:53:45Z"
    - latency: 8.993134ms
      message: 'load-balancer-api-internal: resolved host name a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:53:45Z"
    - latency: 3.867035ms
      message: 'load-balancer-api-internal: tcp connection to a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:52:45Z"
    - latency: 9.335016ms
      message: 'load-balancer-api-internal: resolved host name a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:52:45Z"
    - latency: 4.992469ms
      message: 'load-balancer-api-internal: tcp connection to a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:51:45Z"
    - latency: 8.722683ms
      message: 'load-balancer-api-internal: resolved host name a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:51:45Z"
    - latency: 13.939393ms
      message: 'load-balancer-api-internal: tcp connection to a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:50:45Z"
    - latency: 9.585469ms
      message: 'load-balancer-api-internal: resolved host name a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:50:45Z"
    - latency: 3.959957ms
      message: 'load-balancer-api-internal: tcp connection to a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:49:45Z"
    - latency: 7.402137ms
      message: 'load-balancer-api-internal: resolved host name a6d08db35174d440c85a74310cc26d3a-cd48296e66d07ddc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:49:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:23:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-85-to-network-check-target-ip-10-0-130-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-85.ec2.internal
      uid: 7f25b0b8-a948-4a3d-8bc6-77b5e76ee831
    resourceVersion: "57486"
    uid: bc4b6726-46a0-4ee5-8485-05e28474b7fb
  spec:
    sourcePod: network-check-source-6f8b768455-lc6tw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:30:45Z"
      message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.205364ms
      message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:51:45Z"
    - latency: 1.831681ms
      message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:50:45Z"
    - latency: 2.273314ms
      message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:49:45Z"
    - latency: 2.510764ms
      message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:48:45Z"
    - latency: 2.067669ms
      message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:47:45Z"
    - latency: 2.270818ms
      message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:46:45Z"
    - latency: 2.095949ms
      message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:45:45Z"
    - latency: 2.990918ms
      message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:44:45Z"
    - latency: 2.291821ms
      message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:43:45Z"
    - latency: 2.083655ms
      message: 'network-check-target-ip-10-0-130-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:42:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:23:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-85-to-network-check-target-ip-10-0-138-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-85.ec2.internal
      uid: 7f25b0b8-a948-4a3d-8bc6-77b5e76ee831
    resourceVersion: "57485"
    uid: 7fdfaf34-9452-4e51-a8d0-c746316bed50
  spec:
    sourcePod: network-check-source-6f8b768455-lc6tw
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:30:45Z"
      message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.434751ms
      message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:51:45Z"
    - latency: 2.20462ms
      message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:50:45Z"
    - latency: 2.217937ms
      message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:49:45Z"
    - latency: 2.540265ms
      message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:48:45Z"
    - latency: 2.228956ms
      message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:47:45Z"
    - latency: 2.326678ms
      message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:46:45Z"
    - latency: 3.082122ms
      message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:45:45Z"
    - latency: 2.372026ms
      message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:44:45Z"
    - latency: 2.385636ms
      message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:43:45Z"
    - latency: 2.314697ms
      message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:42:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:23:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-85-to-network-check-target-ip-10-0-143-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-85.ec2.internal
      uid: 7f25b0b8-a948-4a3d-8bc6-77b5e76ee831
    resourceVersion: "57487"
    uid: c901216f-7fdc-4758-b7fb-dad607ee4c1c
  spec:
    sourcePod: network-check-source-6f8b768455-lc6tw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:30:45Z"
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.235934ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:51:45Z"
    - latency: 968.181µs
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:50:45Z"
    - latency: 842.648µs
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:49:45Z"
    - latency: 1.646191ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:48:45Z"
    - latency: 884.539µs
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:47:45Z"
    - latency: 850.021µs
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:46:45Z"
    - latency: 2.818841ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:45:45Z"
    - latency: 1.661587ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:44:45Z"
    - latency: 1.142874ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:43:45Z"
    - latency: 1.101749ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:42:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:23:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-85-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-85.ec2.internal
      uid: 7f25b0b8-a948-4a3d-8bc6-77b5e76ee831
    resourceVersion: "59335"
    uid: b6a2f6fe-35b8-4a86-a858-8abe0023f7b3
  spec:
    sourcePod: network-check-source-6f8b768455-lc6tw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:29:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.78µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:53:45Z"
    - latency: 1.792371ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:53:45Z"
    - latency: 1.13921ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:52:45Z"
    - latency: 2.092762ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:52:45Z"
    - latency: 1.115679ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:51:45Z"
    - latency: 2.056483ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:51:45Z"
    - latency: 980.872µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:50:45Z"
    - latency: 1.817642ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:50:45Z"
    - latency: 964.396µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:49:45Z"
    - latency: 1.521082ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:49:45Z"
kind: List
metadata:
  resourceVersion: ""