apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-253-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-253.ec2.internal
      uid: 5e46e407-aae8-40b8-9c99-36cbf9e1c896
    resourceVersion: "63006"
    uid: fdbf3eb7-dc74-4c07-8fc3-3b22b9928d87
  spec:
    sourcePod: network-check-source-685456655f-lm8pr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:38:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.28631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:06:06Z"
    - latency: 1.35156ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:05:06Z"
    - latency: 1.04836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:04:06Z"
    - latency: 1.232439ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:03:06Z"
    - latency: 1.163099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:02:06Z"
    - latency: 1.278301ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:01:06Z"
    - latency: 1.065356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:00:06Z"
    - latency: 1.026443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:59:06Z"
    - latency: 1.216897ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:58:06Z"
    - latency: 1.142327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:57:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-253-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-253.ec2.internal
      uid: 5e46e407-aae8-40b8-9c99-36cbf9e1c896
    resourceVersion: "63783"
    uid: 8d1b014b-8759-445f-9b37-4ad249b181f9
  spec:
    sourcePod: network-check-source-685456655f-lm8pr
    targetEndpoint: ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:37:06Z"
      message: 'load-balancer-api-external: tcp connection to ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.786916ms
      message: 'load-balancer-api-external: tcp connection to ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:07:06Z"
    - latency: 8.763054ms
      message: 'load-balancer-api-external: resolved host name ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:07:06Z"
    - latency: 3.953841ms
      message: 'load-balancer-api-external: tcp connection to ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:06:06Z"
    - latency: 8.683979ms
      message: 'load-balancer-api-external: resolved host name ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:06:06Z"
    - latency: 3.723898ms
      message: 'load-balancer-api-external: tcp connection to ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:05:06Z"
    - latency: 9.04822ms
      message: 'load-balancer-api-external: resolved host name ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:05:06Z"
    - latency: 5.427642ms
      message: 'load-balancer-api-external: tcp connection to ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:04:06Z"
    - latency: 8.307246ms
      message: 'load-balancer-api-external: resolved host name ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:04:06Z"
    - latency: 4.680264ms
      message: 'load-balancer-api-external: tcp connection to ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:03:06Z"
    - latency: 8.918441ms
      message: 'load-balancer-api-external: resolved host name ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:03:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-253-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-253.ec2.internal
      uid: 5e46e407-aae8-40b8-9c99-36cbf9e1c896
    resourceVersion: "63782"
    uid: 3398a880-4e8f-4f09-8e3e-af2e0f7ac611
  spec:
    sourcePod: network-check-source-685456655f-lm8pr
    targetEndpoint: ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:37:06Z"
      message: 'load-balancer-api-internal: tcp connection to ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.037139ms
      message: 'load-balancer-api-internal: tcp connection to ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:07:06Z"
    - latency: 8.723624ms
      message: 'load-balancer-api-internal: resolved host name ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:07:06Z"
    - latency: 3.999291ms
      message: 'load-balancer-api-internal: tcp connection to ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:06:06Z"
    - latency: 8.631157ms
      message: 'load-balancer-api-internal: resolved host name ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:06:06Z"
    - latency: 3.736335ms
      message: 'load-balancer-api-internal: tcp connection to ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:05:06Z"
    - latency: 9.178904ms
      message: 'load-balancer-api-internal: resolved host name ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:05:06Z"
    - latency: 5.402463ms
      message: 'load-balancer-api-internal: tcp connection to ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:04:06Z"
    - latency: 8.227819ms
      message: 'load-balancer-api-internal: resolved host name ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:04:06Z"
    - latency: 5.49022ms
      message: 'load-balancer-api-internal: tcp connection to ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:03:06Z"
    - latency: 8.89006ms
      message: 'load-balancer-api-internal: resolved host name ac98c1ffcb7ce44b0919176460062de8-a2d2dcf15b13ca4f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:03:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-253-to-network-check-target-ip-10-0-129-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-253.ec2.internal
      uid: 5e46e407-aae8-40b8-9c99-36cbf9e1c896
    resourceVersion: "66287"
    uid: 28f39b6d-df52-46c4-bf94-740e36d3366b
  spec:
    sourcePod: network-check-source-685456655f-lm8pr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:02:55Z"
      message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.52121ms
      message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:09:55Z"
    - latency: 2.325981ms
      message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:08:55Z"
    - latency: 2.446942ms
      message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:07:55Z"
    - latency: 2.496822ms
      message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:06:55Z"
    - latency: 1.929666ms
      message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:05:55Z"
    - latency: 2.008001ms
      message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:04:55Z"
    - latency: 2.323189ms
      message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:03:55Z"
    - latency: 2.531322ms
      message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:02:55Z"
    - latency: 2.48837ms
      message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:01:55Z"
    - latency: 2.44803ms
      message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:00:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-253-to-network-check-target-ip-10-0-132-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-253.ec2.internal
      uid: 5e46e407-aae8-40b8-9c99-36cbf9e1c896
    resourceVersion: "63004"
    uid: 55667218-b47c-42e2-8965-3c6b1d00eeb2
  spec:
    sourcePod: network-check-source-685456655f-lm8pr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:38:06Z"
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.663µs
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:06:06Z"
    - latency: 1.337063ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:05:06Z"
    - latency: 1.286531ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:04:06Z"
    - latency: 916.815µs
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:03:06Z"
    - latency: 1.080798ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:02:06Z"
    - latency: 944.754µs
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:01:06Z"
    - latency: 1.404805ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:00:06Z"
    - latency: 993.134µs
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:59:06Z"
    - latency: 1.303622ms
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:58:06Z"
    - latency: 839.741µs
      message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:57:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-253-to-network-check-target-ip-10-0-137-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-253.ec2.internal
      uid: 5e46e407-aae8-40b8-9c99-36cbf9e1c896
    resourceVersion: "63005"
    uid: e187617d-deba-419c-a911-a09c15f71085
  spec:
    sourcePod: network-check-source-685456655f-lm8pr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:38:06Z"
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.244536ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:06:06Z"
    - latency: 2.543567ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:05:06Z"
    - latency: 2.464448ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:04:06Z"
    - latency: 2.499101ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:03:06Z"
    - latency: 2.415046ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:02:06Z"
    - latency: 2.260134ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:01:06Z"
    - latency: 2.540717ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:00:06Z"
    - latency: 2.673434ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:59:06Z"
    - latency: 2.533803ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:58:06Z"
    - latency: 2.808867ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:57:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-253-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-253.ec2.internal
      uid: 5e46e407-aae8-40b8-9c99-36cbf9e1c896
    resourceVersion: "63781"
    uid: 43d0f0cc-12ea-4310-bc58-c7b864dfc2e5
  spec:
    sourcePod: network-check-source-685456655f-lm8pr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:37:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.973µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:07:06Z"
    - latency: 1.894873ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:07:06Z"
    - latency: 1.026357ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:06:06Z"
    - latency: 2.020039ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:06:06Z"
    - latency: 894.307µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:05:06Z"
    - latency: 1.997158ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:05:06Z"
    - latency: 860.616µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:04:06Z"
    - latency: 1.699206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:04:06Z"
    - latency: 796.263µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:03:06Z"
    - latency: 2.448029ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:03:06Z"
kind: List
metadata:
  resourceVersion: ""