apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T08:38:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-115-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-115.ec2.internal
      uid: 99281272-5ad7-4e80-a41f-11b5bf0f7e23
    resourceVersion: "17684"
    uid: 09b4d72f-8625-4c61-a70c-ad8930897426
  spec:
    sourcePod: network-check-source-7b678d77c7-nzw48
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T08:45:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.50585ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:13:02Z"
    - latency: 1.435187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:12:02Z"
    - latency: 1.664176ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:11:02Z"
    - latency: 1.244724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:10:02Z"
    - latency: 803.343µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:09:02Z"
    - latency: 923.772µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:08:02Z"
    - latency: 819.945µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:07:02Z"
    - latency: 1.351555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:06:02Z"
    - latency: 948.779µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:05:02Z"
    - latency: 761.648µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:04:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T08:38:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-115-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-115.ec2.internal
      uid: 99281272-5ad7-4e80-a41f-11b5bf0f7e23
    resourceVersion: "16700"
    uid: 9cab3a46-e004-4799-96db-f6f781848f1a
  spec:
    sourcePod: network-check-source-7b678d77c7-nzw48
    targetEndpoint: a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T08:44:02Z"
      message: 'load-balancer-api-external: tcp connection to a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.912158ms
      message: 'load-balancer-api-external: tcp connection to a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:08:02Z"
    - latency: 7.25803ms
      message: 'load-balancer-api-external: resolved host name a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:08:02Z"
    - latency: 4.350829ms
      message: 'load-balancer-api-external: tcp connection to a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:07:02Z"
    - latency: 8.846065ms
      message: 'load-balancer-api-external: resolved host name a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:07:02Z"
    - latency: 4.510167ms
      message: 'load-balancer-api-external: tcp connection to a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:06:02Z"
    - latency: 8.597032ms
      message: 'load-balancer-api-external: resolved host name a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:06:02Z"
    - latency: 3.658486ms
      message: 'load-balancer-api-external: tcp connection to a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:05:02Z"
    - latency: 9.24709ms
      message: 'load-balancer-api-external: resolved host name a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:05:02Z"
    - latency: 5.121198ms
      message: 'load-balancer-api-external: tcp connection to a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:04:02Z"
    - latency: 9.62376ms
      message: 'load-balancer-api-external: resolved host name a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:04:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T08:38:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-115-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-115.ec2.internal
      uid: 99281272-5ad7-4e80-a41f-11b5bf0f7e23
    resourceVersion: "16701"
    uid: 4f3bd220-a052-4850-8d57-8b94a6ad7dcc
  spec:
    sourcePod: network-check-source-7b678d77c7-nzw48
    targetEndpoint: a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T08:44:02Z"
      message: 'load-balancer-api-internal: tcp connection to a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.322394ms
      message: 'load-balancer-api-internal: tcp connection to a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:08:02Z"
    - latency: 7.204622ms
      message: 'load-balancer-api-internal: resolved host name a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:08:02Z"
    - latency: 4.319958ms
      message: 'load-balancer-api-internal: tcp connection to a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:07:02Z"
    - latency: 8.910758ms
      message: 'load-balancer-api-internal: resolved host name a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:07:02Z"
    - latency: 5.972518ms
      message: 'load-balancer-api-internal: tcp connection to a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:06:02Z"
    - latency: 8.690598ms
      message: 'load-balancer-api-internal: resolved host name a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:06:02Z"
    - latency: 4.235778ms
      message: 'load-balancer-api-internal: tcp connection to a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:05:02Z"
    - latency: 9.155546ms
      message: 'load-balancer-api-internal: resolved host name a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:05:02Z"
    - latency: 5.115603ms
      message: 'load-balancer-api-internal: tcp connection to a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:04:02Z"
    - latency: 9.571647ms
      message: 'load-balancer-api-internal: resolved host name a1d21a5bcd9c440b0b761f2544bde852-4535e5574b51748b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:04:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T08:38:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-115-to-network-check-target-ip-10-0-128-115
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-115.ec2.internal
      uid: 99281272-5ad7-4e80-a41f-11b5bf0f7e23
    resourceVersion: "17681"
    uid: 7c101b12-38d8-4ed8-8810-27b6eb6ee66f
  spec:
    sourcePod: network-check-source-7b678d77c7-nzw48
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T08:45:02Z"
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.279004ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:13:02Z"
    - latency: 1.007832ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:12:02Z"
    - latency: 1.990363ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:11:02Z"
    - latency: 662.97µs
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:10:02Z"
    - latency: 1.155857ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:09:02Z"
    - latency: 1.166516ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:08:02Z"
    - latency: 975.643µs
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:07:02Z"
    - latency: 966.253µs
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:06:02Z"
    - latency: 1.658175ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:05:02Z"
    - latency: 1.925193ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:04:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T08:38:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-115-to-network-check-target-ip-10-0-130-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-115.ec2.internal
      uid: 99281272-5ad7-4e80-a41f-11b5bf0f7e23
    resourceVersion: "17682"
    uid: 7107a286-fd7f-41da-9fc4-0e3dc5fdd3bc
  spec:
    sourcePod: network-check-source-7b678d77c7-nzw48
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T08:45:02Z"
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.083913ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:13:02Z"
    - latency: 2.127516ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:12:02Z"
    - latency: 2.076842ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:11:02Z"
    - latency: 2.050719ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:10:02Z"
    - latency: 1.952987ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:09:02Z"
    - latency: 1.822064ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:08:02Z"
    - latency: 2.112453ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:07:02Z"
    - latency: 1.996792ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:06:02Z"
    - latency: 2.602888ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:05:02Z"
    - latency: 2.16841ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:04:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T08:38:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-115-to-network-check-target-ip-10-0-139-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-115.ec2.internal
      uid: 99281272-5ad7-4e80-a41f-11b5bf0f7e23
    resourceVersion: "17683"
    uid: fc58f15c-6d12-4eca-8a6a-f74d73507bd8
  spec:
    sourcePod: network-check-source-7b678d77c7-nzw48
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T08:45:02Z"
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.618164ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:13:02Z"
    - latency: 1.821669ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:12:02Z"
    - latency: 2.3678ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:11:02Z"
    - latency: 1.472857ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:10:02Z"
    - latency: 1.335197ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:09:02Z"
    - latency: 1.804396ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:08:02Z"
    - latency: 1.796917ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:07:02Z"
    - latency: 1.77501ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:06:02Z"
    - latency: 1.632571ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:05:02Z"
    - latency: 2.017826ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:04:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T08:38:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-115-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-115.ec2.internal
      uid: 99281272-5ad7-4e80-a41f-11b5bf0f7e23
    resourceVersion: "16699"
    uid: 99257761-ced8-4529-842e-50976f540c39
  spec:
    sourcePod: network-check-source-7b678d77c7-nzw48
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T08:44:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 763.367µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:08:02Z"
    - latency: 1.558024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:08:02Z"
    - latency: 1.140953ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:07:02Z"
    - latency: 1.80958ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:07:02Z"
    - latency: 993.618µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:06:02Z"
    - latency: 2.118847ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:06:02Z"
    - latency: 976.104µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:05:02Z"
    - latency: 2.277833ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:05:02Z"
    - latency: 1.115968ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T09:04:02Z"
    - latency: 2.176372ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T09:04:02Z"
kind: List
metadata:
  resourceVersion: ""