apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T02:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: b7d1d9a1-11da-4cee-a4e8-b303c3cb839b
    resourceVersion: "71645"
    uid: 097bb929-816f-4aa3-a3fa-73cbac69c3ee
  spec:
    sourcePod: network-check-source-7d88cb55d8-x9v2z
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T02:39:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.308912ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:21:36Z"
    - latency: 1.331253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:20:36Z"
    - latency: 1.542663ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:19:36Z"
    - latency: 986.323µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:18:36Z"
    - latency: 751.464µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:17:36Z"
    - latency: 1.556841ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:16:36Z"
    - latency: 1.337114ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:15:36Z"
    - latency: 1.228388ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:14:36Z"
    - latency: 879.36µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:13:36Z"
    - latency: 1.083762ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:12:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T02:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: b7d1d9a1-11da-4cee-a4e8-b303c3cb839b
    resourceVersion: "70380"
    uid: dcffc848-cc3c-450a-8d51-0409a2b4b320
  spec:
    sourcePod: network-check-source-7d88cb55d8-x9v2z
    targetEndpoint: ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T02:38:36Z"
      message: 'load-balancer-api-external: tcp connection to ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.707425ms
      message: 'load-balancer-api-external: tcp connection to ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:20:36Z"
    - latency: 10.221543ms
      message: 'load-balancer-api-external: resolved host name ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:20:36Z"
    - latency: 4.272441ms
      message: 'load-balancer-api-external: tcp connection to ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:19:36Z"
    - latency: 9.811471ms
      message: 'load-balancer-api-external: resolved host name ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:19:36Z"
    - latency: 3.801314ms
      message: 'load-balancer-api-external: tcp connection to ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:18:36Z"
    - latency: 8.679142ms
      message: 'load-balancer-api-external: resolved host name ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:18:36Z"
    - latency: 5.809822ms
      message: 'load-balancer-api-external: tcp connection to ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:17:36Z"
    - latency: 9.690599ms
      message: 'load-balancer-api-external: resolved host name ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:17:36Z"
    - latency: 4.157905ms
      message: 'load-balancer-api-external: tcp connection to ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:16:36Z"
    - latency: 9.517395ms
      message: 'load-balancer-api-external: resolved host name ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:16:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T02:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: b7d1d9a1-11da-4cee-a4e8-b303c3cb839b
    resourceVersion: "70379"
    uid: c0da09bb-d7f4-4a17-80bd-a3e69ff100a5
  spec:
    sourcePod: network-check-source-7d88cb55d8-x9v2z
    targetEndpoint: ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T02:38:36Z"
      message: 'load-balancer-api-internal: tcp connection to ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.29737ms
      message: 'load-balancer-api-internal: tcp connection to ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:20:36Z"
    - latency: 10.256341ms
      message: 'load-balancer-api-internal: resolved host name ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:20:36Z"
    - latency: 4.991087ms
      message: 'load-balancer-api-internal: tcp connection to ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:19:36Z"
    - latency: 9.881946ms
      message: 'load-balancer-api-internal: resolved host name ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:19:36Z"
    - latency: 3.694611ms
      message: 'load-balancer-api-internal: tcp connection to ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:18:36Z"
    - latency: 8.72159ms
      message: 'load-balancer-api-internal: resolved host name ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:18:36Z"
    - latency: 5.805013ms
      message: 'load-balancer-api-internal: tcp connection to ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:17:36Z"
    - latency: 9.629776ms
      message: 'load-balancer-api-internal: resolved host name ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:17:36Z"
    - latency: 4.983148ms
      message: 'load-balancer-api-internal: tcp connection to ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:16:36Z"
    - latency: 9.626846ms
      message: 'load-balancer-api-internal: resolved host name ac615414a533b428babcf658c105701a-8892ac593c4408cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:16:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T02:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-network-check-target-ip-10-0-131-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: b7d1d9a1-11da-4cee-a4e8-b303c3cb839b
    resourceVersion: "71642"
    uid: 72771e40-502e-4c21-a610-dfb9c6ec96ed
  spec:
    sourcePod: network-check-source-7d88cb55d8-x9v2z
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T02:39:36Z"
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.643345ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:21:36Z"
    - latency: 1.30502ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:20:36Z"
    - latency: 1.787902ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:19:36Z"
    - latency: 951.877µs
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:18:36Z"
    - latency: 840.909µs
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:17:36Z"
    - latency: 1.025088ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:16:36Z"
    - latency: 1.287007ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:15:36Z"
    - latency: 966.89µs
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:14:36Z"
    - latency: 1.272362ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:13:36Z"
    - latency: 905.238µs
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:12:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T02:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-network-check-target-ip-10-0-132-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: b7d1d9a1-11da-4cee-a4e8-b303c3cb839b
    resourceVersion: "71644"
    uid: cb55c6cf-388f-4c8a-bbea-051f95530e5e
  spec:
    sourcePod: network-check-source-7d88cb55d8-x9v2z
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T02:39:36Z"
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.429217ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:21:36Z"
    - latency: 2.246213ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:20:36Z"
    - latency: 2.244802ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:19:36Z"
    - latency: 2.303894ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:18:36Z"
    - latency: 2.228182ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:17:36Z"
    - latency: 2.711654ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:16:36Z"
    - latency: 2.838039ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:15:36Z"
    - latency: 2.354261ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:14:36Z"
    - latency: 2.105152ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:13:36Z"
    - latency: 2.730889ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:12:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T02:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-network-check-target-ip-10-0-136-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: b7d1d9a1-11da-4cee-a4e8-b303c3cb839b
    resourceVersion: "71643"
    uid: 5ef6eb4f-af70-4fcf-b9dc-a36a0ee3d353
  spec:
    sourcePod: network-check-source-7d88cb55d8-x9v2z
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T02:39:36Z"
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.373728ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:21:36Z"
    - latency: 2.386539ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:20:36Z"
    - latency: 2.244808ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:19:36Z"
    - latency: 2.22296ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:18:36Z"
    - latency: 2.38163ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:17:36Z"
    - latency: 2.236784ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:16:36Z"
    - latency: 2.303932ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:15:36Z"
    - latency: 2.473082ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:14:36Z"
    - latency: 2.389661ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:13:36Z"
    - latency: 2.093537ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:12:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T02:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: b7d1d9a1-11da-4cee-a4e8-b303c3cb839b
    resourceVersion: "70378"
    uid: 96fb113c-99b0-45db-a33b-53cda2b1063a
  spec:
    sourcePod: network-check-source-7d88cb55d8-x9v2z
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T02:38:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 890.055µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:20:36Z"
    - latency: 2.219316ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:20:36Z"
    - latency: 890.306µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:19:36Z"
    - latency: 2.739558ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:19:36Z"
    - latency: 961.315µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:18:36Z"
    - latency: 1.807382ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:18:36Z"
    - latency: 1.203182ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:17:36Z"
    - latency: 1.993256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:17:36Z"
    - latency: 937.13µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T03:16:36Z"
    - latency: 2.271617ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T03:16:36Z"
kind: List
metadata:
  resourceVersion: ""