apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:22:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-164-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-164.ec2.internal
      uid: 39ddf8c4-f553-4621-94d9-0aa90abbead1
    resourceVersion: "19407"
    uid: d423cca9-0350-43ca-9334-8414ca8d25ea
  spec:
    sourcePod: network-check-source-7f44b6dd87-bzvwj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:29:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.013542ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:17Z"
    - latency: 677.338µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:17Z"
    - latency: 1.28462ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:17Z"
    - latency: 935.513µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:17Z"
    - latency: 1.333346ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:17Z"
    - latency: 688.414µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:38:17Z"
    - latency: 899.663µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:37:17Z"
    - latency: 933.721µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:36:17Z"
    - latency: 875.224µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:35:17Z"
    - latency: 926.65µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:34:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:22:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-164-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-164.ec2.internal
      uid: 39ddf8c4-f553-4621-94d9-0aa90abbead1
    resourceVersion: "20576"
    uid: 1cbea911-67cb-45d7-ad50-d0d5b135adad
  spec:
    sourcePod: network-check-source-7f44b6dd87-bzvwj
    targetEndpoint: a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:28:17Z"
      message: 'load-balancer-api-external: tcp connection to a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.001272ms
      message: 'load-balancer-api-external: tcp connection to a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:46:17Z"
    - latency: 9.497748ms
      message: 'load-balancer-api-external: resolved host name a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:46:17Z"
    - latency: 4.980709ms
      message: 'load-balancer-api-external: tcp connection to a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:45:17Z"
    - latency: 8.740136ms
      message: 'load-balancer-api-external: resolved host name a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:45:17Z"
    - latency: 5.219323ms
      message: 'load-balancer-api-external: tcp connection to a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:44:17Z"
    - latency: 8.813959ms
      message: 'load-balancer-api-external: resolved host name a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:44:17Z"
    - latency: 6.312622ms
      message: 'load-balancer-api-external: tcp connection to a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:17Z"
    - latency: 11.221291ms
      message: 'load-balancer-api-external: resolved host name a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:43:17Z"
    - latency: 5.125132ms
      message: 'load-balancer-api-external: tcp connection to a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:17Z"
    - latency: 7.61127ms
      message: 'load-balancer-api-external: resolved host name a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:42:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:22:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-164-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-164.ec2.internal
      uid: 39ddf8c4-f553-4621-94d9-0aa90abbead1
    resourceVersion: "20577"
    uid: 40dc8c06-72d1-40e2-9313-29c59dc03ccc
  spec:
    sourcePod: network-check-source-7f44b6dd87-bzvwj
    targetEndpoint: a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:28:17Z"
      message: 'load-balancer-api-internal: tcp connection to a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.886942ms
      message: 'load-balancer-api-internal: tcp connection to a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:46:17Z"
    - latency: 9.455491ms
      message: 'load-balancer-api-internal: resolved host name a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:46:17Z"
    - latency: 4.595111ms
      message: 'load-balancer-api-internal: tcp connection to a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:45:17Z"
    - latency: 8.788877ms
      message: 'load-balancer-api-internal: resolved host name a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:45:17Z"
    - latency: 5.098599ms
      message: 'load-balancer-api-internal: tcp connection to a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:44:17Z"
    - latency: 8.749104ms
      message: 'load-balancer-api-internal: resolved host name a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:44:17Z"
    - latency: 7.596628ms
      message: 'load-balancer-api-internal: tcp connection to a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:17Z"
    - latency: 11.100097ms
      message: 'load-balancer-api-internal: resolved host name a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:43:17Z"
    - latency: 4.638273ms
      message: 'load-balancer-api-internal: tcp connection to a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:17Z"
    - latency: 7.629196ms
      message: 'load-balancer-api-internal: resolved host name a651b1cd6245f4e2f801e7b7d58ce0b8-0162d905688e2063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:42:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:22:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-164-to-network-check-target-ip-10-0-140-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-164.ec2.internal
      uid: 39ddf8c4-f553-4621-94d9-0aa90abbead1
    resourceVersion: "19405"
    uid: fc3f95c8-1ba6-4edb-93bc-80fc9b16df4c
  spec:
    sourcePod: network-check-source-7f44b6dd87-bzvwj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:29:17Z"
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.321718ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:17Z"
    - latency: 1.088546ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:17Z"
    - latency: 955.169µs
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:17Z"
    - latency: 780.848µs
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:17Z"
    - latency: 870.146µs
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:17Z"
    - latency: 3.916466ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:38:17Z"
    - latency: 876.541µs
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:37:17Z"
    - latency: 1.04048ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:36:17Z"
    - latency: 1.049198ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:35:17Z"
    - latency: 1.263452ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:34:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:22:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-164-to-network-check-target-ip-10-0-141-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-164.ec2.internal
      uid: 39ddf8c4-f553-4621-94d9-0aa90abbead1
    resourceVersion: "19406"
    uid: e35265cf-c688-4fa7-ae71-55db1aad09a0
  spec:
    sourcePod: network-check-source-7f44b6dd87-bzvwj
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:29:17Z"
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.874186ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:17Z"
    - latency: 1.71879ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:17Z"
    - latency: 1.935144ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:17Z"
    - latency: 2.034081ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:17Z"
    - latency: 1.880131ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:17Z"
    - latency: 1.871019ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:38:17Z"
    - latency: 1.798973ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:37:17Z"
    - latency: 2.009061ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:36:17Z"
    - latency: 1.738396ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:35:17Z"
    - latency: 1.807525ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:34:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:22:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-164-to-network-check-target-ip-10-0-142-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-164.ec2.internal
      uid: 39ddf8c4-f553-4621-94d9-0aa90abbead1
    resourceVersion: "19404"
    uid: 20463781-264e-4a97-82eb-5dda58d1b44f
  spec:
    sourcePod: network-check-source-7f44b6dd87-bzvwj
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:29:17Z"
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.091866ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:17Z"
    - latency: 1.866082ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:17Z"
    - latency: 1.992483ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:17Z"
    - latency: 1.979746ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:17Z"
    - latency: 8.105515ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:17Z"
    - latency: 4.334749ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:38:17Z"
    - latency: 2.040043ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:37:17Z"
    - latency: 2.109185ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:36:17Z"
    - latency: 1.902622ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:35:17Z"
    - latency: 2.011549ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:34:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:22:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-164-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-164.ec2.internal
      uid: 39ddf8c4-f553-4621-94d9-0aa90abbead1
    resourceVersion: "20575"
    uid: 6ee920e6-7fc7-42b0-af66-511f8303761c
  spec:
    sourcePod: network-check-source-7f44b6dd87-bzvwj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:28:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 818.161µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:46:17Z"
    - latency: 2.403778ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:46:17Z"
    - latency: 913.092µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:45:17Z"
    - latency: 1.918741ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:45:17Z"
    - latency: 1.045615ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:44:17Z"
    - latency: 1.83243ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:44:17Z"
    - latency: 1.272772ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:17Z"
    - latency: 1.853087ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:43:17Z"
    - latency: 687.394µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:17Z"
    - latency: 1.912629ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:42:17Z"
kind: List
metadata:
  resourceVersion: ""