apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:19:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-178-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-178.ec2.internal
      uid: 233cbe41-51a3-49bf-a10b-d13e647204b0
    resourceVersion: "54175"
    uid: 7a856f79-25d2-4c6a-82bd-a0764d562638
  spec:
    sourcePod: network-check-source-685456655f-t6qbv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:26:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.02763ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:47:50Z"
    - latency: 816.217µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:46:50Z"
    - latency: 882.919µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:45:50Z"
    - latency: 1.013355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:44:50Z"
    - latency: 1.404405ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:43:50Z"
    - latency: 851.882µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:42:50Z"
    - latency: 1.08372ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:41:50Z"
    - latency: 969.996µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:40:50Z"
    - latency: 1.179434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:39:50Z"
    - latency: 880.486µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:38:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:19:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-178-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-178.ec2.internal
      uid: 233cbe41-51a3-49bf-a10b-d13e647204b0
    resourceVersion: "55718"
    uid: 4ecd5653-dbcc-40a8-adac-b6a1f5882705
  spec:
    sourcePod: network-check-source-685456655f-t6qbv
    targetEndpoint: abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:25:50Z"
      message: 'load-balancer-api-external: tcp connection to abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.536367ms
      message: 'load-balancer-api-external: tcp connection to abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:49:50Z"
    - latency: 8.514311ms
      message: 'load-balancer-api-external: resolved host name abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:49:50Z"
    - latency: 3.17541ms
      message: 'load-balancer-api-external: tcp connection to abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:48:50Z"
    - latency: 7.84974ms
      message: 'load-balancer-api-external: resolved host name abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:48:50Z"
    - latency: 5.480129ms
      message: 'load-balancer-api-external: tcp connection to abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:47:50Z"
    - latency: 8.831998ms
      message: 'load-balancer-api-external: resolved host name abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:47:50Z"
    - latency: 5.10923ms
      message: 'load-balancer-api-external: tcp connection to abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:46:50Z"
    - latency: 8.567854ms
      message: 'load-balancer-api-external: resolved host name abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:46:50Z"
    - latency: 5.70996ms
      message: 'load-balancer-api-external: tcp connection to abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:45:50Z"
    - latency: 10.125778ms
      message: 'load-balancer-api-external: resolved host name abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:45:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:19:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-178-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-178.ec2.internal
      uid: 233cbe41-51a3-49bf-a10b-d13e647204b0
    resourceVersion: "55717"
    uid: 589dbe0b-28bf-4d5e-8c16-13c4280f9e97
  spec:
    sourcePod: network-check-source-685456655f-t6qbv
    targetEndpoint: abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:25:50Z"
      message: 'load-balancer-api-internal: tcp connection to abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.528917ms
      message: 'load-balancer-api-internal: tcp connection to abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:49:50Z"
    - latency: 8.532969ms
      message: 'load-balancer-api-internal: resolved host name abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:49:50Z"
    - latency: 3.775119ms
      message: 'load-balancer-api-internal: tcp connection to abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:48:50Z"
    - latency: 7.816831ms
      message: 'load-balancer-api-internal: resolved host name abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:48:50Z"
    - latency: 5.219702ms
      message: 'load-balancer-api-internal: tcp connection to abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:47:50Z"
    - latency: 8.776895ms
      message: 'load-balancer-api-internal: resolved host name abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:47:50Z"
    - latency: 4.401447ms
      message: 'load-balancer-api-internal: tcp connection to abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:46:50Z"
    - latency: 8.633844ms
      message: 'load-balancer-api-internal: resolved host name abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:46:50Z"
    - latency: 5.705924ms
      message: 'load-balancer-api-internal: tcp connection to abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:45:50Z"
    - latency: 10.17567ms
      message: 'load-balancer-api-internal: resolved host name abdd625b762ee4b5ca3ea7424b688376-29625ba4858ea84c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:45:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:19:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-178-to-network-check-target-ip-10-0-132-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-178.ec2.internal
      uid: 233cbe41-51a3-49bf-a10b-d13e647204b0
    resourceVersion: "54173"
    uid: ba3fe06a-6486-4aff-89f1-dd2dc70fa452
  spec:
    sourcePod: network-check-source-685456655f-t6qbv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:26:50Z"
      message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.379522ms
      message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:47:50Z"
    - latency: 2.180256ms
      message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:46:50Z"
    - latency: 2.046941ms
      message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:45:50Z"
    - latency: 2.026937ms
      message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:44:50Z"
    - latency: 1.811292ms
      message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:43:50Z"
    - latency: 2.133629ms
      message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:42:50Z"
    - latency: 2.351779ms
      message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:41:50Z"
    - latency: 2.338824ms
      message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:40:50Z"
    - latency: 1.989009ms
      message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:39:50Z"
    - latency: 2.28817ms
      message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:38:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:19:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-178-to-network-check-target-ip-10-0-133-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-178.ec2.internal
      uid: 233cbe41-51a3-49bf-a10b-d13e647204b0
    resourceVersion: "54174"
    uid: 3f83a522-a64d-492e-9f5f-666fa97c931a
  spec:
    sourcePod: network-check-source-685456655f-t6qbv
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:26:50Z"
      message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.938162ms
      message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:47:50Z"
    - latency: 2.03713ms
      message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:46:50Z"
    - latency: 2.378263ms
      message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:45:50Z"
    - latency: 2.192362ms
      message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:44:50Z"
    - latency: 2.12304ms
      message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:43:50Z"
    - latency: 2.582368ms
      message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:42:50Z"
    - latency: 2.015562ms
      message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:41:50Z"
    - latency: 2.238962ms
      message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:40:50Z"
    - latency: 1.864704ms
      message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:39:50Z"
    - latency: 2.219406ms
      message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:38:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:19:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-178-to-network-check-target-ip-10-0-142-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-178.ec2.internal
      uid: 233cbe41-51a3-49bf-a10b-d13e647204b0
    resourceVersion: "54172"
    uid: 8c69d2af-63d5-4496-ac1e-71a87d42b3ac
  spec:
    sourcePod: network-check-source-685456655f-t6qbv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:26:50Z"
      message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 840.899µs
      message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:47:50Z"
    - latency: 1.101467ms
      message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:46:50Z"
    - latency: 932.233µs
      message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:45:50Z"
    - latency: 924.013µs
      message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:44:50Z"
    - latency: 952.526µs
      message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:43:50Z"
    - latency: 1.116777ms
      message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:42:50Z"
    - latency: 1.610398ms
      message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:41:50Z"
    - latency: 1.255506ms
      message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:40:50Z"
    - latency: 1.262456ms
      message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:39:50Z"
    - latency: 1.179848ms
      message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:38:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:19:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-178-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-178.ec2.internal
      uid: 233cbe41-51a3-49bf-a10b-d13e647204b0
    resourceVersion: "55716"
    uid: ad883fd1-b738-4db2-ac92-93e8a4f06482
  spec:
    sourcePod: network-check-source-685456655f-t6qbv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:25:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 756.974µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:49:50Z"
    - latency: 1.812033ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:49:50Z"
    - latency: 1.590897ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:48:50Z"
    - latency: 1.768786ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:48:50Z"
    - latency: 1.03084ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:47:50Z"
    - latency: 1.838091ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:47:50Z"
    - latency: 905.845µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:46:50Z"
    - latency: 2.127874ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:46:50Z"
    - latency: 962.927µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:45:50Z"
    - latency: 1.828611ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:45:50Z"
kind: List
metadata:
  resourceVersion: ""