apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-199-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-199.ec2.internal
      uid: 33b6a92f-1c71-4022-9991-67ef18addb22
    resourceVersion: "57147"
    uid: 276b5bb5-6635-4f54-a837-a0e8087dbcf8
  spec:
    sourcePod: network-check-source-869dcfcdcd-gp2rz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:35:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.646728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:03:00Z"
    - latency: 1.118069ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:02:00Z"
    - latency: 1.247793ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:01:00Z"
    - latency: 2.091902ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:00:00Z"
    - latency: 1.251606ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:59:00Z"
    - latency: 1.228521ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:58:00Z"
    - latency: 868.658µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:57:00Z"
    - latency: 1.321068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:56:00Z"
    - latency: 1.023934ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:55:00Z"
    - latency: 954.562µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:54:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-199-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-199.ec2.internal
      uid: 33b6a92f-1c71-4022-9991-67ef18addb22
    resourceVersion: "58114"
    uid: 61a78879-3d3e-44d5-8dff-4f36f082d786
  spec:
    sourcePod: network-check-source-869dcfcdcd-gp2rz
    targetEndpoint: a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:34:00Z"
      message: 'load-balancer-api-external: tcp connection to a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.322384ms
      message: 'load-balancer-api-external: tcp connection to a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:04:00Z"
    - latency: 8.609433ms
      message: 'load-balancer-api-external: resolved host name a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:04:00Z"
    - latency: 5.295335ms
      message: 'load-balancer-api-external: tcp connection to a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:03:00Z"
    - latency: 7.0575ms
      message: 'load-balancer-api-external: resolved host name a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:03:00Z"
    - latency: 4.735079ms
      message: 'load-balancer-api-external: tcp connection to a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:02:00Z"
    - latency: 7.686625ms
      message: 'load-balancer-api-external: resolved host name a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:02:00Z"
    - latency: 4.154924ms
      message: 'load-balancer-api-external: tcp connection to a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:01:00Z"
    - latency: 7.012317ms
      message: 'load-balancer-api-external: resolved host name a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:01:00Z"
    - latency: 3.492631ms
      message: 'load-balancer-api-external: tcp connection to a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:00:00Z"
    - latency: 8.405957ms
      message: 'load-balancer-api-external: resolved host name a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:00:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-199-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-199.ec2.internal
      uid: 33b6a92f-1c71-4022-9991-67ef18addb22
    resourceVersion: "58113"
    uid: 065e7912-0a93-4e0e-9522-12ec925b348f
  spec:
    sourcePod: network-check-source-869dcfcdcd-gp2rz
    targetEndpoint: a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:34:00Z"
      message: 'load-balancer-api-internal: tcp connection to a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.217922ms
      message: 'load-balancer-api-internal: tcp connection to a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:04:00Z"
    - latency: 8.563824ms
      message: 'load-balancer-api-internal: resolved host name a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:04:00Z"
    - latency: 4.117369ms
      message: 'load-balancer-api-internal: tcp connection to a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:03:00Z"
    - latency: 7.111676ms
      message: 'load-balancer-api-internal: resolved host name a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:03:00Z"
    - latency: 4.20108ms
      message: 'load-balancer-api-internal: tcp connection to a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:02:00Z"
    - latency: 7.616721ms
      message: 'load-balancer-api-internal: resolved host name a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:02:00Z"
    - latency: 5.439912ms
      message: 'load-balancer-api-internal: tcp connection to a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:01:00Z"
    - latency: 7.188477ms
      message: 'load-balancer-api-internal: resolved host name a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:01:00Z"
    - latency: 3.488757ms
      message: 'load-balancer-api-internal: tcp connection to a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:00:00Z"
    - latency: 8.474052ms
      message: 'load-balancer-api-internal: resolved host name a4a657758600b4d4184c315671fa2a4a-6e60a0fb905684c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:00:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-199-to-network-check-target-ip-10-0-128-199
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-199.ec2.internal
      uid: 33b6a92f-1c71-4022-9991-67ef18addb22
    resourceVersion: "57144"
    uid: 43d553a9-57ad-4bc0-ac30-9e6830fc3366
  spec:
    sourcePod: network-check-source-869dcfcdcd-gp2rz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:35:00Z"
      message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.197819ms
      message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:03:00Z"
    - latency: 1.409771ms
      message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:02:00Z"
    - latency: 1.061335ms
      message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:01:00Z"
    - latency: 2.055244ms
      message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:00:00Z"
    - latency: 1.008037ms
      message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:59:00Z"
    - latency: 1.007159ms
      message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:58:00Z"
    - latency: 964.296µs
      message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:57:00Z"
    - latency: 968.302µs
      message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:56:00Z"
    - latency: 989.236µs
      message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:55:00Z"
    - latency: 1.422005ms
      message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:54:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-199-to-network-check-target-ip-10-0-136-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-199.ec2.internal
      uid: 33b6a92f-1c71-4022-9991-67ef18addb22
    resourceVersion: "57146"
    uid: 7c003c95-8e5b-44c7-bf8c-b2c8ba3e261a
  spec:
    sourcePod: network-check-source-869dcfcdcd-gp2rz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:35:00Z"
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.03672ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:03:00Z"
    - latency: 2.150321ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:02:00Z"
    - latency: 2.159526ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:01:00Z"
    - latency: 2.058022ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:00:00Z"
    - latency: 1.874428ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:59:00Z"
    - latency: 2.136878ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:58:00Z"
    - latency: 1.651125ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:57:00Z"
    - latency: 2.111752ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:56:00Z"
    - latency: 1.772225ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:55:00Z"
    - latency: 1.856605ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:54:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-199-to-network-check-target-ip-10-0-142-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-199.ec2.internal
      uid: 33b6a92f-1c71-4022-9991-67ef18addb22
    resourceVersion: "57145"
    uid: e982f234-d0b5-40d2-933f-6b4884333cad
  spec:
    sourcePod: network-check-source-869dcfcdcd-gp2rz
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:35:00Z"
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.081034ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:03:00Z"
    - latency: 2.189043ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:02:00Z"
    - latency: 2.165292ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:01:00Z"
    - latency: 2.227655ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:00:00Z"
    - latency: 2.154958ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:59:00Z"
    - latency: 2.47337ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:58:00Z"
    - latency: 2.039087ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:57:00Z"
    - latency: 2.319543ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:56:00Z"
    - latency: 1.976192ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:55:00Z"
    - latency: 2.043238ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:54:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-199-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-199.ec2.internal
      uid: 33b6a92f-1c71-4022-9991-67ef18addb22
    resourceVersion: "58112"
    uid: 004005ac-db3b-4d52-a59e-8991bf9b7e3b
  spec:
    sourcePod: network-check-source-869dcfcdcd-gp2rz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:34:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.299959ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:04:00Z"
    - latency: 1.728736ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:04:00Z"
    - latency: 1.184124ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:03:00Z"
    - latency: 1.949285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:03:00Z"
    - latency: 891.54µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:02:00Z"
    - latency: 1.951343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:02:00Z"
    - latency: 1.098086ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:01:00Z"
    - latency: 1.776612ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:01:00Z"
    - latency: 1.263099ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:00:00Z"
    - latency: 2.126924ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:00:00Z"
kind: List
metadata:
  resourceVersion: ""