apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.ec2.internal
      uid: 068effb0-0cb5-4473-a48a-386f9fa73956
    resourceVersion: "29520"
    uid: d512621f-68f7-4813-b2e8-0826c9730522
  spec:
    sourcePod: network-check-source-6947749cfc-mdfnf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:07:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.150282ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:14:49Z"
    - latency: 834.87µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:13:49Z"
    - latency: 1.423365ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:12:49Z"
    - latency: 1.020339ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:11:49Z"
    - latency: 973.971µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:10:49Z"
    - latency: 1.130487ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:09:49Z"
    - latency: 962.453µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:08:49Z"
    - latency: 1.021274ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:07:49Z"
    - latency: 1.127647ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:06:49Z"
    - latency: 1.210486ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:05:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.ec2.internal
      uid: 068effb0-0cb5-4473-a48a-386f9fa73956
    resourceVersion: "28255"
    uid: cecc2e5b-9aea-4337-87ec-fb926c16ed87
  spec:
    sourcePod: network-check-source-6947749cfc-mdfnf
    targetEndpoint: acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:06:49Z"
      message: 'load-balancer-api-external: tcp connection to acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.980453ms
      message: 'load-balancer-api-external: tcp connection to acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:12:49Z"
    - latency: 7.263345ms
      message: 'load-balancer-api-external: resolved host name acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:12:49Z"
    - latency: 4.994733ms
      message: 'load-balancer-api-external: tcp connection to acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:11:49Z"
    - latency: 6.942796ms
      message: 'load-balancer-api-external: resolved host name acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:11:49Z"
    - latency: 5.577422ms
      message: 'load-balancer-api-external: tcp connection to acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:10:49Z"
    - latency: 9.48698ms
      message: 'load-balancer-api-external: resolved host name acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:10:49Z"
    - latency: 5.286881ms
      message: 'load-balancer-api-external: tcp connection to acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:09:49Z"
    - latency: 7.592949ms
      message: 'load-balancer-api-external: resolved host name acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:09:49Z"
    - latency: 5.557963ms
      message: 'load-balancer-api-external: tcp connection to acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:08:49Z"
    - latency: 7.365984ms
      message: 'load-balancer-api-external: resolved host name acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:08:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.ec2.internal
      uid: 068effb0-0cb5-4473-a48a-386f9fa73956
    resourceVersion: "28256"
    uid: fe4bbbbb-8bb8-47a5-ac77-51291d194519
  spec:
    sourcePod: network-check-source-6947749cfc-mdfnf
    targetEndpoint: acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:06:49Z"
      message: 'load-balancer-api-internal: tcp connection to acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.94886ms
      message: 'load-balancer-api-internal: tcp connection to acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:12:49Z"
    - latency: 7.351258ms
      message: 'load-balancer-api-internal: resolved host name acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:12:49Z"
    - latency: 4.951097ms
      message: 'load-balancer-api-internal: tcp connection to acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:11:49Z"
    - latency: 6.967884ms
      message: 'load-balancer-api-internal: resolved host name acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:11:49Z"
    - latency: 5.53087ms
      message: 'load-balancer-api-internal: tcp connection to acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:10:49Z"
    - latency: 9.602516ms
      message: 'load-balancer-api-internal: resolved host name acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:10:49Z"
    - latency: 5.320799ms
      message: 'load-balancer-api-internal: tcp connection to acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:09:49Z"
    - latency: 7.569663ms
      message: 'load-balancer-api-internal: resolved host name acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:09:49Z"
    - latency: 5.590693ms
      message: 'load-balancer-api-internal: tcp connection to acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:08:49Z"
    - latency: 7.394689ms
      message: 'load-balancer-api-internal: resolved host name acee54a735bf94452a5b21f7c7b670ed-e4c001e50337ba36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:08:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-network-check-target-ip-10-0-131-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.ec2.internal
      uid: 068effb0-0cb5-4473-a48a-386f9fa73956
    resourceVersion: "29517"
    uid: f89fb02e-2b51-49b1-bba1-8ab48526bab1
  spec:
    sourcePod: network-check-source-6947749cfc-mdfnf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:07:49Z"
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.32421ms
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:14:49Z"
    - latency: 1.081189ms
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:13:49Z"
    - latency: 840.629µs
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:12:49Z"
    - latency: 1.206884ms
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:11:49Z"
    - latency: 959.06µs
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:10:49Z"
    - latency: 1.064133ms
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:09:49Z"
    - latency: 970.103µs
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:08:49Z"
    - latency: 921.774µs
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:07:49Z"
    - latency: 1.267801ms
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:06:49Z"
    - latency: 1.042503ms
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:05:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-network-check-target-ip-10-0-139-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.ec2.internal
      uid: 068effb0-0cb5-4473-a48a-386f9fa73956
    resourceVersion: "29518"
    uid: 7d97f697-2656-4bd8-8443-4f326a330ee1
  spec:
    sourcePod: network-check-source-6947749cfc-mdfnf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:07:49Z"
      message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.846209ms
      message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:14:49Z"
    - latency: 1.861003ms
      message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:13:49Z"
    - latency: 1.955503ms
      message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:12:49Z"
    - latency: 2.126016ms
      message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:11:49Z"
    - latency: 2.036826ms
      message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:10:49Z"
    - latency: 1.685669ms
      message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:09:49Z"
    - latency: 1.892019ms
      message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:08:49Z"
    - latency: 2.101479ms
      message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:07:49Z"
    - latency: 1.854025ms
      message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:06:49Z"
    - latency: 1.762569ms
      message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:05:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-network-check-target-ip-10-0-141-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.ec2.internal
      uid: 068effb0-0cb5-4473-a48a-386f9fa73956
    resourceVersion: "29519"
    uid: 2b0c9243-6109-47e3-a494-5ed565efa15f
  spec:
    sourcePod: network-check-source-6947749cfc-mdfnf
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:07:49Z"
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.376045ms
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:14:49Z"
    - latency: 2.325147ms
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:13:49Z"
    - latency: 2.15795ms
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:12:49Z"
    - latency: 2.264017ms
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:11:49Z"
    - latency: 2.191598ms
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:10:49Z"
    - latency: 2.279131ms
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:09:49Z"
    - latency: 2.31957ms
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:08:49Z"
    - latency: 2.442864ms
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:07:49Z"
    - latency: 2.226274ms
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:06:49Z"
    - latency: 2.404342ms
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:05:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.ec2.internal
      uid: 068effb0-0cb5-4473-a48a-386f9fa73956
    resourceVersion: "28254"
    uid: 476b4039-ca08-4aa0-b6ed-d42cea87e651
  spec:
    sourcePod: network-check-source-6947749cfc-mdfnf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:06:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 951.287µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:12:49Z"
    - latency: 2.020796ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:12:49Z"
    - latency: 967.944µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:11:49Z"
    - latency: 1.703594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:11:49Z"
    - latency: 910.174µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:10:49Z"
    - latency: 1.642608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:10:49Z"
    - latency: 824.691µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:09:49Z"
    - latency: 2.165496ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:09:49Z"
    - latency: 987.396µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:08:49Z"
    - latency: 2.001011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:08:49Z"
kind: List
metadata:
  resourceVersion: ""