apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:44:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-5-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-5.ec2.internal
      uid: 1812be9a-5633-4b75-b138-c4f26e28e8f9
    resourceVersion: "46120"
    uid: 27e82640-b354-4495-8029-74030d96e162
  spec:
    sourcePod: network-check-source-dbd9cf844-lbq8q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:51:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.644051ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:12:58Z"
    - latency: 923.099µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:11:58Z"
    - latency: 1.134599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:10:58Z"
    - latency: 1.121746ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:09:58Z"
    - latency: 1.113838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:08:58Z"
    - latency: 1.109788ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:07:58Z"
    - latency: 1.640423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:06:58Z"
    - latency: 919.342µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:05:58Z"
    - latency: 893.311µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:04:58Z"
    - latency: 1.11499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:03:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:44:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-5-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-5.ec2.internal
      uid: 1812be9a-5633-4b75-b138-c4f26e28e8f9
    resourceVersion: "48261"
    uid: 0998b72c-34ef-4483-a263-cfb787175db5
  spec:
    sourcePod: network-check-source-dbd9cf844-lbq8q
    targetEndpoint: ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:50:58Z"
      message: 'load-balancer-api-external: tcp connection to ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.872363ms
      message: 'load-balancer-api-external: tcp connection to ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:14:58Z"
    - latency: 6.690956ms
      message: 'load-balancer-api-external: resolved host name ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:14:58Z"
    - latency: 4.050738ms
      message: 'load-balancer-api-external: tcp connection to ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:13:58Z"
    - latency: 6.842432ms
      message: 'load-balancer-api-external: resolved host name ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:13:58Z"
    - latency: 4.853887ms
      message: 'load-balancer-api-external: tcp connection to ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:12:58Z"
    - latency: 7.103638ms
      message: 'load-balancer-api-external: resolved host name ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:12:58Z"
    - latency: 4.621609ms
      message: 'load-balancer-api-external: tcp connection to ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:11:58Z"
    - latency: 7.532483ms
      message: 'load-balancer-api-external: resolved host name ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:11:58Z"
    - latency: 4.826776ms
      message: 'load-balancer-api-external: tcp connection to ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:10:58Z"
    - latency: 7.014261ms
      message: 'load-balancer-api-external: resolved host name ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:10:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:44:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-5-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-5.ec2.internal
      uid: 1812be9a-5633-4b75-b138-c4f26e28e8f9
    resourceVersion: "48260"
    uid: 20b791bf-24cb-420c-b99b-eac845ad7757
  spec:
    sourcePod: network-check-source-dbd9cf844-lbq8q
    targetEndpoint: ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:50:58Z"
      message: 'load-balancer-api-internal: tcp connection to ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.854668ms
      message: 'load-balancer-api-internal: tcp connection to ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:14:58Z"
    - latency: 6.566333ms
      message: 'load-balancer-api-internal: resolved host name ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:14:58Z"
    - latency: 4.72699ms
      message: 'load-balancer-api-internal: tcp connection to ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:13:58Z"
    - latency: 6.798196ms
      message: 'load-balancer-api-internal: resolved host name ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:13:58Z"
    - latency: 5.476863ms
      message: 'load-balancer-api-internal: tcp connection to ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:12:58Z"
    - latency: 7.054626ms
      message: 'load-balancer-api-internal: resolved host name ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:12:58Z"
    - latency: 4.811162ms
      message: 'load-balancer-api-internal: tcp connection to ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:11:58Z"
    - latency: 7.501289ms
      message: 'load-balancer-api-internal: resolved host name ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:11:58Z"
    - latency: 3.839427ms
      message: 'load-balancer-api-internal: tcp connection to ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:10:58Z"
    - latency: 6.93309ms
      message: 'load-balancer-api-internal: resolved host name ad0cfdc3568f64f4b8a22894cdeb91a6-8b9d2cd28dc3817f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:10:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:44:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-5-to-network-check-target-ip-10-0-131-237
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-5.ec2.internal
      uid: 1812be9a-5633-4b75-b138-c4f26e28e8f9
    resourceVersion: "46119"
    uid: 82763d6f-9191-4092-9d8b-323ff59e9839
  spec:
    sourcePod: network-check-source-dbd9cf844-lbq8q
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:51:58Z"
      message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.311065ms
      message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:12:58Z"
    - latency: 2.387343ms
      message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:11:58Z"
    - latency: 2.439935ms
      message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:10:58Z"
    - latency: 2.601569ms
      message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:09:58Z"
    - latency: 2.350156ms
      message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:08:58Z"
    - latency: 2.253221ms
      message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:07:58Z"
    - latency: 2.538107ms
      message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:06:58Z"
    - latency: 1.991014ms
      message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:05:58Z"
    - latency: 2.114038ms
      message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:04:58Z"
    - latency: 2.188811ms
      message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:03:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:44:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-5-to-network-check-target-ip-10-0-140-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-5.ec2.internal
      uid: 1812be9a-5633-4b75-b138-c4f26e28e8f9
    resourceVersion: "46118"
    uid: aae4b672-89be-4e37-a0cd-395bfc7dcdba
  spec:
    sourcePod: network-check-source-dbd9cf844-lbq8q
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:51:58Z"
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.980404ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:12:58Z"
    - latency: 1.896048ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:11:58Z"
    - latency: 2.099139ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:10:58Z"
    - latency: 1.969108ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:09:58Z"
    - latency: 2.300444ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:08:58Z"
    - latency: 2.176095ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:07:58Z"
    - latency: 1.923428ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:06:58Z"
    - latency: 1.947249ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:05:58Z"
    - latency: 1.905272ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:04:58Z"
    - latency: 1.914549ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:03:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:44:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-5-to-network-check-target-ip-10-0-141-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-5.ec2.internal
      uid: 1812be9a-5633-4b75-b138-c4f26e28e8f9
    resourceVersion: "46117"
    uid: 02ce75a8-297b-4fa6-a79c-7a424634789f
  spec:
    sourcePod: network-check-source-dbd9cf844-lbq8q
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:51:58Z"
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.820814ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:12:58Z"
    - latency: 1.510904ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:11:58Z"
    - latency: 1.130761ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:10:58Z"
    - latency: 1.022135ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:09:58Z"
    - latency: 1.40746ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:08:58Z"
    - latency: 1.401544ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:07:58Z"
    - latency: 1.186484ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:06:58Z"
    - latency: 1.095288ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:05:58Z"
    - latency: 887.366µs
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:04:58Z"
    - latency: 1.255302ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:03:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:44:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-5-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-5.ec2.internal
      uid: 1812be9a-5633-4b75-b138-c4f26e28e8f9
    resourceVersion: "48259"
    uid: 12cf0bfe-28f4-43dc-98c4-ece4e52a91ff
  spec:
    sourcePod: network-check-source-dbd9cf844-lbq8q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:50:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 922.922µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:14:58Z"
    - latency: 1.714679ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:14:58Z"
    - latency: 825.938µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:13:58Z"
    - latency: 1.808115ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:13:58Z"
    - latency: 1.065494ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:12:58Z"
    - latency: 1.854423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:12:58Z"
    - latency: 1.072105ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:11:58Z"
    - latency: 2.139815ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:11:58Z"
    - latency: 1.258434ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:10:58Z"
    - latency: 1.861024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:10:58Z"
kind: List
metadata:
  resourceVersion: ""