apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:45:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-14-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-14.ec2.internal
      uid: 5824ef69-8394-4829-bde8-61dd93d9ea2b
    resourceVersion: "39853"
    uid: 3f70c2de-33ec-49d1-a2c8-9cedf54064d1
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9gvb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:52:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.050695ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:39Z"
    - latency: 950.998µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:39Z"
    - latency: 1.060079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:39Z"
    - latency: 1.214544ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:31:39Z"
    - latency: 919.463µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:30:39Z"
    - latency: 1.157777ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:39Z"
    - latency: 1.041641ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:39Z"
    - latency: 805.368µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:39Z"
    - latency: 1.368756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:39Z"
    - latency: 1.183605ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:45:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-14-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-14.ec2.internal
      uid: 5824ef69-8394-4829-bde8-61dd93d9ea2b
    resourceVersion: "39304"
    uid: 64dc66e9-20ad-4734-b082-9010db679e63
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9gvb
    targetEndpoint: adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:51:39Z"
      message: 'load-balancer-api-external: tcp connection to adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.736ms
      message: 'load-balancer-api-external: tcp connection to adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:39Z"
    - latency: 8.025186ms
      message: 'load-balancer-api-external: resolved host name adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:33:39Z"
    - latency: 6.772558ms
      message: 'load-balancer-api-external: tcp connection to adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:39Z"
    - latency: 6.439357ms
      message: 'load-balancer-api-external: resolved host name adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:32:39Z"
    - latency: 4.853971ms
      message: 'load-balancer-api-external: tcp connection to adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:31:39Z"
    - latency: 7.491902ms
      message: 'load-balancer-api-external: resolved host name adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:31:39Z"
    - latency: 5.173091ms
      message: 'load-balancer-api-external: tcp connection to adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:30:39Z"
    - latency: 6.609932ms
      message: 'load-balancer-api-external: resolved host name adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:30:39Z"
    - latency: 4.185785ms
      message: 'load-balancer-api-external: tcp connection to adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:39Z"
    - latency: 7.782301ms
      message: 'load-balancer-api-external: resolved host name adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:29:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:45:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-14-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-14.ec2.internal
      uid: 5824ef69-8394-4829-bde8-61dd93d9ea2b
    resourceVersion: "39303"
    uid: 660439a8-1ecc-42d6-b391-d276c4717384
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9gvb
    targetEndpoint: adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:51:39Z"
      message: 'load-balancer-api-internal: tcp connection to adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.916555ms
      message: 'load-balancer-api-internal: tcp connection to adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:39Z"
    - latency: 7.960434ms
      message: 'load-balancer-api-internal: resolved host name adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:33:39Z"
    - latency: 6.765003ms
      message: 'load-balancer-api-internal: tcp connection to adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:39Z"
    - latency: 6.499483ms
      message: 'load-balancer-api-internal: resolved host name adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:32:39Z"
    - latency: 4.877961ms
      message: 'load-balancer-api-internal: tcp connection to adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:31:39Z"
    - latency: 7.52079ms
      message: 'load-balancer-api-internal: resolved host name adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:31:39Z"
    - latency: 5.277835ms
      message: 'load-balancer-api-internal: tcp connection to adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:30:39Z"
    - latency: 6.662174ms
      message: 'load-balancer-api-internal: resolved host name adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:30:39Z"
    - latency: 4.633412ms
      message: 'load-balancer-api-internal: tcp connection to adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:39Z"
    - latency: 7.691586ms
      message: 'load-balancer-api-internal: resolved host name adbf58c138a7244b6950cb6d279df4fb-3282c65938a9656c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:29:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:45:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-14-to-network-check-target-ip-10-0-131-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-14.ec2.internal
      uid: 5824ef69-8394-4829-bde8-61dd93d9ea2b
    resourceVersion: "39850"
    uid: 1d2b406a-562c-44ed-9d79-741b95dd8e52
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9gvb
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:52:39Z"
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.075973ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:39Z"
    - latency: 884.259µs
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:39Z"
    - latency: 808.557µs
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:39Z"
    - latency: 1.731186ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:31:39Z"
    - latency: 1.444855ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:30:39Z"
    - latency: 889.335µs
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:39Z"
    - latency: 942.394µs
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:39Z"
    - latency: 885.387µs
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:39Z"
    - latency: 974.496µs
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:39Z"
    - latency: 942.092µs
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:45:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-14-to-network-check-target-ip-10-0-131-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-14.ec2.internal
      uid: 5824ef69-8394-4829-bde8-61dd93d9ea2b
    resourceVersion: "39851"
    uid: 498a430d-0597-4af6-b923-de7676d2bc3c
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9gvb
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:52:39Z"
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.314076ms
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:39Z"
    - latency: 2.308831ms
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:39Z"
    - latency: 2.208461ms
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:39Z"
    - latency: 2.322194ms
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:31:39Z"
    - latency: 2.189596ms
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:30:39Z"
    - latency: 2.417831ms
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:39Z"
    - latency: 2.407374ms
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:39Z"
    - latency: 2.258292ms
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:39Z"
    - latency: 2.123604ms
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:39Z"
    - latency: 2.358222ms
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:45:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-14-to-network-check-target-ip-10-0-138-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-14.ec2.internal
      uid: 5824ef69-8394-4829-bde8-61dd93d9ea2b
    resourceVersion: "39852"
    uid: c8b64cca-26c7-4512-a6db-955928145b1c
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9gvb
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:52:39Z"
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.627584ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:39Z"
    - latency: 1.878751ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:39Z"
    - latency: 1.821293ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:39Z"
    - latency: 2.620397ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:31:39Z"
    - latency: 1.854423ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:30:39Z"
    - latency: 2.261542ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:39Z"
    - latency: 1.712693ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:39Z"
    - latency: 2.227769ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:39Z"
    - latency: 1.893439ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:39Z"
    - latency: 2.302325ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:45:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-14-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-14.ec2.internal
      uid: 5824ef69-8394-4829-bde8-61dd93d9ea2b
    resourceVersion: "39302"
    uid: 13c9798b-1a94-4686-9122-5aa906f54ec7
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9gvb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:51:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.603µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:39Z"
    - latency: 1.876977ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:33:39Z"
    - latency: 1.027485ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:39Z"
    - latency: 1.652139ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:32:39Z"
    - latency: 970.695µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:31:39Z"
    - latency: 1.909848ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:31:39Z"
    - latency: 1.340001ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:30:39Z"
    - latency: 1.832311ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:30:39Z"
    - latency: 763.771µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:39Z"
    - latency: 1.728675ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:29:39Z"
kind: List
metadata:
  resourceVersion: ""