apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T22:44:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-134-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-134.ec2.internal
      uid: e25a3ddc-5471-4b6b-9690-1fddc0a0efc1
    resourceVersion: "71441"
    uid: 6167bd86-e9cd-44fb-a60e-6567de9ad9f8
  spec:
    sourcePod: network-check-source-65bdbbff45-hvnsp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T22:51:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.042625ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:33:29Z"
    - latency: 1.010557ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:32:29Z"
    - latency: 882.289µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:31:29Z"
    - latency: 1.195428ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:30:29Z"
    - latency: 1.118162ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:29:29Z"
    - latency: 1.050653ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:28:29Z"
    - latency: 1.391822ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:27:29Z"
    - latency: 1.051179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:26:29Z"
    - latency: 1.79132ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:25:29Z"
    - latency: 1.119809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:24:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T22:44:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-134-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-134.ec2.internal
      uid: e25a3ddc-5471-4b6b-9690-1fddc0a0efc1
    resourceVersion: "76612"
    uid: 53038a11-5f60-42a0-a8b3-970e94a71abc
  spec:
    sourcePod: network-check-source-65bdbbff45-hvnsp
    targetEndpoint: a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T22:50:29Z"
      message: 'load-balancer-api-external: tcp connection to a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.559667ms
      message: 'load-balancer-api-external: tcp connection to a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:38:29Z"
    - latency: 8.154924ms
      message: 'load-balancer-api-external: resolved host name a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:38:29Z"
    - latency: 4.893699ms
      message: 'load-balancer-api-external: tcp connection to a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:37:29Z"
    - latency: 8.519255ms
      message: 'load-balancer-api-external: resolved host name a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:37:29Z"
    - latency: 4.704658ms
      message: 'load-balancer-api-external: tcp connection to a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:36:29Z"
    - latency: 8.746056ms
      message: 'load-balancer-api-external: resolved host name a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:36:29Z"
    - latency: 4.297087ms
      message: 'load-balancer-api-external: tcp connection to a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:35:29Z"
    - latency: 8.366007ms
      message: 'load-balancer-api-external: resolved host name a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:35:29Z"
    - latency: 4.568546ms
      message: 'load-balancer-api-external: tcp connection to a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:34:29Z"
    - latency: 7.961833ms
      message: 'load-balancer-api-external: resolved host name a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:34:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T22:44:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-134-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-134.ec2.internal
      uid: e25a3ddc-5471-4b6b-9690-1fddc0a0efc1
    resourceVersion: "76613"
    uid: 60aa79de-fd0c-4653-b0a6-0facd15edef5
  spec:
    sourcePod: network-check-source-65bdbbff45-hvnsp
    targetEndpoint: a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T22:50:29Z"
      message: 'load-balancer-api-internal: tcp connection to a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.501811ms
      message: 'load-balancer-api-internal: tcp connection to a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:38:29Z"
    - latency: 8.117285ms
      message: 'load-balancer-api-internal: resolved host name a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:38:29Z"
    - latency: 4.886221ms
      message: 'load-balancer-api-internal: tcp connection to a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:37:29Z"
    - latency: 8.566907ms
      message: 'load-balancer-api-internal: resolved host name a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:37:29Z"
    - latency: 5.0079ms
      message: 'load-balancer-api-internal: tcp connection to a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:36:29Z"
    - latency: 8.725342ms
      message: 'load-balancer-api-internal: resolved host name a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:36:29Z"
    - latency: 4.257858ms
      message: 'load-balancer-api-internal: tcp connection to a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:35:29Z"
    - latency: 8.478399ms
      message: 'load-balancer-api-internal: resolved host name a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:35:29Z"
    - latency: 3.651398ms
      message: 'load-balancer-api-internal: tcp connection to a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:34:29Z"
    - latency: 7.926965ms
      message: 'load-balancer-api-internal: resolved host name a335248e1618c474c971a610bbe42e8d-0dd7978f7a0aa215.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:34:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T22:44:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-134-to-network-check-target-ip-10-0-137-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-134.ec2.internal
      uid: e25a3ddc-5471-4b6b-9690-1fddc0a0efc1
    resourceVersion: "71438"
    uid: 8854be64-4b26-4b24-a968-9fb97e038cbb
  spec:
    sourcePod: network-check-source-65bdbbff45-hvnsp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T22:51:29Z"
      message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.017903ms
      message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:33:29Z"
    - latency: 892.779µs
      message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:32:29Z"
    - latency: 1.252602ms
      message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:31:29Z"
    - latency: 1.173441ms
      message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:30:29Z"
    - latency: 1.013183ms
      message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:29:29Z"
    - latency: 1.094137ms
      message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:28:29Z"
    - latency: 1.068717ms
      message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:27:29Z"
    - latency: 1.255773ms
      message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:26:29Z"
    - latency: 1.852562ms
      message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:25:29Z"
    - latency: 1.58431ms
      message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:24:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T22:44:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-134-to-network-check-target-ip-10-0-142-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-134.ec2.internal
      uid: e25a3ddc-5471-4b6b-9690-1fddc0a0efc1
    resourceVersion: "71440"
    uid: 4ffbe499-45ad-4bf6-bd96-716e87992f82
  spec:
    sourcePod: network-check-source-65bdbbff45-hvnsp
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T22:51:29Z"
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.435441ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:33:29Z"
    - latency: 2.370524ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:32:29Z"
    - latency: 2.66298ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:31:29Z"
    - latency: 2.64544ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:30:29Z"
    - latency: 2.843053ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:29:29Z"
    - latency: 2.665948ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:28:29Z"
    - latency: 2.657084ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:27:29Z"
    - latency: 2.594106ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:26:29Z"
    - latency: 2.816694ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:25:29Z"
    - latency: 2.532164ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:24:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T22:44:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-134-to-network-check-target-ip-10-0-143-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-134.ec2.internal
      uid: e25a3ddc-5471-4b6b-9690-1fddc0a0efc1
    resourceVersion: "71439"
    uid: e82b0a8a-fbe3-4bcb-8de8-51366d89e2a5
  spec:
    sourcePod: network-check-source-65bdbbff45-hvnsp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T22:51:29Z"
      message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.461078ms
      message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:33:29Z"
    - latency: 2.065417ms
      message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:32:29Z"
    - latency: 2.399238ms
      message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:31:29Z"
    - latency: 2.486791ms
      message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:30:29Z"
    - latency: 2.644966ms
      message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:29:29Z"
    - latency: 2.300045ms
      message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:28:29Z"
    - latency: 2.474291ms
      message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:27:29Z"
    - latency: 2.463044ms
      message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:26:29Z"
    - latency: 2.839309ms
      message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:25:29Z"
    - latency: 2.566851ms
      message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:24:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T22:44:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-134-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-134.ec2.internal
      uid: e25a3ddc-5471-4b6b-9690-1fddc0a0efc1
    resourceVersion: "76611"
    uid: aa518422-af93-4acc-b9df-7d91fbd3e496
  spec:
    sourcePod: network-check-source-65bdbbff45-hvnsp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T22:50:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 851.969µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:38:29Z"
    - latency: 2.838001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:38:29Z"
    - latency: 939.056µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:37:29Z"
    - latency: 1.756341ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:37:29Z"
    - latency: 800.058µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:36:29Z"
    - latency: 1.651875ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:36:29Z"
    - latency: 1.092945ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:35:29Z"
    - latency: 1.622192ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:35:29Z"
    - latency: 1.059107ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T23:34:29Z"
    - latency: 1.705863ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T23:34:29Z"
kind: List
metadata:
  resourceVersion: ""