apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-142.ec2.internal
      uid: e7d261f9-046e-478d-8d29-ef1e6f98fdcd
    resourceVersion: "74394"
    uid: 9c3df800-5842-4d08-b844-3b242b2eac8d
  spec:
    sourcePod: network-check-source-7d88cb55d8-5rrkj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:18:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.239869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T23:00:42Z"
    - latency: 1.178453ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:59:42Z"
    - latency: 1.444535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:58:42Z"
    - latency: 853.215µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:57:42Z"
    - latency: 862.62µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:56:42Z"
    - latency: 1.230028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:42Z"
    - latency: 913.411µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:54:42Z"
    - latency: 1.483048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:53:42Z"
    - latency: 1.19309ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:52:42Z"
    - latency: 1.322613ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-142.ec2.internal
      uid: e7d261f9-046e-478d-8d29-ef1e6f98fdcd
    resourceVersion: "72063"
    uid: b75df009-d40e-4b4b-961c-943ccc1bbc48
  spec:
    sourcePod: network-check-source-7d88cb55d8-5rrkj
    targetEndpoint: aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:17:42Z"
      message: 'load-balancer-api-external: tcp connection to aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.590093ms
      message: 'load-balancer-api-external: tcp connection to aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:59:42Z"
    - latency: 6.72446ms
      message: 'load-balancer-api-external: resolved host name aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:59:42Z"
    - latency: 4.463245ms
      message: 'load-balancer-api-external: tcp connection to aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:58:42Z"
    - latency: 9.421435ms
      message: 'load-balancer-api-external: resolved host name aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:58:42Z"
    - latency: 4.073936ms
      message: 'load-balancer-api-external: tcp connection to aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:57:42Z"
    - latency: 9.714529ms
      message: 'load-balancer-api-external: resolved host name aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:57:42Z"
    - latency: 4.998798ms
      message: 'load-balancer-api-external: tcp connection to aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:56:42Z"
    - latency: 8.412717ms
      message: 'load-balancer-api-external: resolved host name aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:56:42Z"
    - latency: 4.240638ms
      message: 'load-balancer-api-external: tcp connection to aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:42Z"
    - latency: 8.97786ms
      message: 'load-balancer-api-external: resolved host name aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:55:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-142.ec2.internal
      uid: e7d261f9-046e-478d-8d29-ef1e6f98fdcd
    resourceVersion: "72064"
    uid: 98c230c2-97ad-4937-8657-e0b726fafe03
  spec:
    sourcePod: network-check-source-7d88cb55d8-5rrkj
    targetEndpoint: aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:17:42Z"
      message: 'load-balancer-api-internal: tcp connection to aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.589959ms
      message: 'load-balancer-api-internal: tcp connection to aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:59:42Z"
    - latency: 6.743718ms
      message: 'load-balancer-api-internal: resolved host name aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:59:42Z"
    - latency: 3.283437ms
      message: 'load-balancer-api-internal: tcp connection to aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:58:42Z"
    - latency: 9.526857ms
      message: 'load-balancer-api-internal: resolved host name aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:58:42Z"
    - latency: 3.138817ms
      message: 'load-balancer-api-internal: tcp connection to aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:57:42Z"
    - latency: 9.743301ms
      message: 'load-balancer-api-internal: resolved host name aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:57:42Z"
    - latency: 4.997296ms
      message: 'load-balancer-api-internal: tcp connection to aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:56:42Z"
    - latency: 8.462211ms
      message: 'load-balancer-api-internal: resolved host name aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:56:42Z"
    - latency: 4.164046ms
      message: 'load-balancer-api-internal: tcp connection to aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:42Z"
    - latency: 8.993613ms
      message: 'load-balancer-api-internal: resolved host name aa321e8be2a4a411ba3d855d4c892c96-0e787d0f5522d381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:55:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-142-to-network-check-target-ip-10-0-128-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-142.ec2.internal
      uid: e7d261f9-046e-478d-8d29-ef1e6f98fdcd
    resourceVersion: "74393"
    uid: f00776f3-d009-455d-a441-a482cccffb04
  spec:
    sourcePod: network-check-source-7d88cb55d8-5rrkj
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:18:42Z"
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.134852ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T23:00:42Z"
    - latency: 2.414506ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:59:42Z"
    - latency: 2.502816ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:58:42Z"
    - latency: 1.988216ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:57:42Z"
    - latency: 2.43005ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:56:42Z"
    - latency: 2.017365ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:42Z"
    - latency: 1.940548ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:54:42Z"
    - latency: 2.259355ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:53:42Z"
    - latency: 2.5114ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:52:42Z"
    - latency: 2.368803ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-142-to-network-check-target-ip-10-0-133-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-142.ec2.internal
      uid: e7d261f9-046e-478d-8d29-ef1e6f98fdcd
    resourceVersion: "74391"
    uid: 57943fcc-3e3d-4a77-8089-92f54715b081
  spec:
    sourcePod: network-check-source-7d88cb55d8-5rrkj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:18:42Z"
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.054366ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T23:00:42Z"
    - latency: 1.16557ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:59:42Z"
    - latency: 1.606941ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:58:42Z"
    - latency: 845.894µs
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:57:42Z"
    - latency: 1.067829ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:56:42Z"
    - latency: 980.244µs
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:42Z"
    - latency: 946.207µs
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:54:42Z"
    - latency: 1.192649ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:53:42Z"
    - latency: 969.971µs
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:52:42Z"
    - latency: 965.418µs
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-142-to-network-check-target-ip-10-0-134-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-142.ec2.internal
      uid: e7d261f9-046e-478d-8d29-ef1e6f98fdcd
    resourceVersion: "74392"
    uid: 75a1fdd4-78d6-40b9-aaf6-21c44a61ebdd
  spec:
    sourcePod: network-check-source-7d88cb55d8-5rrkj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:18:42Z"
      message: 'network-check-target-ip-10-0-134-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.060076ms
      message: 'network-check-target-ip-10-0-134-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T23:00:42Z"
    - latency: 1.897439ms
      message: 'network-check-target-ip-10-0-134-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:59:42Z"
    - latency: 1.929599ms
      message: 'network-check-target-ip-10-0-134-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:58:42Z"
    - latency: 1.517015ms
      message: 'network-check-target-ip-10-0-134-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:57:42Z"
    - latency: 1.938649ms
      message: 'network-check-target-ip-10-0-134-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:56:42Z"
    - latency: 1.858775ms
      message: 'network-check-target-ip-10-0-134-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:42Z"
    - latency: 1.549574ms
      message: 'network-check-target-ip-10-0-134-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:54:42Z"
    - latency: 1.960331ms
      message: 'network-check-target-ip-10-0-134-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:53:42Z"
    - latency: 1.903218ms
      message: 'network-check-target-ip-10-0-134-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:52:42Z"
    - latency: 2.012671ms
      message: 'network-check-target-ip-10-0-134-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T22:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-142.ec2.internal
      uid: e7d261f9-046e-478d-8d29-ef1e6f98fdcd
    resourceVersion: "72062"
    uid: 9ec847e0-afac-4f81-a10f-148b68ab6bdf
  spec:
    sourcePod: network-check-source-7d88cb55d8-5rrkj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T22:17:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.107347ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:59:42Z"
    - latency: 1.731848ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:59:42Z"
    - latency: 977.612µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:58:42Z"
    - latency: 2.252683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:58:42Z"
    - latency: 860.751µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:57:42Z"
    - latency: 1.925597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:57:42Z"
    - latency: 861.537µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:56:42Z"
    - latency: 1.971332ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:56:42Z"
    - latency: 892.389µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T22:55:42Z"
    - latency: 2.017407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T22:55:42Z"
kind: List
metadata:
  resourceVersion: ""