apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T18:54:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-23-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-23.ec2.internal
      uid: 8428da90-6dce-4b3d-b155-fa7f9365a4ab
    resourceVersion: "61640"
    uid: 5ce53205-fb0d-4b05-b749-26627c5abdd4
  spec:
    sourcePod: network-check-source-869dcfcdcd-sntfz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:01:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.481922ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:36:14Z"
    - latency: 1.051775ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:35:14Z"
    - latency: 898.774µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:34:14Z"
    - latency: 1.215207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:33:14Z"
    - latency: 911.78µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:32:14Z"
    - latency: 1.211802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:31:14Z"
    - latency: 1.681039ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:30:14Z"
    - latency: 1.020802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:29:14Z"
    - latency: 1.173275ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:28:14Z"
    - latency: 1.193315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:27:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T18:54:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-23-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-23.ec2.internal
      uid: 8428da90-6dce-4b3d-b155-fa7f9365a4ab
    resourceVersion: "61643"
    uid: fd080cd3-a242-4518-b724-d822ee7f547f
  spec:
    sourcePod: network-check-source-869dcfcdcd-sntfz
    targetEndpoint: a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:00:14Z"
      message: 'load-balancer-api-external: tcp connection to a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.978765ms
      message: 'load-balancer-api-external: tcp connection to a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:36:14Z"
    - latency: 7.295593ms
      message: 'load-balancer-api-external: resolved host name a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:36:14Z"
    - latency: 6.063621ms
      message: 'load-balancer-api-external: tcp connection to a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:35:14Z"
    - latency: 10.540301ms
      message: 'load-balancer-api-external: resolved host name a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:35:14Z"
    - latency: 4.641002ms
      message: 'load-balancer-api-external: tcp connection to a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:34:14Z"
    - latency: 9.392508ms
      message: 'load-balancer-api-external: resolved host name a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:34:14Z"
    - latency: 3.363002ms
      message: 'load-balancer-api-external: tcp connection to a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:33:14Z"
    - latency: 6.450039ms
      message: 'load-balancer-api-external: resolved host name a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:33:14Z"
    - latency: 4.487918ms
      message: 'load-balancer-api-external: tcp connection to a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:32:14Z"
    - latency: 7.766438ms
      message: 'load-balancer-api-external: resolved host name a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:32:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T18:54:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-23-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-23.ec2.internal
      uid: 8428da90-6dce-4b3d-b155-fa7f9365a4ab
    resourceVersion: "61642"
    uid: 4617430b-17a2-4ecd-af87-d42277f344dd
  spec:
    sourcePod: network-check-source-869dcfcdcd-sntfz
    targetEndpoint: a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:00:14Z"
      message: 'load-balancer-api-internal: tcp connection to a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.605031ms
      message: 'load-balancer-api-internal: tcp connection to a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:36:14Z"
    - latency: 7.334349ms
      message: 'load-balancer-api-internal: resolved host name a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:36:14Z"
    - latency: 4.017226ms
      message: 'load-balancer-api-internal: tcp connection to a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:35:14Z"
    - latency: 10.651155ms
      message: 'load-balancer-api-internal: resolved host name a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:35:14Z"
    - latency: 4.652652ms
      message: 'load-balancer-api-internal: tcp connection to a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:34:14Z"
    - latency: 9.454299ms
      message: 'load-balancer-api-internal: resolved host name a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:34:14Z"
    - latency: 3.733042ms
      message: 'load-balancer-api-internal: tcp connection to a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:33:14Z"
    - latency: 6.518281ms
      message: 'load-balancer-api-internal: resolved host name a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:33:14Z"
    - latency: 3.931186ms
      message: 'load-balancer-api-internal: tcp connection to a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:32:14Z"
    - latency: 7.8159ms
      message: 'load-balancer-api-internal: resolved host name a6980ca8f52484502a39d7403e9725f7-f9a970c62e1ad9eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:32:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T18:54:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-23-to-network-check-target-ip-10-0-130-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-23.ec2.internal
      uid: 8428da90-6dce-4b3d-b155-fa7f9365a4ab
    resourceVersion: "61638"
    uid: e0e18a85-b2fb-45ec-852b-bef7a0ed507c
  spec:
    sourcePod: network-check-source-869dcfcdcd-sntfz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:01:14Z"
      message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.304579ms
      message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:36:14Z"
    - latency: 2.590311ms
      message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:35:14Z"
    - latency: 2.331321ms
      message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:34:14Z"
    - latency: 2.447014ms
      message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:33:14Z"
    - latency: 2.448971ms
      message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:32:14Z"
    - latency: 2.582188ms
      message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:31:14Z"
    - latency: 2.672691ms
      message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:30:14Z"
    - latency: 2.275605ms
      message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:29:14Z"
    - latency: 2.557374ms
      message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:28:14Z"
    - latency: 2.62585ms
      message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:27:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T18:54:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-23-to-network-check-target-ip-10-0-133-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-23.ec2.internal
      uid: 8428da90-6dce-4b3d-b155-fa7f9365a4ab
    resourceVersion: "61636"
    uid: c935e3f1-68f3-4384-bf94-1a9d86765b93
  spec:
    sourcePod: network-check-source-869dcfcdcd-sntfz
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:01:14Z"
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 960.19µs
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:36:14Z"
    - latency: 1.448126ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:35:14Z"
    - latency: 1.613843ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:34:14Z"
    - latency: 1.066053ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:33:14Z"
    - latency: 1.175205ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:32:14Z"
    - latency: 1.929246ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:31:14Z"
    - latency: 1.485997ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:30:14Z"
    - latency: 858.408µs
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:29:14Z"
    - latency: 1.091853ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:28:14Z"
    - latency: 1.532567ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:27:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T18:54:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-23-to-network-check-target-ip-10-0-137-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-23.ec2.internal
      uid: 8428da90-6dce-4b3d-b155-fa7f9365a4ab
    resourceVersion: "61637"
    uid: ded05fcd-0eff-4639-b846-83e8c2888355
  spec:
    sourcePod: network-check-source-869dcfcdcd-sntfz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:01:14Z"
      message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.114963ms
      message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:36:14Z"
    - latency: 2.784759ms
      message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:35:14Z"
    - latency: 2.362656ms
      message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:34:14Z"
    - latency: 2.737401ms
      message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:33:14Z"
    - latency: 2.329317ms
      message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:32:14Z"
    - latency: 2.647336ms
      message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:31:14Z"
    - latency: 2.482023ms
      message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:30:14Z"
    - latency: 2.682434ms
      message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:29:14Z"
    - latency: 2.338712ms
      message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:28:14Z"
    - latency: 3.028908ms
      message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:27:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T18:54:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-23-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-23.ec2.internal
      uid: 8428da90-6dce-4b3d-b155-fa7f9365a4ab
    resourceVersion: "61639"
    uid: cb8bab5a-38c6-4731-b62e-d67528242329
  spec:
    sourcePod: network-check-source-869dcfcdcd-sntfz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:00:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.255929ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:36:14Z"
    - latency: 1.94124ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:36:14Z"
    - latency: 848.136µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:35:14Z"
    - latency: 1.899192ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:35:14Z"
    - latency: 1.028288ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:34:14Z"
    - latency: 1.891584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:34:14Z"
    - latency: 1.144948ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:33:14Z"
    - latency: 1.921356ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:33:14Z"
    - latency: 1.321905ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:32:14Z"
    - latency: 1.988621ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:32:14Z"
kind: List
metadata:
  resourceVersion: ""