apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:47:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: d6d8e452-78c2-47ea-800e-a2150506ce54
    resourceVersion: "54230"
    uid: e4b0b1bf-6fbd-4b9c-acf9-31124c44accc
  spec:
    sourcePod: network-check-source-989f8b8dc-cm8lr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:54:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.153674ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:22:13Z"
    - latency: 1.25688ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:21:13Z"
    - latency: 1.087169ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:20:13Z"
    - latency: 1.299101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:19:13Z"
    - latency: 1.152996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:18:13Z"
    - latency: 1.028764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:17:13Z"
    - latency: 1.370307ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:16:13Z"
    - latency: 1.115456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:15:13Z"
    - latency: 1.017893ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:14:13Z"
    - latency: 1.051519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:13:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:47:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: d6d8e452-78c2-47ea-800e-a2150506ce54
    resourceVersion: "55228"
    uid: 6c163381-10e8-465e-933d-6aaa5839049c
  spec:
    sourcePod: network-check-source-989f8b8dc-cm8lr
    targetEndpoint: af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:53:13Z"
      message: 'load-balancer-api-external: tcp connection to af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.805634ms
      message: 'load-balancer-api-external: tcp connection to af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:23:13Z"
    - latency: 7.276765ms
      message: 'load-balancer-api-external: resolved host name af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:23:13Z"
    - latency: 5.834476ms
      message: 'load-balancer-api-external: tcp connection to af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:22:13Z"
    - latency: 7.215601ms
      message: 'load-balancer-api-external: resolved host name af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:22:13Z"
    - latency: 4.94296ms
      message: 'load-balancer-api-external: tcp connection to af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:21:13Z"
    - latency: 6.786307ms
      message: 'load-balancer-api-external: resolved host name af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:21:13Z"
    - latency: 4.121803ms
      message: 'load-balancer-api-external: tcp connection to af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:20:13Z"
    - latency: 6.578946ms
      message: 'load-balancer-api-external: resolved host name af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:20:13Z"
    - latency: 5.089492ms
      message: 'load-balancer-api-external: tcp connection to af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:19:13Z"
    - latency: 6.276461ms
      message: 'load-balancer-api-external: resolved host name af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:19:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:47:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: d6d8e452-78c2-47ea-800e-a2150506ce54
    resourceVersion: "55227"
    uid: d021e4c3-d168-4fc6-8eef-ba229c7e62c9
  spec:
    sourcePod: network-check-source-989f8b8dc-cm8lr
    targetEndpoint: af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:53:13Z"
      message: 'load-balancer-api-internal: tcp connection to af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.815227ms
      message: 'load-balancer-api-internal: tcp connection to af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:23:13Z"
    - latency: 7.186152ms
      message: 'load-balancer-api-internal: resolved host name af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:23:13Z"
    - latency: 5.895492ms
      message: 'load-balancer-api-internal: tcp connection to af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:22:13Z"
    - latency: 7.069564ms
      message: 'load-balancer-api-internal: resolved host name af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:22:13Z"
    - latency: 3.697041ms
      message: 'load-balancer-api-internal: tcp connection to af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:21:13Z"
    - latency: 6.727365ms
      message: 'load-balancer-api-internal: resolved host name af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:21:13Z"
    - latency: 4.157997ms
      message: 'load-balancer-api-internal: tcp connection to af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:20:13Z"
    - latency: 6.432784ms
      message: 'load-balancer-api-internal: resolved host name af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:20:13Z"
    - latency: 5.170421ms
      message: 'load-balancer-api-internal: tcp connection to af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:19:13Z"
    - latency: 6.184391ms
      message: 'load-balancer-api-internal: resolved host name af210c342337d4e888d1669661050f98-b77d2e8593d25db1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:19:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:47:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-network-check-target-ip-10-0-136-171
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: d6d8e452-78c2-47ea-800e-a2150506ce54
    resourceVersion: "54227"
    uid: 03fdcf70-c066-48c4-94eb-030420544f54
  spec:
    sourcePod: network-check-source-989f8b8dc-cm8lr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:54:13Z"
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.439236ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:22:13Z"
    - latency: 2.294858ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:21:13Z"
    - latency: 2.553539ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:20:13Z"
    - latency: 2.406323ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:19:13Z"
    - latency: 2.500328ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:18:13Z"
    - latency: 2.163963ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:17:13Z"
    - latency: 2.243384ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:16:13Z"
    - latency: 2.61577ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:15:13Z"
    - latency: 2.285698ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:14:13Z"
    - latency: 2.400786ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:13:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:47:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-network-check-target-ip-10-0-138-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: d6d8e452-78c2-47ea-800e-a2150506ce54
    resourceVersion: "54229"
    uid: 7ed11e91-6283-4c4d-baed-9ff265bfa460
  spec:
    sourcePod: network-check-source-989f8b8dc-cm8lr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:54:13Z"
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.750418ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:22:13Z"
    - latency: 2.394451ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:21:13Z"
    - latency: 2.429396ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:20:13Z"
    - latency: 2.237926ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:19:13Z"
    - latency: 2.340139ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:18:13Z"
    - latency: 2.058106ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:17:13Z"
    - latency: 2.300845ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:16:13Z"
    - latency: 2.45709ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:15:13Z"
    - latency: 2.130438ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:14:13Z"
    - latency: 2.282438ms
      message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:13:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:47:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-network-check-target-ip-10-0-141-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: d6d8e452-78c2-47ea-800e-a2150506ce54
    resourceVersion: "54228"
    uid: 806c2014-2051-478c-904f-217e21ca9d0f
  spec:
    sourcePod: network-check-source-989f8b8dc-cm8lr
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:54:13Z"
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.46149ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:22:13Z"
    - latency: 896.676µs
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:21:13Z"
    - latency: 1.020174ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:20:13Z"
    - latency: 891.248µs
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:19:13Z"
    - latency: 914.802µs
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:18:13Z"
    - latency: 1.218233ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:17:13Z"
    - latency: 1.411146ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:16:13Z"
    - latency: 933.234µs
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:15:13Z"
    - latency: 908.037µs
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:14:13Z"
    - latency: 853.997µs
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:13:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:47:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: d6d8e452-78c2-47ea-800e-a2150506ce54
    resourceVersion: "55226"
    uid: 88505ba8-c5c7-404e-9adb-fa189dc7e5bc
  spec:
    sourcePod: network-check-source-989f8b8dc-cm8lr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:53:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 752.447µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:23:13Z"
    - latency: 1.667642ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:23:13Z"
    - latency: 920.654µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:22:13Z"
    - latency: 2.064339ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:22:13Z"
    - latency: 897.755µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:21:13Z"
    - latency: 2.002086ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:21:13Z"
    - latency: 1.063179ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:20:13Z"
    - latency: 1.748307ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:20:13Z"
    - latency: 1.283772ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:19:13Z"
    - latency: 1.881031ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:19:13Z"
kind: List
metadata:
  resourceVersion: ""