apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T10:54:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-116-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-116.ec2.internal
      uid: 1bcabe9a-ee85-41fb-90cf-8f1d45b8076b
    resourceVersion: "19117"
    uid: 993022bd-d006-44b6-985d-9939b9ee998d
  spec:
    sourcePod: network-check-source-7f44b6dd87-29m6h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T11:01:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 956.231µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:15:09Z"
    - latency: 930.393µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:14:09Z"
    - latency: 1.067477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:13:09Z"
    - latency: 930.599µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:12:09Z"
    - latency: 925.179µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:11:09Z"
    - latency: 934.679µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:10:09Z"
    - latency: 1.02305ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:09:09Z"
    - latency: 1.120849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:08:09Z"
    - latency: 959.182µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:07:09Z"
    - latency: 993.532µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:06:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T10:54:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-116-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-116.ec2.internal
      uid: 1bcabe9a-ee85-41fb-90cf-8f1d45b8076b
    resourceVersion: "20285"
    uid: d1f37243-eb37-4716-bd38-8ad9a275cf18
  spec:
    sourcePod: network-check-source-7f44b6dd87-29m6h
    targetEndpoint: a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T11:00:09Z"
      message: 'load-balancer-api-external: tcp connection to a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.879562ms
      message: 'load-balancer-api-external: tcp connection to a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:18:09Z"
    - latency: 7.295717ms
      message: 'load-balancer-api-external: resolved host name a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:18:09Z"
    - latency: 12.717542ms
      message: 'load-balancer-api-external: tcp connection to a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:17:09Z"
    - latency: 7.530065ms
      message: 'load-balancer-api-external: resolved host name a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:17:09Z"
    - latency: 3.618148ms
      message: 'load-balancer-api-external: tcp connection to a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:16:09Z"
    - latency: 7.760492ms
      message: 'load-balancer-api-external: resolved host name a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:16:09Z"
    - latency: 4.073063ms
      message: 'load-balancer-api-external: tcp connection to a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:15:09Z"
    - latency: 8.589155ms
      message: 'load-balancer-api-external: resolved host name a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:15:09Z"
    - latency: 4.501013ms
      message: 'load-balancer-api-external: tcp connection to a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:14:09Z"
    - latency: 7.801496ms
      message: 'load-balancer-api-external: resolved host name a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:14:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T10:54:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-116-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-116.ec2.internal
      uid: 1bcabe9a-ee85-41fb-90cf-8f1d45b8076b
    resourceVersion: "20286"
    uid: ff5acb53-a982-4e62-a80b-53511626fef0
  spec:
    sourcePod: network-check-source-7f44b6dd87-29m6h
    targetEndpoint: a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T11:00:09Z"
      message: 'load-balancer-api-internal: tcp connection to a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.890028ms
      message: 'load-balancer-api-internal: tcp connection to a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:18:09Z"
    - latency: 7.25876ms
      message: 'load-balancer-api-internal: resolved host name a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:18:09Z"
    - latency: 6.18104ms
      message: 'load-balancer-api-internal: tcp connection to a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:17:09Z"
    - latency: 7.600803ms
      message: 'load-balancer-api-internal: resolved host name a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:17:09Z"
    - latency: 4.016502ms
      message: 'load-balancer-api-internal: tcp connection to a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:16:09Z"
    - latency: 7.827717ms
      message: 'load-balancer-api-internal: resolved host name a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:16:09Z"
    - latency: 3.996953ms
      message: 'load-balancer-api-internal: tcp connection to a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:15:09Z"
    - latency: 8.71261ms
      message: 'load-balancer-api-internal: resolved host name a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:15:09Z"
    - latency: 5.762648ms
      message: 'load-balancer-api-internal: tcp connection to a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:14:09Z"
    - latency: 7.822599ms
      message: 'load-balancer-api-internal: resolved host name a79361c84a05f4161ab9760e06bc8d5e-df806c2f4881be77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:14:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T10:54:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-116-to-network-check-target-ip-10-0-131-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-116.ec2.internal
      uid: 1bcabe9a-ee85-41fb-90cf-8f1d45b8076b
    resourceVersion: "19114"
    uid: 6d62bdda-11b1-48a1-a757-4d1c114ad5d8
  spec:
    sourcePod: network-check-source-7f44b6dd87-29m6h
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T11:01:09Z"
      message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.098457ms
      message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:15:09Z"
    - latency: 2.077065ms
      message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:14:09Z"
    - latency: 2.495036ms
      message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:13:09Z"
    - latency: 2.331023ms
      message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:12:09Z"
    - latency: 2.126354ms
      message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:11:09Z"
    - latency: 2.31377ms
      message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:10:09Z"
    - latency: 2.097753ms
      message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:09:09Z"
    - latency: 2.055948ms
      message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:08:09Z"
    - latency: 2.471189ms
      message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:07:09Z"
    - latency: 2.226239ms
      message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:06:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T10:54:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-116-to-network-check-target-ip-10-0-139-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-116.ec2.internal
      uid: 1bcabe9a-ee85-41fb-90cf-8f1d45b8076b
    resourceVersion: "19116"
    uid: 697ccb45-2bfc-4b74-bee1-ddf9d95958c3
  spec:
    sourcePod: network-check-source-7f44b6dd87-29m6h
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T11:01:09Z"
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.559524ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:15:09Z"
    - latency: 1.167479ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:14:09Z"
    - latency: 809.413µs
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:13:09Z"
    - latency: 954.541µs
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:12:09Z"
    - latency: 944.356µs
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:11:09Z"
    - latency: 845.542µs
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:10:09Z"
    - latency: 1.001913ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:09:09Z"
    - latency: 1.325255ms
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:08:09Z"
    - latency: 947.726µs
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:07:09Z"
    - latency: 958.307µs
      message: 'network-check-target-ip-10-0-139-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:06:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T10:54:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-116-to-network-check-target-ip-10-0-142-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-116.ec2.internal
      uid: 1bcabe9a-ee85-41fb-90cf-8f1d45b8076b
    resourceVersion: "19115"
    uid: 3564d23d-d544-4e08-9e33-e4e110690797
  spec:
    sourcePod: network-check-source-7f44b6dd87-29m6h
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T11:01:09Z"
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.307919ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:15:09Z"
    - latency: 2.027225ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:14:09Z"
    - latency: 2.044749ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:13:09Z"
    - latency: 2.33236ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:12:09Z"
    - latency: 2.138763ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:11:09Z"
    - latency: 2.255394ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:10:09Z"
    - latency: 2.073172ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:09:09Z"
    - latency: 2.006287ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:08:09Z"
    - latency: 2.027066ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:07:09Z"
    - latency: 2.219794ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:06:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T10:54:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-116-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-116.ec2.internal
      uid: 1bcabe9a-ee85-41fb-90cf-8f1d45b8076b
    resourceVersion: "20284"
    uid: 4cfeeb5f-bcf8-47fb-88dd-573a7fcd898d
  spec:
    sourcePod: network-check-source-7f44b6dd87-29m6h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T11:00:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 802.797µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:18:09Z"
    - latency: 1.47349ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:18:09Z"
    - latency: 710.092µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:17:09Z"
    - latency: 1.706827ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:17:09Z"
    - latency: 1.187852ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:16:09Z"
    - latency: 1.489278ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:16:09Z"
    - latency: 1.10512ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:15:09Z"
    - latency: 1.888178ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:15:09Z"
    - latency: 887.845µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T11:14:09Z"
    - latency: 1.755672ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T11:14:09Z"
kind: List
metadata:
  resourceVersion: ""