apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:15:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-247-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-247.ec2.internal
      uid: de6e9356-8894-41c5-b319-1de66c95630b
    resourceVersion: "44114"
    uid: ed6d3aa9-183c-476d-9fef-5b9b2a6076a4
  spec:
    sourcePod: network-check-source-8894fc9bd-pts4j
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:22:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.012791ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:43:27Z"
    - latency: 1.374566ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:42:27Z"
    - latency: 1.385362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:41:27Z"
    - latency: 1.062294ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:40:27Z"
    - latency: 904.267µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:39:27Z"
    - latency: 1.102483ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:38:27Z"
    - latency: 943.437µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:37:27Z"
    - latency: 1.003258ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:36:27Z"
    - latency: 1.141579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:35:27Z"
    - latency: 781.468µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:15:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-247-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-247.ec2.internal
      uid: de6e9356-8894-41c5-b319-1de66c95630b
    resourceVersion: "46323"
    uid: 53178f97-d409-4cc7-8fb4-9abb87b447db
  spec:
    sourcePod: network-check-source-8894fc9bd-pts4j
    targetEndpoint: acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:21:27Z"
      message: 'load-balancer-api-external: tcp connection to acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.024276ms
      message: 'load-balancer-api-external: tcp connection to acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:45:27Z"
    - latency: 8.26448ms
      message: 'load-balancer-api-external: resolved host name acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:45:27Z"
    - latency: 5.463209ms
      message: 'load-balancer-api-external: tcp connection to acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:44:27Z"
    - latency: 10.680779ms
      message: 'load-balancer-api-external: resolved host name acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:44:27Z"
    - latency: 4.692325ms
      message: 'load-balancer-api-external: tcp connection to acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:43:27Z"
    - latency: 7.691445ms
      message: 'load-balancer-api-external: resolved host name acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:43:27Z"
    - latency: 4.700073ms
      message: 'load-balancer-api-external: tcp connection to acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:42:27Z"
    - latency: 8.913219ms
      message: 'load-balancer-api-external: resolved host name acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:42:27Z"
    - latency: 5.158191ms
      message: 'load-balancer-api-external: tcp connection to acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:41:27Z"
    - latency: 8.352675ms
      message: 'load-balancer-api-external: resolved host name acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:41:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:15:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-247-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-247.ec2.internal
      uid: de6e9356-8894-41c5-b319-1de66c95630b
    resourceVersion: "46324"
    uid: 5fa017bd-71de-45d4-bb0b-19e62e5b6c0e
  spec:
    sourcePod: network-check-source-8894fc9bd-pts4j
    targetEndpoint: acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:21:27Z"
      message: 'load-balancer-api-internal: tcp connection to acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.993314ms
      message: 'load-balancer-api-internal: tcp connection to acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:45:27Z"
    - latency: 8.192887ms
      message: 'load-balancer-api-internal: resolved host name acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:45:27Z"
    - latency: 3.860419ms
      message: 'load-balancer-api-internal: tcp connection to acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:44:27Z"
    - latency: 10.720954ms
      message: 'load-balancer-api-internal: resolved host name acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:44:27Z"
    - latency: 4.564922ms
      message: 'load-balancer-api-internal: tcp connection to acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:43:27Z"
    - latency: 7.618118ms
      message: 'load-balancer-api-internal: resolved host name acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:43:27Z"
    - latency: 3.664697ms
      message: 'load-balancer-api-internal: tcp connection to acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:42:27Z"
    - latency: 8.976635ms
      message: 'load-balancer-api-internal: resolved host name acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:42:27Z"
    - latency: 5.178945ms
      message: 'load-balancer-api-internal: tcp connection to acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:41:27Z"
    - latency: 8.306093ms
      message: 'load-balancer-api-internal: resolved host name acb2cacfcff734b81a29d4d5c54c680e-9b32b952126d008a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:41:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:15:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-247-to-network-check-target-ip-10-0-129-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-247.ec2.internal
      uid: de6e9356-8894-41c5-b319-1de66c95630b
    resourceVersion: "44113"
    uid: 708266f0-6fc1-47dd-b726-fb1b3a5fcf57
  spec:
    sourcePod: network-check-source-8894fc9bd-pts4j
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:22:27Z"
      message: 'network-check-target-ip-10-0-129-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.294353ms
      message: 'network-check-target-ip-10-0-129-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:43:27Z"
    - latency: 1.093286ms
      message: 'network-check-target-ip-10-0-129-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:42:27Z"
    - latency: 1.14867ms
      message: 'network-check-target-ip-10-0-129-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:41:27Z"
    - latency: 874.847µs
      message: 'network-check-target-ip-10-0-129-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:40:27Z"
    - latency: 865.533µs
      message: 'network-check-target-ip-10-0-129-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:39:27Z"
    - latency: 1.307723ms
      message: 'network-check-target-ip-10-0-129-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:38:27Z"
    - latency: 727.626µs
      message: 'network-check-target-ip-10-0-129-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:37:27Z"
    - latency: 914.494µs
      message: 'network-check-target-ip-10-0-129-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:36:27Z"
    - latency: 1.310532ms
      message: 'network-check-target-ip-10-0-129-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:35:27Z"
    - latency: 921.87µs
      message: 'network-check-target-ip-10-0-129-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:15:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-247-to-network-check-target-ip-10-0-134-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-247.ec2.internal
      uid: de6e9356-8894-41c5-b319-1de66c95630b
    resourceVersion: "44111"
    uid: 7fcd21cd-e082-4595-955d-322c805540a7
  spec:
    sourcePod: network-check-source-8894fc9bd-pts4j
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:22:27Z"
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.830568ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:43:27Z"
    - latency: 1.819584ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:42:27Z"
    - latency: 1.743624ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:41:27Z"
    - latency: 1.585278ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:40:27Z"
    - latency: 1.858613ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:39:27Z"
    - latency: 1.914594ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:38:27Z"
    - latency: 1.462305ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:37:27Z"
    - latency: 2.016765ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:36:27Z"
    - latency: 1.664653ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:35:27Z"
    - latency: 1.949019ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:15:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-247-to-network-check-target-ip-10-0-141-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-247.ec2.internal
      uid: de6e9356-8894-41c5-b319-1de66c95630b
    resourceVersion: "44112"
    uid: db3459e0-9cdd-41fd-b791-d100dec63331
  spec:
    sourcePod: network-check-source-8894fc9bd-pts4j
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:22:27Z"
      message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.94154ms
      message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:43:27Z"
    - latency: 2.242065ms
      message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:42:27Z"
    - latency: 2.239008ms
      message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:41:27Z"
    - latency: 2.022842ms
      message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:40:27Z"
    - latency: 1.915167ms
      message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:39:27Z"
    - latency: 2.073712ms
      message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:38:27Z"
    - latency: 1.830058ms
      message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:37:27Z"
    - latency: 2.210169ms
      message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:36:27Z"
    - latency: 2.194887ms
      message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:35:27Z"
    - latency: 2.295564ms
      message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:15:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-247-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-247.ec2.internal
      uid: de6e9356-8894-41c5-b319-1de66c95630b
    resourceVersion: "46322"
    uid: d373be7f-4c4b-4788-b6b2-eb89c3db3d89
  spec:
    sourcePod: network-check-source-8894fc9bd-pts4j
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:21:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 840.577µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:45:27Z"
    - latency: 2.093218ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:45:27Z"
    - latency: 818.025µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:44:27Z"
    - latency: 1.865356ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:44:27Z"
    - latency: 1.181544ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:43:27Z"
    - latency: 1.690479ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:43:27Z"
    - latency: 827.423µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:42:27Z"
    - latency: 1.669246ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:42:27Z"
    - latency: 1.012108ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:41:27Z"
    - latency: 1.713313ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T20:41:27Z"
kind: List
metadata:
  resourceVersion: ""