apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:21:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-112-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-112.ec2.internal
      uid: 07ce1541-8a45-4afc-b8a5-7fa5d147ffdf
    resourceVersion: "25481"
    uid: d8906bd2-f1c2-4139-a537-997e23baeb59
  spec:
    sourcePod: network-check-source-989f8b8dc-j742c
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:28:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.976555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:35:44Z"
    - latency: 1.085389ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:34:44Z"
    - latency: 1.141224ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:33:44Z"
    - latency: 1.000603ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:32:44Z"
    - latency: 1.092329ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:31:44Z"
    - latency: 1.166356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:30:44Z"
    - latency: 1.136732ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:29:44Z"
    - latency: 960.929µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:28:44Z"
    - latency: 1.383986ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:27:44Z"
    - latency: 1.141192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:26:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:21:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-112-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-112.ec2.internal
      uid: 07ce1541-8a45-4afc-b8a5-7fa5d147ffdf
    resourceVersion: "24279"
    uid: 65645ffc-56af-4085-8220-f5ef1eae48bc
  spec:
    sourcePod: network-check-source-989f8b8dc-j742c
    targetEndpoint: a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:27:44Z"
      message: 'load-balancer-api-external: tcp connection to a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.19563ms
      message: 'load-balancer-api-external: tcp connection to a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:33:44Z"
    - latency: 10.507107ms
      message: 'load-balancer-api-external: resolved host name a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:33:44Z"
    - latency: 7.839177ms
      message: 'load-balancer-api-external: tcp connection to a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:32:44Z"
    - latency: 12.910359ms
      message: 'load-balancer-api-external: resolved host name a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:32:44Z"
    - latency: 5.7411ms
      message: 'load-balancer-api-external: tcp connection to a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:31:44Z"
    - latency: 14.391708ms
      message: 'load-balancer-api-external: resolved host name a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:31:44Z"
    - latency: 5.345148ms
      message: 'load-balancer-api-external: tcp connection to a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:30:44Z"
    - latency: 12.303102ms
      message: 'load-balancer-api-external: resolved host name a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:30:44Z"
    - latency: 5.530515ms
      message: 'load-balancer-api-external: tcp connection to a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:29:44Z"
    - latency: 7.810915ms
      message: 'load-balancer-api-external: resolved host name a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:29:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:21:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-112-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-112.ec2.internal
      uid: 07ce1541-8a45-4afc-b8a5-7fa5d147ffdf
    resourceVersion: "24278"
    uid: 103515d7-d2b3-4976-ad4f-95ad039f070a
  spec:
    sourcePod: network-check-source-989f8b8dc-j742c
    targetEndpoint: a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:27:44Z"
      message: 'load-balancer-api-internal: tcp connection to a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.157969ms
      message: 'load-balancer-api-internal: tcp connection to a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:33:44Z"
    - latency: 10.452923ms
      message: 'load-balancer-api-internal: resolved host name a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:33:44Z"
    - latency: 4.312002ms
      message: 'load-balancer-api-internal: tcp connection to a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:32:44Z"
    - latency: 12.934539ms
      message: 'load-balancer-api-internal: resolved host name a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:32:44Z"
    - latency: 5.743438ms
      message: 'load-balancer-api-internal: tcp connection to a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:31:44Z"
    - latency: 14.317512ms
      message: 'load-balancer-api-internal: resolved host name a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:31:44Z"
    - latency: 5.863043ms
      message: 'load-balancer-api-internal: tcp connection to a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:30:44Z"
    - latency: 12.284318ms
      message: 'load-balancer-api-internal: resolved host name a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:30:44Z"
    - latency: 5.547315ms
      message: 'load-balancer-api-internal: tcp connection to a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:29:44Z"
    - latency: 7.761449ms
      message: 'load-balancer-api-internal: resolved host name a39c84098e8434eaf8458ad9551c7703-af4249328be6f1f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:29:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:21:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-112-to-network-check-target-ip-10-0-128-176
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-112.ec2.internal
      uid: 07ce1541-8a45-4afc-b8a5-7fa5d147ffdf
    resourceVersion: "25480"
    uid: 94207389-9fb1-4d2d-805e-29cc86e11b6e
  spec:
    sourcePod: network-check-source-989f8b8dc-j742c
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:28:44Z"
      message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.379727ms
      message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:35:44Z"
    - latency: 1.910506ms
      message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:34:44Z"
    - latency: 2.204176ms
      message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:33:44Z"
    - latency: 2.392588ms
      message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:32:44Z"
    - latency: 2.376556ms
      message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:31:44Z"
    - latency: 2.026288ms
      message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:30:44Z"
    - latency: 2.430608ms
      message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:29:44Z"
    - latency: 2.334872ms
      message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:28:44Z"
    - latency: 2.273618ms
      message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:27:44Z"
    - latency: 2.310325ms
      message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:26:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:21:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-112-to-network-check-target-ip-10-0-135-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-112.ec2.internal
      uid: 07ce1541-8a45-4afc-b8a5-7fa5d147ffdf
    resourceVersion: "25479"
    uid: f9fbc902-df9a-46f8-91f4-3da781544ddd
  spec:
    sourcePod: network-check-source-989f8b8dc-j742c
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:28:44Z"
      message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.471115ms
      message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:35:44Z"
    - latency: 2.460465ms
      message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:34:44Z"
    - latency: 2.371388ms
      message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:33:44Z"
    - latency: 2.220267ms
      message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:32:44Z"
    - latency: 2.017234ms
      message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:31:44Z"
    - latency: 2.354243ms
      message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:30:44Z"
    - latency: 2.427452ms
      message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:29:44Z"
    - latency: 2.515706ms
      message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:28:44Z"
    - latency: 2.387839ms
      message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:27:44Z"
    - latency: 2.518173ms
      message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:26:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:21:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-112-to-network-check-target-ip-10-0-136-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-112.ec2.internal
      uid: 07ce1541-8a45-4afc-b8a5-7fa5d147ffdf
    resourceVersion: "25478"
    uid: 4cbcf504-f3d2-4981-8bf0-d317bf05cff6
  spec:
    sourcePod: network-check-source-989f8b8dc-j742c
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:28:44Z"
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.532965ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:35:44Z"
    - latency: 919.752µs
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:34:44Z"
    - latency: 930.015µs
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:33:44Z"
    - latency: 968.983µs
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:32:44Z"
    - latency: 1.3663ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:31:44Z"
    - latency: 965.814µs
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:30:44Z"
    - latency: 904.699µs
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:29:44Z"
    - latency: 1.084517ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:28:44Z"
    - latency: 1.002226ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:27:44Z"
    - latency: 1.067204ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:26:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:21:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-112-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-112.ec2.internal
      uid: 07ce1541-8a45-4afc-b8a5-7fa5d147ffdf
    resourceVersion: "24276"
    uid: 7a1c7f3f-a6e9-48d5-bbac-e2c0599688d4
  spec:
    sourcePod: network-check-source-989f8b8dc-j742c
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:27:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.237071ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:33:44Z"
    - latency: 1.808751ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:33:44Z"
    - latency: 829.77µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:32:44Z"
    - latency: 1.725037ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:32:44Z"
    - latency: 989.667µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:31:44Z"
    - latency: 2.06916ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:31:44Z"
    - latency: 983.632µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:30:44Z"
    - latency: 2.049084ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:30:44Z"
    - latency: 768.158µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T13:29:44Z"
    - latency: 1.77461ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T13:29:44Z"
kind: List
metadata:
  resourceVersion: ""