apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 38893acf-0386-44d5-ada1-c622e7ef05d4
    resourceVersion: "68987"
    uid: bf6cc431-6755-4a32-a70d-efdcc0956b7a
  spec:
    sourcePod: network-check-source-6f8b768455-5wttx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T05:00:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 882.465µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:28:13Z"
    - latency: 1.259511ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:27:13Z"
    - latency: 1.520248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:26:13Z"
    - latency: 1.261097ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:25:13Z"
    - latency: 1.482497ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:24:13Z"
    - latency: 1.207102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:23:13Z"
    - latency: 1.506395ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:22:13Z"
    - latency: 1.411767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:21:13Z"
    - latency: 996.033µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:20:13Z"
    - latency: 1.03021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:19:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 38893acf-0386-44d5-ada1-c622e7ef05d4
    resourceVersion: "69919"
    uid: 66d9452b-686a-4ae2-b64d-c24f59d9eb3f
  spec:
    sourcePod: network-check-source-6f8b768455-5wttx
    targetEndpoint: ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T04:59:13Z"
      message: 'load-balancer-api-external: tcp connection to ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.141397ms
      message: 'load-balancer-api-external: tcp connection to ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:29:13Z"
    - latency: 8.188512ms
      message: 'load-balancer-api-external: resolved host name ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:29:13Z"
    - latency: 5.023945ms
      message: 'load-balancer-api-external: tcp connection to ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:28:13Z"
    - latency: 8.427523ms
      message: 'load-balancer-api-external: resolved host name ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:28:13Z"
    - latency: 4.373789ms
      message: 'load-balancer-api-external: tcp connection to ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:27:13Z"
    - latency: 6.921513ms
      message: 'load-balancer-api-external: resolved host name ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:27:13Z"
    - latency: 3.500428ms
      message: 'load-balancer-api-external: tcp connection to ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:26:13Z"
    - latency: 9.302199ms
      message: 'load-balancer-api-external: resolved host name ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:26:13Z"
    - latency: 4.67253ms
      message: 'load-balancer-api-external: tcp connection to ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:25:13Z"
    - latency: 8.002299ms
      message: 'load-balancer-api-external: resolved host name ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:25:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 38893acf-0386-44d5-ada1-c622e7ef05d4
    resourceVersion: "69918"
    uid: ee1dc586-df48-4b17-9bcf-274e9f29db29
  spec:
    sourcePod: network-check-source-6f8b768455-5wttx
    targetEndpoint: ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T04:59:13Z"
      message: 'load-balancer-api-internal: tcp connection to ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.909296ms
      message: 'load-balancer-api-internal: tcp connection to ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:29:13Z"
    - latency: 8.247925ms
      message: 'load-balancer-api-internal: resolved host name ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:29:13Z"
    - latency: 5.026438ms
      message: 'load-balancer-api-internal: tcp connection to ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:28:13Z"
    - latency: 8.491753ms
      message: 'load-balancer-api-internal: resolved host name ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:28:13Z"
    - latency: 4.395588ms
      message: 'load-balancer-api-internal: tcp connection to ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:27:13Z"
    - latency: 6.832422ms
      message: 'load-balancer-api-internal: resolved host name ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:27:13Z"
    - latency: 3.545548ms
      message: 'load-balancer-api-internal: tcp connection to ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:26:13Z"
    - latency: 9.272172ms
      message: 'load-balancer-api-internal: resolved host name ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:26:13Z"
    - latency: 4.688331ms
      message: 'load-balancer-api-internal: tcp connection to ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:25:13Z"
    - latency: 8.052363ms
      message: 'load-balancer-api-internal: resolved host name ac269d06bd3e94e189e04a54fc692bf8-4dac23c0c8974564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:25:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-network-check-target-ip-10-0-133-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 38893acf-0386-44d5-ada1-c622e7ef05d4
    resourceVersion: "68984"
    uid: e7e4057b-0149-4f97-861f-6cbba2163b43
  spec:
    sourcePod: network-check-source-6f8b768455-5wttx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T05:00:13Z"
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.188844ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:28:13Z"
    - latency: 2.328141ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:27:13Z"
    - latency: 2.483918ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:26:13Z"
    - latency: 2.243593ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:25:13Z"
    - latency: 1.929744ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:24:13Z"
    - latency: 2.425717ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:23:13Z"
    - latency: 2.427672ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:22:13Z"
    - latency: 2.53958ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:21:13Z"
    - latency: 2.136175ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:20:13Z"
    - latency: 2.384399ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:19:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-network-check-target-ip-10-0-134-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 38893acf-0386-44d5-ada1-c622e7ef05d4
    resourceVersion: "68985"
    uid: 1b3340d1-e936-4aba-aca0-02bafd925aed
  spec:
    sourcePod: network-check-source-6f8b768455-5wttx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T05:00:13Z"
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.04633ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:28:13Z"
    - latency: 1.941756ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:27:13Z"
    - latency: 1.887365ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:26:13Z"
    - latency: 1.996172ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:25:13Z"
    - latency: 2.326868ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:24:13Z"
    - latency: 2.018874ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:23:13Z"
    - latency: 1.817999ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:22:13Z"
    - latency: 1.909102ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:21:13Z"
    - latency: 1.882998ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:20:13Z"
    - latency: 2.036893ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:19:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-network-check-target-ip-10-0-142-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 38893acf-0386-44d5-ada1-c622e7ef05d4
    resourceVersion: "68986"
    uid: 676c7d80-a64b-4bb3-ab32-37872fb7a69c
  spec:
    sourcePod: network-check-source-6f8b768455-5wttx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T05:00:13Z"
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.280611ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:28:13Z"
    - latency: 1.108126ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:27:13Z"
    - latency: 1.78083ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:26:13Z"
    - latency: 872.405µs
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:25:13Z"
    - latency: 1.739255ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:24:13Z"
    - latency: 1.532908ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:23:13Z"
    - latency: 1.02464ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:22:13Z"
    - latency: 1.217277ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:21:13Z"
    - latency: 1.223886ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:20:13Z"
    - latency: 1.132269ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:19:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 38893acf-0386-44d5-ada1-c622e7ef05d4
    resourceVersion: "69917"
    uid: 3416f5f3-6795-442b-a550-fffa96376525
  spec:
    sourcePod: network-check-source-6f8b768455-5wttx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T04:59:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.163561ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:29:13Z"
    - latency: 1.667249ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:29:13Z"
    - latency: 881.602µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:28:13Z"
    - latency: 2.126016ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:28:13Z"
    - latency: 1.25459ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:27:13Z"
    - latency: 1.734318ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:27:13Z"
    - latency: 929.485µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:26:13Z"
    - latency: 2.53011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:26:13Z"
    - latency: 1.000747ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T05:25:13Z"
    - latency: 1.782527ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T05:25:13Z"
kind: List
metadata:
  resourceVersion: ""