apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-149-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-149.ec2.internal
      uid: 7bb47ca5-9534-4d9f-b695-6f9e1afd0a49
    resourceVersion: "61658"
    uid: c99b42f1-c30b-44a0-a1e2-5db2d616f346
  spec:
    sourcePod: network-check-source-869dcfcdcd-mmlx6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T17:10:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.11699ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:45:27Z"
    - latency: 2.203297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:44:27Z"
    - latency: 826.723µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:43:27Z"
    - latency: 1.267891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:42:27Z"
    - latency: 846.885µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:41:27Z"
    - latency: 1.121365ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:40:27Z"
    - latency: 911.999µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:39:27Z"
    - latency: 1.873213ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:38:27Z"
    - latency: 893.025µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:37:27Z"
    - latency: 973.147µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:36:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-149-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-149.ec2.internal
      uid: 7bb47ca5-9534-4d9f-b695-6f9e1afd0a49
    resourceVersion: "61660"
    uid: cef6ff61-49a3-4583-b605-3ed0467f0166
  spec:
    sourcePod: network-check-source-869dcfcdcd-mmlx6
    targetEndpoint: af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T17:09:27Z"
      message: 'load-balancer-api-external: tcp connection to af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.99966ms
      message: 'load-balancer-api-external: tcp connection to af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:45:27Z"
    - latency: 6.75054ms
      message: 'load-balancer-api-external: resolved host name af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:45:27Z"
    - latency: 4.559765ms
      message: 'load-balancer-api-external: tcp connection to af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:44:27Z"
    - latency: 9.123479ms
      message: 'load-balancer-api-external: resolved host name af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:44:27Z"
    - latency: 6.603502ms
      message: 'load-balancer-api-external: tcp connection to af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:43:27Z"
    - latency: 6.29859ms
      message: 'load-balancer-api-external: resolved host name af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:43:27Z"
    - latency: 3.511643ms
      message: 'load-balancer-api-external: tcp connection to af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:42:27Z"
    - latency: 7.036386ms
      message: 'load-balancer-api-external: resolved host name af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:42:27Z"
    - latency: 4.700838ms
      message: 'load-balancer-api-external: tcp connection to af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:41:27Z"
    - latency: 6.293004ms
      message: 'load-balancer-api-external: resolved host name af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:41:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-149-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-149.ec2.internal
      uid: 7bb47ca5-9534-4d9f-b695-6f9e1afd0a49
    resourceVersion: "61659"
    uid: a5e018a3-cfdf-4276-b635-15cd1a196ced
  spec:
    sourcePod: network-check-source-869dcfcdcd-mmlx6
    targetEndpoint: af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T17:09:27Z"
      message: 'load-balancer-api-internal: tcp connection to af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.503812ms
      message: 'load-balancer-api-internal: tcp connection to af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:45:27Z"
    - latency: 6.67397ms
      message: 'load-balancer-api-internal: resolved host name af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:45:27Z"
    - latency: 4.625576ms
      message: 'load-balancer-api-internal: tcp connection to af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:44:27Z"
    - latency: 8.584348ms
      message: 'load-balancer-api-internal: resolved host name af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:44:27Z"
    - latency: 6.590838ms
      message: 'load-balancer-api-internal: tcp connection to af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:43:27Z"
    - latency: 6.369636ms
      message: 'load-balancer-api-internal: resolved host name af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:43:27Z"
    - latency: 4.570578ms
      message: 'load-balancer-api-internal: tcp connection to af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:42:27Z"
    - latency: 6.919294ms
      message: 'load-balancer-api-internal: resolved host name af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:42:27Z"
    - latency: 4.710178ms
      message: 'load-balancer-api-internal: tcp connection to af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:41:27Z"
    - latency: 6.336779ms
      message: 'load-balancer-api-internal: resolved host name af721174c2f0d403390b529275a78dc8-d8893fcc9b8c28d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:41:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-149-to-network-check-target-ip-10-0-134-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-149.ec2.internal
      uid: 7bb47ca5-9534-4d9f-b695-6f9e1afd0a49
    resourceVersion: "61655"
    uid: 3c12ffb0-2697-4952-bc52-2e3ce9107014
  spec:
    sourcePod: network-check-source-869dcfcdcd-mmlx6
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T17:10:27Z"
      message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.951478ms
      message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:45:27Z"
    - latency: 2.398679ms
      message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:44:27Z"
    - latency: 1.668751ms
      message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:43:27Z"
    - latency: 2.059154ms
      message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:42:27Z"
    - latency: 1.944396ms
      message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:41:27Z"
    - latency: 1.932691ms
      message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:40:27Z"
    - latency: 1.817591ms
      message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:39:27Z"
    - latency: 1.941055ms
      message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:38:27Z"
    - latency: 1.888504ms
      message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:37:27Z"
    - latency: 1.929564ms
      message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:36:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-149-to-network-check-target-ip-10-0-140-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-149.ec2.internal
      uid: 7bb47ca5-9534-4d9f-b695-6f9e1afd0a49
    resourceVersion: "61654"
    uid: 56463a7f-b1be-4725-9efa-189431ddc9b5
  spec:
    sourcePod: network-check-source-869dcfcdcd-mmlx6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T17:10:27Z"
      message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.065064ms
      message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:45:27Z"
    - latency: 3.247684ms
      message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:44:27Z"
    - latency: 1.263896ms
      message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:43:27Z"
    - latency: 886.087µs
      message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:42:27Z"
    - latency: 1.008852ms
      message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:41:27Z"
    - latency: 1.050317ms
      message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:40:27Z"
    - latency: 725.769µs
      message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:39:27Z"
    - latency: 1.059456ms
      message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:38:27Z"
    - latency: 1.015303ms
      message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:37:27Z"
    - latency: 1.132575ms
      message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:36:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-149-to-network-check-target-ip-10-0-142-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-149.ec2.internal
      uid: 7bb47ca5-9534-4d9f-b695-6f9e1afd0a49
    resourceVersion: "61656"
    uid: 61399f97-9595-4930-8233-aab65a78600f
  spec:
    sourcePod: network-check-source-869dcfcdcd-mmlx6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T17:10:27Z"
      message: 'network-check-target-ip-10-0-142-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.094947ms
      message: 'network-check-target-ip-10-0-142-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:45:27Z"
    - latency: 2.556002ms
      message: 'network-check-target-ip-10-0-142-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:44:27Z"
    - latency: 1.977179ms
      message: 'network-check-target-ip-10-0-142-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:43:27Z"
    - latency: 2.137717ms
      message: 'network-check-target-ip-10-0-142-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:42:27Z"
    - latency: 2.391543ms
      message: 'network-check-target-ip-10-0-142-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:41:27Z"
    - latency: 2.432789ms
      message: 'network-check-target-ip-10-0-142-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:40:27Z"
    - latency: 1.78748ms
      message: 'network-check-target-ip-10-0-142-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:39:27Z"
    - latency: 2.34848ms
      message: 'network-check-target-ip-10-0-142-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:38:27Z"
    - latency: 2.171132ms
      message: 'network-check-target-ip-10-0-142-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:37:27Z"
    - latency: 2.133065ms
      message: 'network-check-target-ip-10-0-142-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:36:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-149-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-149.ec2.internal
      uid: 7bb47ca5-9534-4d9f-b695-6f9e1afd0a49
    resourceVersion: "61657"
    uid: e07c7b58-95b1-4a92-853b-0d2daba1ee21
  spec:
    sourcePod: network-check-source-869dcfcdcd-mmlx6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T17:09:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.007822ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:45:27Z"
    - latency: 1.961627ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:45:27Z"
    - latency: 902.377µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:44:27Z"
    - latency: 3.645564ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:44:27Z"
    - latency: 781.657µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:43:27Z"
    - latency: 1.697584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:43:27Z"
    - latency: 909.847µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:42:27Z"
    - latency: 2.124852ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:42:27Z"
    - latency: 833.416µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T17:41:27Z"
    - latency: 2.233258ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T17:41:27Z"
kind: List
metadata:
  resourceVersion: ""