apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T23:37:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-39-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-39.ec2.internal
      uid: d718a986-514c-46d9-92bc-5dfa9da7ed1c
    resourceVersion: "18517"
    uid: eb4b5a17-4d63-4bb3-9b49-1f57430621e2
  spec:
    sourcePod: network-check-source-7f44b6dd87-twrrs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T23:44:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.385µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:58:47Z"
    - latency: 1.110475ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:57:47Z"
    - latency: 929.573µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:56:47Z"
    - latency: 1.036456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:55:47Z"
    - latency: 762.382µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:54:47Z"
    - latency: 1.070814ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:53:47Z"
    - latency: 908.507µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:52:47Z"
    - latency: 1.173031ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:51:47Z"
    - latency: 908.695µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:50:47Z"
    - latency: 1.188676ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:49:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T23:37:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-39-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-39.ec2.internal
      uid: d718a986-514c-46d9-92bc-5dfa9da7ed1c
    resourceVersion: "19886"
    uid: cca0dd6b-6141-406d-8626-f51c9839cde7
  spec:
    sourcePod: network-check-source-7f44b6dd87-twrrs
    targetEndpoint: a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T23:43:47Z"
      message: 'load-balancer-api-external: tcp connection to a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.963118ms
      message: 'load-balancer-api-external: tcp connection to a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T00:01:47Z"
    - latency: 9.164502ms
      message: 'load-balancer-api-external: resolved host name a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T00:01:47Z"
    - latency: 4.174209ms
      message: 'load-balancer-api-external: tcp connection to a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T00:00:47Z"
    - latency: 8.267923ms
      message: 'load-balancer-api-external: resolved host name a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T00:00:47Z"
    - latency: 4.63158ms
      message: 'load-balancer-api-external: tcp connection to a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:59:47Z"
    - latency: 7.771333ms
      message: 'load-balancer-api-external: resolved host name a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T23:59:47Z"
    - latency: 4.290221ms
      message: 'load-balancer-api-external: tcp connection to a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:58:47Z"
    - latency: 9.294646ms
      message: 'load-balancer-api-external: resolved host name a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T23:58:47Z"
    - latency: 3.820289ms
      message: 'load-balancer-api-external: tcp connection to a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:57:47Z"
    - latency: 8.391561ms
      message: 'load-balancer-api-external: resolved host name a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T23:57:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T23:37:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-39-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-39.ec2.internal
      uid: d718a986-514c-46d9-92bc-5dfa9da7ed1c
    resourceVersion: "19885"
    uid: a19307c6-0e9b-4d07-a350-aab6105499fc
  spec:
    sourcePod: network-check-source-7f44b6dd87-twrrs
    targetEndpoint: a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T23:43:47Z"
      message: 'load-balancer-api-internal: tcp connection to a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.165868ms
      message: 'load-balancer-api-internal: tcp connection to a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T00:01:47Z"
    - latency: 9.125487ms
      message: 'load-balancer-api-internal: resolved host name a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T00:01:47Z"
    - latency: 4.165439ms
      message: 'load-balancer-api-internal: tcp connection to a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T00:00:47Z"
    - latency: 8.331348ms
      message: 'load-balancer-api-internal: resolved host name a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T00:00:47Z"
    - latency: 4.46387ms
      message: 'load-balancer-api-internal: tcp connection to a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:59:47Z"
    - latency: 7.672941ms
      message: 'load-balancer-api-internal: resolved host name a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T23:59:47Z"
    - latency: 5.100887ms
      message: 'load-balancer-api-internal: tcp connection to a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:58:47Z"
    - latency: 9.272815ms
      message: 'load-balancer-api-internal: resolved host name a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T23:58:47Z"
    - latency: 3.623041ms
      message: 'load-balancer-api-internal: tcp connection to a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:57:47Z"
    - latency: 8.272936ms
      message: 'load-balancer-api-internal: resolved host name a8619d86fa347472295685fb16022521-68129f47981e83d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T23:57:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T23:37:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-39-to-network-check-target-ip-10-0-130-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-39.ec2.internal
      uid: d718a986-514c-46d9-92bc-5dfa9da7ed1c
    resourceVersion: "18516"
    uid: 810cad6f-9f1e-4740-92fb-e3a134ee120f
  spec:
    sourcePod: network-check-source-7f44b6dd87-twrrs
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T23:44:47Z"
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.873607ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:58:47Z"
    - latency: 1.895251ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:57:47Z"
    - latency: 2.092481ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:56:47Z"
    - latency: 2.063202ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:55:47Z"
    - latency: 2.282403ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:54:47Z"
    - latency: 2.193329ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:53:47Z"
    - latency: 2.285557ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:52:47Z"
    - latency: 2.081966ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:51:47Z"
    - latency: 2.222672ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:50:47Z"
    - latency: 2.234085ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:49:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T23:37:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-39-to-network-check-target-ip-10-0-134-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-39.ec2.internal
      uid: d718a986-514c-46d9-92bc-5dfa9da7ed1c
    resourceVersion: "18515"
    uid: 0414d433-be9a-48d6-867b-5954cd148491
  spec:
    sourcePod: network-check-source-7f44b6dd87-twrrs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T23:44:47Z"
      message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.239011ms
      message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:58:47Z"
    - latency: 1.522426ms
      message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:57:47Z"
    - latency: 1.796083ms
      message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:56:47Z"
    - latency: 1.817338ms
      message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:55:47Z"
    - latency: 2.158418ms
      message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:54:47Z"
    - latency: 2.124829ms
      message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:53:47Z"
    - latency: 2.230338ms
      message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:52:47Z"
    - latency: 1.705588ms
      message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:51:47Z"
    - latency: 1.720877ms
      message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:50:47Z"
    - latency: 1.658929ms
      message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:49:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T23:37:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-39-to-network-check-target-ip-10-0-138-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-39.ec2.internal
      uid: d718a986-514c-46d9-92bc-5dfa9da7ed1c
    resourceVersion: "18514"
    uid: f2e6eba1-1f81-4824-9c46-a065cfa8dfee
  spec:
    sourcePod: network-check-source-7f44b6dd87-twrrs
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T23:44:47Z"
      message: 'network-check-target-ip-10-0-138-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 813.187µs
      message: 'network-check-target-ip-10-0-138-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:58:47Z"
    - latency: 772.545µs
      message: 'network-check-target-ip-10-0-138-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:57:47Z"
    - latency: 742.943µs
      message: 'network-check-target-ip-10-0-138-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:56:47Z"
    - latency: 1.210165ms
      message: 'network-check-target-ip-10-0-138-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:55:47Z"
    - latency: 765.357µs
      message: 'network-check-target-ip-10-0-138-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:54:47Z"
    - latency: 874.239µs
      message: 'network-check-target-ip-10-0-138-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:53:47Z"
    - latency: 765.088µs
      message: 'network-check-target-ip-10-0-138-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:52:47Z"
    - latency: 800.943µs
      message: 'network-check-target-ip-10-0-138-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:51:47Z"
    - latency: 1.262123ms
      message: 'network-check-target-ip-10-0-138-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:50:47Z"
    - latency: 785.655µs
      message: 'network-check-target-ip-10-0-138-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:49:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T23:37:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-39-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-39.ec2.internal
      uid: d718a986-514c-46d9-92bc-5dfa9da7ed1c
    resourceVersion: "19884"
    uid: bd126111-e782-4437-9424-271cb5345e52
  spec:
    sourcePod: network-check-source-7f44b6dd87-twrrs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T23:43:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.116061ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T00:01:47Z"
    - latency: 1.679036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T00:01:47Z"
    - latency: 918.457µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T00:00:47Z"
    - latency: 1.775541ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T00:00:47Z"
    - latency: 972.775µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:59:47Z"
    - latency: 1.572545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T23:59:47Z"
    - latency: 822.689µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:58:47Z"
    - latency: 1.56472ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T23:58:47Z"
    - latency: 1.178123ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T23:57:47Z"
    - latency: 1.662253ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T23:57:47Z"
kind: List
metadata:
  resourceVersion: ""