apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:46:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-117-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-117.ec2.internal
      uid: d1aaef36-776f-4bcc-86b9-28c715faf215
    resourceVersion: "23705"
    uid: 444ec729-2322-434f-ac3c-02787de9cf52
  spec:
    sourcePod: network-check-source-7cbc45fddc-cjf9d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:53:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.238614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:07:12Z"
    - latency: 1.020472ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:06:12Z"
    - latency: 1.417337ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:05:12Z"
    - latency: 1.154276ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:04:12Z"
    - latency: 876.149µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:03:12Z"
    - latency: 1.079187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:02:12Z"
    - latency: 1.137172ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:01:12Z"
    - latency: 1.155263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:00:12Z"
    - latency: 1.154312ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:59:12Z"
    - latency: 1.227516ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:58:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:46:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-117-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-117.ec2.internal
      uid: d1aaef36-776f-4bcc-86b9-28c715faf215
    resourceVersion: "22266"
    uid: e8f82276-17df-44bf-8f64-05f97b4749d0
  spec:
    sourcePod: network-check-source-7cbc45fddc-cjf9d
    targetEndpoint: ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:52:12Z"
      message: 'load-balancer-api-external: tcp connection to ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.57665ms
      message: 'load-balancer-api-external: tcp connection to ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:04:12Z"
    - latency: 8.513837ms
      message: 'load-balancer-api-external: resolved host name ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:04:12Z"
    - latency: 5.391147ms
      message: 'load-balancer-api-external: tcp connection to ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:03:12Z"
    - latency: 8.853514ms
      message: 'load-balancer-api-external: resolved host name ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:03:12Z"
    - latency: 5.360916ms
      message: 'load-balancer-api-external: tcp connection to ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:02:12Z"
    - latency: 8.09527ms
      message: 'load-balancer-api-external: resolved host name ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:02:12Z"
    - latency: 4.636566ms
      message: 'load-balancer-api-external: tcp connection to ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:01:12Z"
    - latency: 9.513207ms
      message: 'load-balancer-api-external: resolved host name ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:01:12Z"
    - latency: 4.316055ms
      message: 'load-balancer-api-external: tcp connection to ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:00:12Z"
    - latency: 8.886478ms
      message: 'load-balancer-api-external: resolved host name ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:46:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-117-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-117.ec2.internal
      uid: d1aaef36-776f-4bcc-86b9-28c715faf215
    resourceVersion: "22265"
    uid: 7683cb9f-2c04-455b-afe5-83fc457f47c4
  spec:
    sourcePod: network-check-source-7cbc45fddc-cjf9d
    targetEndpoint: ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:52:12Z"
      message: 'load-balancer-api-internal: tcp connection to ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.627351ms
      message: 'load-balancer-api-internal: tcp connection to ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:04:12Z"
    - latency: 8.435472ms
      message: 'load-balancer-api-internal: resolved host name ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:04:12Z"
    - latency: 5.048807ms
      message: 'load-balancer-api-internal: tcp connection to ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:03:12Z"
    - latency: 8.914669ms
      message: 'load-balancer-api-internal: resolved host name ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:03:12Z"
    - latency: 5.439422ms
      message: 'load-balancer-api-internal: tcp connection to ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:02:12Z"
    - latency: 8.032027ms
      message: 'load-balancer-api-internal: resolved host name ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:02:12Z"
    - latency: 4.667899ms
      message: 'load-balancer-api-internal: tcp connection to ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:01:12Z"
    - latency: 9.455005ms
      message: 'load-balancer-api-internal: resolved host name ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:01:12Z"
    - latency: 4.313818ms
      message: 'load-balancer-api-internal: tcp connection to ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:00:12Z"
    - latency: 8.837058ms
      message: 'load-balancer-api-internal: resolved host name ad5f56725d7f241f6b86e44f39e9f19d-15abb8b2bd870b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:46:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-117-to-network-check-target-ip-10-0-130-106
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-117.ec2.internal
      uid: d1aaef36-776f-4bcc-86b9-28c715faf215
    resourceVersion: "23704"
    uid: b61f3d0d-fb57-4f20-8c4d-d8ea7bef490a
  spec:
    sourcePod: network-check-source-7cbc45fddc-cjf9d
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:53:12Z"
      message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.176567ms
      message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:07:12Z"
    - latency: 2.274861ms
      message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:06:12Z"
    - latency: 2.090614ms
      message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:05:12Z"
    - latency: 2.442604ms
      message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:04:12Z"
    - latency: 2.076922ms
      message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:03:12Z"
    - latency: 2.352317ms
      message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:02:12Z"
    - latency: 2.187091ms
      message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:01:12Z"
    - latency: 2.009535ms
      message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:00:12Z"
    - latency: 2.175529ms
      message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:59:12Z"
    - latency: 1.85264ms
      message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:58:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:46:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-117-to-network-check-target-ip-10-0-132-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-117.ec2.internal
      uid: d1aaef36-776f-4bcc-86b9-28c715faf215
    resourceVersion: "23703"
    uid: 1e8eeb10-27d0-4507-b9db-52369054e7b6
  spec:
    sourcePod: network-check-source-7cbc45fddc-cjf9d
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:53:12Z"
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.722187ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:07:12Z"
    - latency: 1.935128ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:06:12Z"
    - latency: 1.642597ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:05:12Z"
    - latency: 1.834068ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:04:12Z"
    - latency: 1.936091ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:03:12Z"
    - latency: 1.985785ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:02:12Z"
    - latency: 1.865808ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:01:12Z"
    - latency: 1.960311ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:00:12Z"
    - latency: 1.794836ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:59:12Z"
    - latency: 2.156071ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:58:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:46:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-117-to-network-check-target-ip-10-0-138-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-117.ec2.internal
      uid: d1aaef36-776f-4bcc-86b9-28c715faf215
    resourceVersion: "23702"
    uid: e824d7f0-7b54-42e2-9695-68f0923b6647
  spec:
    sourcePod: network-check-source-7cbc45fddc-cjf9d
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:53:12Z"
      message: 'network-check-target-ip-10-0-138-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 922.195µs
      message: 'network-check-target-ip-10-0-138-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:07:12Z"
    - latency: 798.449µs
      message: 'network-check-target-ip-10-0-138-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:06:12Z"
    - latency: 809.044µs
      message: 'network-check-target-ip-10-0-138-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:05:12Z"
    - latency: 1.182627ms
      message: 'network-check-target-ip-10-0-138-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:04:12Z"
    - latency: 805.777µs
      message: 'network-check-target-ip-10-0-138-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:03:12Z"
    - latency: 800.62µs
      message: 'network-check-target-ip-10-0-138-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:02:12Z"
    - latency: 898.614µs
      message: 'network-check-target-ip-10-0-138-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:01:12Z"
    - latency: 809.45µs
      message: 'network-check-target-ip-10-0-138-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:00:12Z"
    - latency: 834.322µs
      message: 'network-check-target-ip-10-0-138-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:59:12Z"
    - latency: 720.666µs
      message: 'network-check-target-ip-10-0-138-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:58:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:46:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-117-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-117.ec2.internal
      uid: d1aaef36-776f-4bcc-86b9-28c715faf215
    resourceVersion: "22264"
    uid: c2f912f8-87cd-4a28-8a32-2b2c847745a9
  spec:
    sourcePod: network-check-source-7cbc45fddc-cjf9d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:52:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 729.085µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:04:12Z"
    - latency: 1.771431ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:04:12Z"
    - latency: 1.168365ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:03:12Z"
    - latency: 1.689588ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:03:12Z"
    - latency: 857.095µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:02:12Z"
    - latency: 1.801863ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:02:12Z"
    - latency: 1.112335ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:01:12Z"
    - latency: 1.860853ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:01:12Z"
    - latency: 773.938µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:00:12Z"
    - latency: 2.051764ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:00:12Z"
kind: List
metadata:
  resourceVersion: ""