apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:43:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 44a3c3a4-f863-4413-b7e5-e2403d413a98
    resourceVersion: "32334"
    uid: 3cc1cdca-790a-4014-b3a4-5ac43350ad93
  spec:
    sourcePod: network-check-source-6f78d59f99-575jz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:50:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 804.463µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:53:08Z"
    - latency: 1.079314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:52:08Z"
    - latency: 833.781µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:51:08Z"
    - latency: 802.485µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:50:08Z"
    - latency: 1.186248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:49:08Z"
    - latency: 1.23605ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:48:08Z"
    - latency: 1.010933ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:47:08Z"
    - latency: 1.594675ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:46:08Z"
    - latency: 1.202614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:45:08Z"
    - latency: 719.436µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:44:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:43:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 44a3c3a4-f863-4413-b7e5-e2403d413a98
    resourceVersion: "33347"
    uid: 858a8385-3235-4cfa-aab4-f0e79941c426
  spec:
    sourcePod: network-check-source-6f78d59f99-575jz
    targetEndpoint: a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:49:08Z"
      message: 'load-balancer-api-external: tcp connection to a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.295995ms
      message: 'load-balancer-api-external: tcp connection to a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:55:08Z"
    - latency: 7.948434ms
      message: 'load-balancer-api-external: resolved host name a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:55:08Z"
    - latency: 16.324009ms
      message: 'load-balancer-api-external: tcp connection to a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:54:08Z"
    - latency: 6.659784ms
      message: 'load-balancer-api-external: resolved host name a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:54:08Z"
    - latency: 19.916497ms
      message: 'load-balancer-api-external: tcp connection to a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:53:08Z"
    - latency: 7.989489ms
      message: 'load-balancer-api-external: resolved host name a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:53:08Z"
    - latency: 17.053274ms
      message: 'load-balancer-api-external: tcp connection to a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:52:08Z"
    - latency: 8.80025ms
      message: 'load-balancer-api-external: resolved host name a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:52:08Z"
    - latency: 16.705412ms
      message: 'load-balancer-api-external: tcp connection to a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:51:08Z"
    - latency: 8.012668ms
      message: 'load-balancer-api-external: resolved host name a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:51:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:43:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 44a3c3a4-f863-4413-b7e5-e2403d413a98
    resourceVersion: "33348"
    uid: 90c04cec-9380-440f-9f1d-33dd5a9bbd28
  spec:
    sourcePod: network-check-source-6f78d59f99-575jz
    targetEndpoint: a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:49:08Z"
      message: 'load-balancer-api-internal: tcp connection to a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.930938ms
      message: 'load-balancer-api-internal: tcp connection to a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:55:08Z"
    - latency: 7.875914ms
      message: 'load-balancer-api-internal: resolved host name a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:55:08Z"
    - latency: 16.349208ms
      message: 'load-balancer-api-internal: tcp connection to a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:54:08Z"
    - latency: 6.597535ms
      message: 'load-balancer-api-internal: resolved host name a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:54:08Z"
    - latency: 17.057858ms
      message: 'load-balancer-api-internal: tcp connection to a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:53:08Z"
    - latency: 8.010464ms
      message: 'load-balancer-api-internal: resolved host name a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:53:08Z"
    - latency: 18.148883ms
      message: 'load-balancer-api-internal: tcp connection to a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:52:08Z"
    - latency: 8.746589ms
      message: 'load-balancer-api-internal: resolved host name a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:52:08Z"
    - latency: 17.687859ms
      message: 'load-balancer-api-internal: tcp connection to a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:51:08Z"
    - latency: 8.062278ms
      message: 'load-balancer-api-internal: resolved host name a75d8716bb1934dc09a52d7e9a0de2b2-bb279796156621f6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:51:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:43:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-network-check-target-ip-10-0-135-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 44a3c3a4-f863-4413-b7e5-e2403d413a98
    resourceVersion: "32332"
    uid: 18d7fbc7-bd55-4817-b9d6-e79a4ca552a4
  spec:
    sourcePod: network-check-source-6f78d59f99-575jz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:50:08Z"
      message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.968332ms
      message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:53:08Z"
    - latency: 1.992007ms
      message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:52:08Z"
    - latency: 1.735639ms
      message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:51:08Z"
    - latency: 1.769819ms
      message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:50:08Z"
    - latency: 2.124231ms
      message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:49:08Z"
    - latency: 1.988706ms
      message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:48:08Z"
    - latency: 1.891833ms
      message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:47:08Z"
    - latency: 1.896136ms
      message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:46:08Z"
    - latency: 1.877147ms
      message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:45:08Z"
    - latency: 1.581186ms
      message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:44:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:43:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-network-check-target-ip-10-0-137-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 44a3c3a4-f863-4413-b7e5-e2403d413a98
    resourceVersion: "32331"
    uid: 5033bf27-a50a-4f1e-b1cd-0a6ff3519e8d
  spec:
    sourcePod: network-check-source-6f78d59f99-575jz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:50:08Z"
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 756.069µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:53:08Z"
    - latency: 1.008371ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:52:08Z"
    - latency: 838.041µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:51:08Z"
    - latency: 792.238µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:50:08Z"
    - latency: 985.618µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:49:08Z"
    - latency: 844.064µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:48:08Z"
    - latency: 1.011528ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:47:08Z"
    - latency: 867.786µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:46:08Z"
    - latency: 772.944µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:45:08Z"
    - latency: 783.877µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:44:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:43:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-network-check-target-ip-10-0-143-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 44a3c3a4-f863-4413-b7e5-e2403d413a98
    resourceVersion: "32333"
    uid: 46867611-a200-40a6-a5e3-a7aff3f2db85
  spec:
    sourcePod: network-check-source-6f78d59f99-575jz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:50:08Z"
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.490807ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:53:08Z"
    - latency: 2.206543ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:52:08Z"
    - latency: 3.003639ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:51:08Z"
    - latency: 1.979185ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:50:08Z"
    - latency: 2.173208ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:49:08Z"
    - latency: 2.286196ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:48:08Z"
    - latency: 2.119529ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:47:08Z"
    - latency: 2.623159ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:46:08Z"
    - latency: 2.115491ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:45:08Z"
    - latency: 2.046668ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:44:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:43:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 44a3c3a4-f863-4413-b7e5-e2403d413a98
    resourceVersion: "33346"
    uid: 318cd878-cdb3-4230-95fe-58c6099abc70
  spec:
    sourcePod: network-check-source-6f78d59f99-575jz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:49:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 807.147µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:55:08Z"
    - latency: 1.950543ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:55:08Z"
    - latency: 790.429µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:54:08Z"
    - latency: 1.926702ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:54:08Z"
    - latency: 966.5µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:53:08Z"
    - latency: 1.680026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:53:08Z"
    - latency: 1.113996ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:52:08Z"
    - latency: 1.899314ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:52:08Z"
    - latency: 816.756µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:51:08Z"
    - latency: 1.651695ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:51:08Z"
kind: List
metadata:
  resourceVersion: ""