apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T10:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-31-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-31.ec2.internal
      uid: f3c124a3-73c2-4e59-8985-2a42e9d8e026
    resourceVersion: "74313"
    uid: 947a1989-f460-4fa5-a498-557a7e44482a
  spec:
    sourcePod: network-check-source-7d88cb55d8-p6nrr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T10:33:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 770.909µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:22:09Z"
    - latency: 1.126276ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:21:09Z"
    - latency: 1.300521ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:20:09Z"
    - latency: 1.059804ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:19:09Z"
    - latency: 1.055268ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:18:09Z"
    - latency: 961.236µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:17:09Z"
    - latency: 1.013572ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:16:09Z"
    - latency: 990.975µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:15:09Z"
    - latency: 897.236µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:14:09Z"
    - latency: 1.89507ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:13:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T10:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-31-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-31.ec2.internal
      uid: f3c124a3-73c2-4e59-8985-2a42e9d8e026
    resourceVersion: "69681"
    uid: 049be721-a5fe-444a-a5d6-88d1d3502215
  spec:
    sourcePod: network-check-source-7d88cb55d8-p6nrr
    targetEndpoint: acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T10:32:09Z"
      message: 'load-balancer-api-external: tcp connection to acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.815412ms
      message: 'load-balancer-api-external: tcp connection to acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:20:09Z"
    - latency: 7.482537ms
      message: 'load-balancer-api-external: resolved host name acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:20:09Z"
    - latency: 3.665897ms
      message: 'load-balancer-api-external: tcp connection to acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:19:09Z"
    - latency: 6.517219ms
      message: 'load-balancer-api-external: resolved host name acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:19:09Z"
    - latency: 4.181084ms
      message: 'load-balancer-api-external: tcp connection to acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:18:09Z"
    - latency: 6.69474ms
      message: 'load-balancer-api-external: resolved host name acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:18:09Z"
    - latency: 3.629425ms
      message: 'load-balancer-api-external: tcp connection to acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:17:09Z"
    - latency: 7.649751ms
      message: 'load-balancer-api-external: resolved host name acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:17:09Z"
    - latency: 4.12454ms
      message: 'load-balancer-api-external: tcp connection to acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:16:09Z"
    - latency: 6.361429ms
      message: 'load-balancer-api-external: resolved host name acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:16:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T10:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-31-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-31.ec2.internal
      uid: f3c124a3-73c2-4e59-8985-2a42e9d8e026
    resourceVersion: "69680"
    uid: be318d57-b85c-4e5f-9892-bc8577eb0237
  spec:
    sourcePod: network-check-source-7d88cb55d8-p6nrr
    targetEndpoint: acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T10:32:09Z"
      message: 'load-balancer-api-internal: tcp connection to acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.76763ms
      message: 'load-balancer-api-internal: tcp connection to acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:20:09Z"
    - latency: 7.429985ms
      message: 'load-balancer-api-internal: resolved host name acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:20:09Z"
    - latency: 3.710353ms
      message: 'load-balancer-api-internal: tcp connection to acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:19:09Z"
    - latency: 6.405502ms
      message: 'load-balancer-api-internal: resolved host name acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:19:09Z"
    - latency: 3.860635ms
      message: 'load-balancer-api-internal: tcp connection to acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:18:09Z"
    - latency: 6.617445ms
      message: 'load-balancer-api-internal: resolved host name acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:18:09Z"
    - latency: 3.645712ms
      message: 'load-balancer-api-internal: tcp connection to acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:17:09Z"
    - latency: 7.716936ms
      message: 'load-balancer-api-internal: resolved host name acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:17:09Z"
    - latency: 4.139768ms
      message: 'load-balancer-api-internal: tcp connection to acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:16:09Z"
    - latency: 6.290381ms
      message: 'load-balancer-api-internal: resolved host name acf32ad0b43664a38904205de8557871-9e8eed4939b35210.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:16:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T10:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-31-to-network-check-target-ip-10-0-129-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-31.ec2.internal
      uid: f3c124a3-73c2-4e59-8985-2a42e9d8e026
    resourceVersion: "74309"
    uid: 4af175e6-1900-47b2-9053-9e6a0aa231d3
  spec:
    sourcePod: network-check-source-7d88cb55d8-p6nrr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T10:33:09Z"
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 759.901µs
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:22:09Z"
    - latency: 1.138846ms
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:21:09Z"
    - latency: 817.379µs
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:20:09Z"
    - latency: 907.241µs
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:19:09Z"
    - latency: 930.722µs
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:18:09Z"
    - latency: 1.840215ms
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:17:09Z"
    - latency: 939.943µs
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:16:09Z"
    - latency: 1.065709ms
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:15:09Z"
    - latency: 755.099µs
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:14:09Z"
    - latency: 1.233184ms
      message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:13:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T10:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-31-to-network-check-target-ip-10-0-130-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-31.ec2.internal
      uid: f3c124a3-73c2-4e59-8985-2a42e9d8e026
    resourceVersion: "74312"
    uid: 4331a28e-8607-43d2-9baa-4b0c2db1d3eb
  spec:
    sourcePod: network-check-source-7d88cb55d8-p6nrr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T10:33:09Z"
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.780902ms
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:22:09Z"
    - latency: 2.081284ms
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:21:09Z"
    - latency: 1.872969ms
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:20:09Z"
    - latency: 2.035153ms
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:19:09Z"
    - latency: 1.956699ms
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:18:09Z"
    - latency: 1.615508ms
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:17:09Z"
    - latency: 2.301542ms
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:16:09Z"
    - latency: 2.056086ms
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:15:09Z"
    - latency: 2.442726ms
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:14:09Z"
    - latency: 2.063203ms
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:13:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T10:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-31-to-network-check-target-ip-10-0-131-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-31.ec2.internal
      uid: f3c124a3-73c2-4e59-8985-2a42e9d8e026
    resourceVersion: "74311"
    uid: d849ff2c-e06f-46b0-8c98-9fff75cff884
  spec:
    sourcePod: network-check-source-7d88cb55d8-p6nrr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T10:33:09Z"
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.251671ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:22:09Z"
    - latency: 1.92005ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:21:09Z"
    - latency: 1.911052ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:20:09Z"
    - latency: 1.878121ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:19:09Z"
    - latency: 2.111395ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:18:09Z"
    - latency: 2.228285ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:17:09Z"
    - latency: 2.260934ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:16:09Z"
    - latency: 2.011876ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:15:09Z"
    - latency: 1.904613ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:14:09Z"
    - latency: 2.168312ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:13:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T10:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-31-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-31.ec2.internal
      uid: f3c124a3-73c2-4e59-8985-2a42e9d8e026
    resourceVersion: "69679"
    uid: 2b05caa0-2143-4479-bd6f-01d32324a7ba
  spec:
    sourcePod: network-check-source-7d88cb55d8-p6nrr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T10:32:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 796.752µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:20:09Z"
    - latency: 2.032641ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:20:09Z"
    - latency: 833.882µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:19:09Z"
    - latency: 1.64495ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:19:09Z"
    - latency: 922.192µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:18:09Z"
    - latency: 1.715429ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:18:09Z"
    - latency: 910.343µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:17:09Z"
    - latency: 2.387976ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:17:09Z"
    - latency: 1.086847ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T11:16:09Z"
    - latency: 1.67926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T11:16:09Z"
kind: List
metadata:
  resourceVersion: ""