apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T04:43:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 3578907e-6a82-487a-b7c4-19156a28562e
    resourceVersion: "38311"
    uid: 7c33083d-9a18-4b60-a572-f471fed4d86b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rffhs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:51:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.068569ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:05:00Z"
    - latency: 1.291966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:04:00Z"
    - latency: 1.103801ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:03:00Z"
    - latency: 1.2153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:02:00Z"
    - latency: 851.496µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:01:00Z"
    - latency: 1.114968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:00:00Z"
    - latency: 895.114µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:59:00Z"
    - latency: 1.004886ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:58:00Z"
    - latency: 1.44598ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:57:00Z"
    - latency: 1.381045ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:56:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T04:43:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 3578907e-6a82-487a-b7c4-19156a28562e
    resourceVersion: "35069"
    uid: 5f579a47-cc48-450f-8fde-773bfd780e6d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rffhs
    targetEndpoint: a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:50:00Z"
      message: 'load-balancer-api-external: tcp connection to a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.817415ms
      message: 'load-balancer-api-external: tcp connection to a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:02:00Z"
    - latency: 6.503959ms
      message: 'load-balancer-api-external: resolved host name a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T05:02:00Z"
    - latency: 5.135601ms
      message: 'load-balancer-api-external: tcp connection to a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:01:00Z"
    - latency: 7.227503ms
      message: 'load-balancer-api-external: resolved host name a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T05:01:00Z"
    - latency: 5.044905ms
      message: 'load-balancer-api-external: tcp connection to a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:00:00Z"
    - latency: 6.897925ms
      message: 'load-balancer-api-external: resolved host name a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T05:00:00Z"
    - latency: 4.415732ms
      message: 'load-balancer-api-external: tcp connection to a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:59:00Z"
    - latency: 7.328876ms
      message: 'load-balancer-api-external: resolved host name a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:59:00Z"
    - latency: 3.797388ms
      message: 'load-balancer-api-external: tcp connection to a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:58:00Z"
    - latency: 7.042522ms
      message: 'load-balancer-api-external: resolved host name a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:58:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T04:43:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 3578907e-6a82-487a-b7c4-19156a28562e
    resourceVersion: "35070"
    uid: 7fcf474a-05b2-41fd-bc1e-3184c6a5ad6d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rffhs
    targetEndpoint: a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:50:00Z"
      message: 'load-balancer-api-internal: tcp connection to a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.53803ms
      message: 'load-balancer-api-internal: tcp connection to a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:02:00Z"
    - latency: 6.692895ms
      message: 'load-balancer-api-internal: resolved host name a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T05:02:00Z"
    - latency: 4.49622ms
      message: 'load-balancer-api-internal: tcp connection to a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:01:00Z"
    - latency: 7.293401ms
      message: 'load-balancer-api-internal: resolved host name a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T05:01:00Z"
    - latency: 4.50227ms
      message: 'load-balancer-api-internal: tcp connection to a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:00:00Z"
    - latency: 6.804898ms
      message: 'load-balancer-api-internal: resolved host name a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T05:00:00Z"
    - latency: 3.642088ms
      message: 'load-balancer-api-internal: tcp connection to a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:59:00Z"
    - latency: 7.502263ms
      message: 'load-balancer-api-internal: resolved host name a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:59:00Z"
    - latency: 4.924758ms
      message: 'load-balancer-api-internal: tcp connection to a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:58:00Z"
    - latency: 7.179992ms
      message: 'load-balancer-api-internal: resolved host name a4823e18fce894e0a87355c8ec2b7c5a-4ba7ca3ad4ef8132.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:58:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T04:43:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-network-check-target-ip-10-0-128-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 3578907e-6a82-487a-b7c4-19156a28562e
    resourceVersion: "38310"
    uid: 0e580b84-14b5-41af-b05b-00172cc62a29
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rffhs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:51:00Z"
      message: 'network-check-target-ip-10-0-128-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.385836ms
      message: 'network-check-target-ip-10-0-128-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:05:00Z"
    - latency: 2.101001ms
      message: 'network-check-target-ip-10-0-128-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:04:00Z"
    - latency: 2.072781ms
      message: 'network-check-target-ip-10-0-128-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:03:00Z"
    - latency: 1.84688ms
      message: 'network-check-target-ip-10-0-128-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:02:00Z"
    - latency: 1.981992ms
      message: 'network-check-target-ip-10-0-128-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:01:00Z"
    - latency: 1.707686ms
      message: 'network-check-target-ip-10-0-128-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:00:00Z"
    - latency: 1.934985ms
      message: 'network-check-target-ip-10-0-128-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:59:00Z"
    - latency: 2.13513ms
      message: 'network-check-target-ip-10-0-128-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:58:00Z"
    - latency: 2.210558ms
      message: 'network-check-target-ip-10-0-128-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:57:00Z"
    - latency: 2.104915ms
      message: 'network-check-target-ip-10-0-128-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:56:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T04:43:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-network-check-target-ip-10-0-136-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 3578907e-6a82-487a-b7c4-19156a28562e
    resourceVersion: "38309"
    uid: b4708f04-370a-41e4-981a-347c748b58ae
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rffhs
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:51:00Z"
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.216627ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:05:00Z"
    - latency: 2.270957ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:04:00Z"
    - latency: 2.327344ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:03:00Z"
    - latency: 2.168484ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:02:00Z"
    - latency: 2.365686ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:01:00Z"
    - latency: 2.259331ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:00:00Z"
    - latency: 2.286446ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:59:00Z"
    - latency: 2.439481ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:58:00Z"
    - latency: 2.142865ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:57:00Z"
    - latency: 1.989672ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:56:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T04:43:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-network-check-target-ip-10-0-139-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 3578907e-6a82-487a-b7c4-19156a28562e
    resourceVersion: "38308"
    uid: 5be8c47d-a7ec-45f9-9717-ff79488a93de
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rffhs
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:51:00Z"
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.279218ms
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:05:00Z"
    - latency: 1.44228ms
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:04:00Z"
    - latency: 973.741µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:03:00Z"
    - latency: 863.274µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:02:00Z"
    - latency: 863.741µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:01:00Z"
    - latency: 1.065118ms
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:00:00Z"
    - latency: 1.311692ms
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:59:00Z"
    - latency: 876.488µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:58:00Z"
    - latency: 885.976µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:57:00Z"
    - latency: 1.38692ms
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:56:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T04:43:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 3578907e-6a82-487a-b7c4-19156a28562e
    resourceVersion: "35068"
    uid: 7eea9f2e-e18a-4d05-b432-677b0e4365d7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rffhs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:50:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 829.847µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:02:00Z"
    - latency: 1.863441ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T05:02:00Z"
    - latency: 800.143µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:01:00Z"
    - latency: 1.693633ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T05:01:00Z"
    - latency: 925.42µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T05:00:00Z"
    - latency: 1.85919ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T05:00:00Z"
    - latency: 808.684µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:59:00Z"
    - latency: 2.466418ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:59:00Z"
    - latency: 995.318µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:58:00Z"
    - latency: 1.726579ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:58:00Z"
kind: List
metadata:
  resourceVersion: ""