apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-10-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-10.ec2.internal
      uid: 3a32987d-a333-4f3c-a47c-6725c136d5aa
    resourceVersion: "71350"
    uid: f731df40-ba46-4f33-aeb7-da440a9d6845
  spec:
    sourcePod: network-check-source-7d88cb55d8-8sgzj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:28:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.528733ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:10:09Z"
    - latency: 1.126163ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:09:09Z"
    - latency: 1.119736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:08:09Z"
    - latency: 999.264µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:07:09Z"
    - latency: 1.166494ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:06:09Z"
    - latency: 1.060496ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:05:09Z"
    - latency: 1.691728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:04:09Z"
    - latency: 1.362842ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:03:09Z"
    - latency: 1.317418ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:02:09Z"
    - latency: 810.127µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:01:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-10-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-10.ec2.internal
      uid: 3a32987d-a333-4f3c-a47c-6725c136d5aa
    resourceVersion: "69303"
    uid: 44fce7d6-6233-4a6a-884d-a2230210aa5c
  spec:
    sourcePod: network-check-source-7d88cb55d8-8sgzj
    targetEndpoint: acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:27:09Z"
      message: 'load-balancer-api-external: tcp connection to acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.206278ms
      message: 'load-balancer-api-external: tcp connection to acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:09:09Z"
    - latency: 7.258301ms
      message: 'load-balancer-api-external: resolved host name acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:09:09Z"
    - latency: 3.879618ms
      message: 'load-balancer-api-external: tcp connection to acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:08:09Z"
    - latency: 6.611239ms
      message: 'load-balancer-api-external: resolved host name acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:08:09Z"
    - latency: 4.467836ms
      message: 'load-balancer-api-external: tcp connection to acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:07:09Z"
    - latency: 7.312249ms
      message: 'load-balancer-api-external: resolved host name acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:07:09Z"
    - latency: 4.284209ms
      message: 'load-balancer-api-external: tcp connection to acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:06:09Z"
    - latency: 6.96744ms
      message: 'load-balancer-api-external: resolved host name acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:06:09Z"
    - latency: 4.549076ms
      message: 'load-balancer-api-external: tcp connection to acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:05:09Z"
    - latency: 7.135155ms
      message: 'load-balancer-api-external: resolved host name acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:05:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-10-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-10.ec2.internal
      uid: 3a32987d-a333-4f3c-a47c-6725c136d5aa
    resourceVersion: "69304"
    uid: fc7ca4bd-f404-43b2-b3e9-db011a84351c
  spec:
    sourcePod: network-check-source-7d88cb55d8-8sgzj
    targetEndpoint: acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:27:09Z"
      message: 'load-balancer-api-internal: tcp connection to acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.156773ms
      message: 'load-balancer-api-internal: tcp connection to acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:09:09Z"
    - latency: 7.225255ms
      message: 'load-balancer-api-internal: resolved host name acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:09:09Z"
    - latency: 3.889007ms
      message: 'load-balancer-api-internal: tcp connection to acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:08:09Z"
    - latency: 6.578243ms
      message: 'load-balancer-api-internal: resolved host name acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:08:09Z"
    - latency: 4.534702ms
      message: 'load-balancer-api-internal: tcp connection to acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:07:09Z"
    - latency: 7.22264ms
      message: 'load-balancer-api-internal: resolved host name acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:07:09Z"
    - latency: 3.839826ms
      message: 'load-balancer-api-internal: tcp connection to acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:06:09Z"
    - latency: 6.884949ms
      message: 'load-balancer-api-internal: resolved host name acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:06:09Z"
    - latency: 4.674154ms
      message: 'load-balancer-api-internal: tcp connection to acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:05:09Z"
    - latency: 7.107707ms
      message: 'load-balancer-api-internal: resolved host name acd59e9a8f5bf427d8fce5c78b1e6923-ca08e8b86d711422.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:05:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-10-to-network-check-target-ip-10-0-133-10
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-10.ec2.internal
      uid: 3a32987d-a333-4f3c-a47c-6725c136d5aa
    resourceVersion: "71348"
    uid: a67b1fe4-e5fb-4e14-b80f-3ae8136de037
  spec:
    sourcePod: network-check-source-7d88cb55d8-8sgzj
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:28:09Z"
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.293335ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:10:09Z"
    - latency: 1.351961ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:09:09Z"
    - latency: 755.307µs
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:08:09Z"
    - latency: 860.841µs
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:07:09Z"
    - latency: 914.614µs
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:06:09Z"
    - latency: 860.226µs
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:05:09Z"
    - latency: 825.118µs
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:04:09Z"
    - latency: 1.110247ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:03:09Z"
    - latency: 1.435636ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:02:09Z"
    - latency: 1.071326ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:01:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-10-to-network-check-target-ip-10-0-135-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-10.ec2.internal
      uid: 3a32987d-a333-4f3c-a47c-6725c136d5aa
    resourceVersion: "71347"
    uid: c6c3e811-7fe2-4b35-9b7e-25b97f21db74
  spec:
    sourcePod: network-check-source-7d88cb55d8-8sgzj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:28:09Z"
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.676203ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:10:09Z"
    - latency: 1.868674ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:09:09Z"
    - latency: 1.786675ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:08:09Z"
    - latency: 1.715987ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:07:09Z"
    - latency: 1.87404ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:06:09Z"
    - latency: 1.461666ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:05:09Z"
    - latency: 1.873059ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:04:09Z"
    - latency: 1.74003ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:03:09Z"
    - latency: 1.639956ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:02:09Z"
    - latency: 1.89039ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:01:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-10-to-network-check-target-ip-10-0-142-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-10.ec2.internal
      uid: 3a32987d-a333-4f3c-a47c-6725c136d5aa
    resourceVersion: "71349"
    uid: 1d91a812-b80e-40e0-aa9a-bcdaa7774e26
  spec:
    sourcePod: network-check-source-7d88cb55d8-8sgzj
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:28:09Z"
      message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.100266ms
      message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:10:09Z"
    - latency: 2.273486ms
      message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:09:09Z"
    - latency: 2.13933ms
      message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:08:09Z"
    - latency: 2.242108ms
      message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:07:09Z"
    - latency: 2.150587ms
      message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:06:09Z"
    - latency: 2.056436ms
      message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:05:09Z"
    - latency: 2.083431ms
      message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:04:09Z"
    - latency: 2.165414ms
      message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:03:09Z"
    - latency: 2.20615ms
      message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:02:09Z"
    - latency: 2.414249ms
      message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:01:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:21:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-10-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-10.ec2.internal
      uid: 3a32987d-a333-4f3c-a47c-6725c136d5aa
    resourceVersion: "69302"
    uid: 7f156c19-e4b1-47e8-b8ca-30e88ffcc5d8
  spec:
    sourcePod: network-check-source-7d88cb55d8-8sgzj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:27:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.748µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:09:09Z"
    - latency: 1.933975ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:09:09Z"
    - latency: 908.582µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:08:09Z"
    - latency: 1.651578ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:08:09Z"
    - latency: 861.056µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:07:09Z"
    - latency: 1.888998ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:07:09Z"
    - latency: 780.066µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:06:09Z"
    - latency: 1.92214ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:06:09Z"
    - latency: 835.027µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T01:05:09Z"
    - latency: 2.228918ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T01:05:09Z"
kind: List
metadata:
  resourceVersion: ""