apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:37:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-154-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-154.ec2.internal
      uid: 3e04d3ba-ff93-4075-8a0e-3c10d18e94cd
    resourceVersion: "55073"
    uid: d70766ca-73a0-44b1-9411-69e9fff23fd5
  spec:
    sourcePod: network-check-source-6f8b768455-bd2z6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:44:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.112656ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:24Z"
    - latency: 1.020888ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:24Z"
    - latency: 1.075194ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:24Z"
    - latency: 1.213485ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:24Z"
    - latency: 1.227851ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:24Z"
    - latency: 1.228092ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:24Z"
    - latency: 1.239291ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:24Z"
    - latency: 2.640927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:58:24Z"
    - latency: 1.347333ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:57:24Z"
    - latency: 1.041486ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:56:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:37:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-154-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-154.ec2.internal
      uid: 3e04d3ba-ff93-4075-8a0e-3c10d18e94cd
    resourceVersion: "56873"
    uid: 52ad6a00-280c-476e-a497-0cb8ceade0c4
  spec:
    sourcePod: network-check-source-6f8b768455-bd2z6
    targetEndpoint: a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:43:24Z"
      message: 'load-balancer-api-external: tcp connection to a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.832064ms
      message: 'load-balancer-api-external: tcp connection to a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:24Z"
    - latency: 7.678361ms
      message: 'load-balancer-api-external: resolved host name a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:07:24Z"
    - latency: 4.650428ms
      message: 'load-balancer-api-external: tcp connection to a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:24Z"
    - latency: 8.561313ms
      message: 'load-balancer-api-external: resolved host name a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:06:24Z"
    - latency: 3.474266ms
      message: 'load-balancer-api-external: tcp connection to a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:24Z"
    - latency: 7.231798ms
      message: 'load-balancer-api-external: resolved host name a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:05:24Z"
    - latency: 3.770511ms
      message: 'load-balancer-api-external: tcp connection to a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:24Z"
    - latency: 7.053631ms
      message: 'load-balancer-api-external: resolved host name a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:04:24Z"
    - latency: 5.248418ms
      message: 'load-balancer-api-external: tcp connection to a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:24Z"
    - latency: 6.981965ms
      message: 'load-balancer-api-external: resolved host name a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:03:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:37:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-154-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-154.ec2.internal
      uid: 3e04d3ba-ff93-4075-8a0e-3c10d18e94cd
    resourceVersion: "56874"
    uid: 48f512b9-552f-4124-939c-da89abc8fc3b
  spec:
    sourcePod: network-check-source-6f8b768455-bd2z6
    targetEndpoint: a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:43:24Z"
      message: 'load-balancer-api-internal: tcp connection to a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.558175ms
      message: 'load-balancer-api-internal: tcp connection to a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:24Z"
    - latency: 7.730945ms
      message: 'load-balancer-api-internal: resolved host name a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:07:24Z"
    - latency: 3.626967ms
      message: 'load-balancer-api-internal: tcp connection to a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:24Z"
    - latency: 8.534922ms
      message: 'load-balancer-api-internal: resolved host name a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:06:24Z"
    - latency: 4.718801ms
      message: 'load-balancer-api-internal: tcp connection to a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:24Z"
    - latency: 7.282437ms
      message: 'load-balancer-api-internal: resolved host name a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:05:24Z"
    - latency: 3.73507ms
      message: 'load-balancer-api-internal: tcp connection to a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:24Z"
    - latency: 7.081727ms
      message: 'load-balancer-api-internal: resolved host name a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:04:24Z"
    - latency: 5.268754ms
      message: 'load-balancer-api-internal: tcp connection to a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:24Z"
    - latency: 6.911466ms
      message: 'load-balancer-api-internal: resolved host name a9d9877b48bae453c9fcb5e38e75518d-736e042d0bea8f31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:03:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:37:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-154-to-network-check-target-ip-10-0-135-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-154.ec2.internal
      uid: 3e04d3ba-ff93-4075-8a0e-3c10d18e94cd
    resourceVersion: "55071"
    uid: 3dfcb738-366e-49ce-93dc-fc959daca6cc
  spec:
    sourcePod: network-check-source-6f8b768455-bd2z6
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:44:24Z"
      message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.425269ms
      message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:24Z"
    - latency: 2.285489ms
      message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:24Z"
    - latency: 2.45692ms
      message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:24Z"
    - latency: 2.431866ms
      message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:24Z"
    - latency: 2.15142ms
      message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:24Z"
    - latency: 2.491646ms
      message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:24Z"
    - latency: 2.440865ms
      message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:24Z"
    - latency: 8.636528ms
      message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:58:24Z"
    - latency: 2.352684ms
      message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:57:24Z"
    - latency: 2.216399ms
      message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:56:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:37:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-154-to-network-check-target-ip-10-0-143-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-154.ec2.internal
      uid: 3e04d3ba-ff93-4075-8a0e-3c10d18e94cd
    resourceVersion: "55070"
    uid: b008b9a4-2439-448e-92cf-9120d3bc0718
  spec:
    sourcePod: network-check-source-6f8b768455-bd2z6
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:44:24Z"
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 938.851µs
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:24Z"
    - latency: 859.743µs
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:24Z"
    - latency: 1.413381ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:24Z"
    - latency: 1.639225ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:24Z"
    - latency: 1.095804ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:24Z"
    - latency: 1.318791ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:24Z"
    - latency: 1.017678ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:24Z"
    - latency: 2.011447ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:58:24Z"
    - latency: 1.186595ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:57:24Z"
    - latency: 922.808µs
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:56:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:37:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-154-to-network-check-target-ip-10-0-143-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-154.ec2.internal
      uid: 3e04d3ba-ff93-4075-8a0e-3c10d18e94cd
    resourceVersion: "55072"
    uid: 00e7d74f-ac7f-4864-9d85-917d63d418b4
  spec:
    sourcePod: network-check-source-6f8b768455-bd2z6
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:44:24Z"
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.460693ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:24Z"
    - latency: 2.355969ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:24Z"
    - latency: 2.369991ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:24Z"
    - latency: 2.618757ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:24Z"
    - latency: 2.320657ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:24Z"
    - latency: 2.473269ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:24Z"
    - latency: 2.312453ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:24Z"
    - latency: 3.433548ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:58:24Z"
    - latency: 2.304505ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:57:24Z"
    - latency: 2.094703ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:56:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:37:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-154-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-154.ec2.internal
      uid: 3e04d3ba-ff93-4075-8a0e-3c10d18e94cd
    resourceVersion: "56872"
    uid: 3c06ded0-35a3-48ee-ba45-a80b4dc1f2ac
  spec:
    sourcePod: network-check-source-6f8b768455-bd2z6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:43:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.205802ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:24Z"
    - latency: 1.884737ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:07:24Z"
    - latency: 860.061µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:24Z"
    - latency: 1.81337ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:06:24Z"
    - latency: 924.778µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:24Z"
    - latency: 2.100299ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:05:24Z"
    - latency: 1.18038ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:24Z"
    - latency: 1.767442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:04:24Z"
    - latency: 943.066µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:24Z"
    - latency: 2.113269ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:03:24Z"
kind: List
metadata:
  resourceVersion: ""