apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:02:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-82-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-82.ec2.internal
      uid: d0dd7579-8677-4164-8cfb-0ad6107be522
    resourceVersion: "60659"
    uid: f323dc04-4235-40d4-a3a9-7cd83a04f66c
  spec:
    sourcePod: network-check-source-6f8b768455-dvh6b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:09:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 975.395µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:37:22Z"
    - latency: 1.00198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:22Z"
    - latency: 1.125388ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:22Z"
    - latency: 1.570549ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:22Z"
    - latency: 1.116412ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:33:22Z"
    - latency: 1.096927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:32:22Z"
    - latency: 1.382981ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:31:22Z"
    - latency: 1.17176ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:30:22Z"
    - latency: 923.25µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:29:22Z"
    - latency: 825.4µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:28:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:02:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-82-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-82.ec2.internal
      uid: d0dd7579-8677-4164-8cfb-0ad6107be522
    resourceVersion: "61699"
    uid: 80dbd5c3-ce4e-4d0c-8d63-a2c406e10712
  spec:
    sourcePod: network-check-source-6f8b768455-dvh6b
    targetEndpoint: a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:08:22Z"
      message: 'load-balancer-api-external: tcp connection to a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.775761ms
      message: 'load-balancer-api-external: tcp connection to a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:38:22Z"
    - latency: 8.494822ms
      message: 'load-balancer-api-external: resolved host name a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:38:22Z"
    - latency: 3.825987ms
      message: 'load-balancer-api-external: tcp connection to a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:37:22Z"
    - latency: 8.591011ms
      message: 'load-balancer-api-external: resolved host name a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:37:22Z"
    - latency: 5.185364ms
      message: 'load-balancer-api-external: tcp connection to a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:22Z"
    - latency: 8.011123ms
      message: 'load-balancer-api-external: resolved host name a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:36:22Z"
    - latency: 3.438849ms
      message: 'load-balancer-api-external: tcp connection to a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:22Z"
    - latency: 8.681995ms
      message: 'load-balancer-api-external: resolved host name a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:35:22Z"
    - latency: 4.891188ms
      message: 'load-balancer-api-external: tcp connection to a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:22Z"
    - latency: 7.894697ms
      message: 'load-balancer-api-external: resolved host name a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:34:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:02:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-82-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-82.ec2.internal
      uid: d0dd7579-8677-4164-8cfb-0ad6107be522
    resourceVersion: "61698"
    uid: 43d47367-08d9-454d-b6ef-7c3fc4dd319c
  spec:
    sourcePod: network-check-source-6f8b768455-dvh6b
    targetEndpoint: a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:08:22Z"
      message: 'load-balancer-api-internal: tcp connection to a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.782275ms
      message: 'load-balancer-api-internal: tcp connection to a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:38:22Z"
    - latency: 8.391907ms
      message: 'load-balancer-api-internal: resolved host name a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:38:22Z"
    - latency: 3.770424ms
      message: 'load-balancer-api-internal: tcp connection to a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:37:22Z"
    - latency: 8.562581ms
      message: 'load-balancer-api-internal: resolved host name a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:37:22Z"
    - latency: 5.192915ms
      message: 'load-balancer-api-internal: tcp connection to a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:22Z"
    - latency: 7.974976ms
      message: 'load-balancer-api-internal: resolved host name a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:36:22Z"
    - latency: 3.473241ms
      message: 'load-balancer-api-internal: tcp connection to a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:22Z"
    - latency: 8.617423ms
      message: 'load-balancer-api-internal: resolved host name a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:35:22Z"
    - latency: 4.952398ms
      message: 'load-balancer-api-internal: tcp connection to a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:22Z"
    - latency: 7.706061ms
      message: 'load-balancer-api-internal: resolved host name a27ecd80e2fb846ea82d89b98e9b3a89-46ee49a862336a09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:34:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:02:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-82-to-network-check-target-ip-10-0-138-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-82.ec2.internal
      uid: d0dd7579-8677-4164-8cfb-0ad6107be522
    resourceVersion: "60657"
    uid: 928014c1-42e6-4184-b294-75edf71da8d3
  spec:
    sourcePod: network-check-source-6f8b768455-dvh6b
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:09:22Z"
      message: 'network-check-target-ip-10-0-138-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.446312ms
      message: 'network-check-target-ip-10-0-138-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:37:22Z"
    - latency: 2.289169ms
      message: 'network-check-target-ip-10-0-138-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:22Z"
    - latency: 2.295627ms
      message: 'network-check-target-ip-10-0-138-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:22Z"
    - latency: 2.368538ms
      message: 'network-check-target-ip-10-0-138-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:22Z"
    - latency: 2.282407ms
      message: 'network-check-target-ip-10-0-138-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:33:22Z"
    - latency: 2.389008ms
      message: 'network-check-target-ip-10-0-138-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:32:22Z"
    - latency: 2.148503ms
      message: 'network-check-target-ip-10-0-138-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:31:22Z"
    - latency: 2.431033ms
      message: 'network-check-target-ip-10-0-138-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:30:22Z"
    - latency: 2.630455ms
      message: 'network-check-target-ip-10-0-138-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:29:22Z"
    - latency: 2.291698ms
      message: 'network-check-target-ip-10-0-138-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:28:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:02:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-82-to-network-check-target-ip-10-0-139-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-82.ec2.internal
      uid: d0dd7579-8677-4164-8cfb-0ad6107be522
    resourceVersion: "60658"
    uid: c97480f3-8711-4f0c-80ae-7cc21da3fdfc
  spec:
    sourcePod: network-check-source-6f8b768455-dvh6b
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:09:22Z"
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.907279ms
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:37:22Z"
    - latency: 1.929349ms
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:22Z"
    - latency: 1.96585ms
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:22Z"
    - latency: 1.827859ms
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:22Z"
    - latency: 2.001789ms
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:33:22Z"
    - latency: 2.11426ms
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:32:22Z"
    - latency: 2.106897ms
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:31:22Z"
    - latency: 2.056039ms
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:30:22Z"
    - latency: 2.18046ms
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:29:22Z"
    - latency: 1.889326ms
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:28:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:02:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-82-to-network-check-target-ip-10-0-142-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-82.ec2.internal
      uid: d0dd7579-8677-4164-8cfb-0ad6107be522
    resourceVersion: "60656"
    uid: 4ca97215-d86e-4262-bf3f-e8c285f56f97
  spec:
    sourcePod: network-check-source-6f8b768455-dvh6b
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:09:22Z"
      message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.841µs
      message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:37:22Z"
    - latency: 1.620196ms
      message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:22Z"
    - latency: 989.008µs
      message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:22Z"
    - latency: 1.501202ms
      message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:22Z"
    - latency: 878.352µs
      message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:33:22Z"
    - latency: 1.410801ms
      message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:32:22Z"
    - latency: 1.011913ms
      message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:31:22Z"
    - latency: 990.032µs
      message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:30:22Z"
    - latency: 1.114037ms
      message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:29:22Z"
    - latency: 1.270317ms
      message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:28:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:02:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-82-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-82.ec2.internal
      uid: d0dd7579-8677-4164-8cfb-0ad6107be522
    resourceVersion: "61697"
    uid: 51275a08-9dbf-411c-a8d5-f07545f93fed
  spec:
    sourcePod: network-check-source-6f8b768455-dvh6b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:08:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 793.978µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:38:22Z"
    - latency: 1.977002ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:38:22Z"
    - latency: 1.119726ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:37:22Z"
    - latency: 1.820832ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:37:22Z"
    - latency: 889.149µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:22Z"
    - latency: 1.821806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:36:22Z"
    - latency: 1.343532ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:22Z"
    - latency: 1.72339ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:35:22Z"
    - latency: 1.185913ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:22Z"
    - latency: 1.762908ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:34:22Z"
kind: List
metadata:
  resourceVersion: ""