apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-234-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-234.ec2.internal
      uid: b4cc2e3d-439d-4577-815e-e56ce3abec8a
    resourceVersion: "68871"
    uid: 55e800cd-457c-48d7-83f2-8b98ba72ead3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8dssn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T05:00:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 906.044µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:42:14Z"
    - latency: 1.543593ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:41:14Z"
    - latency: 871.14µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:40:14Z"
    - latency: 1.022667ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:39:14Z"
    - latency: 979.993µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:38:14Z"
    - latency: 918.21µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:37:14Z"
    - latency: 1.077314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:36:14Z"
    - latency: 989.799µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:35:14Z"
    - latency: 1.255605ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:34:14Z"
    - latency: 1.067728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:33:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-234-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-234.ec2.internal
      uid: b4cc2e3d-439d-4577-815e-e56ce3abec8a
    resourceVersion: "67894"
    uid: 24d13303-4bf0-4e01-bf18-b9f2418d3464
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8dssn
    targetEndpoint: a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T04:59:14Z"
      message: 'load-balancer-api-external: tcp connection to a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.248512ms
      message: 'load-balancer-api-external: tcp connection to a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:41:14Z"
    - latency: 10.484862ms
      message: 'load-balancer-api-external: resolved host name a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:41:14Z"
    - latency: 4.924563ms
      message: 'load-balancer-api-external: tcp connection to a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:40:14Z"
    - latency: 11.827196ms
      message: 'load-balancer-api-external: resolved host name a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:40:14Z"
    - latency: 4.078458ms
      message: 'load-balancer-api-external: tcp connection to a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:39:14Z"
    - latency: 8.695401ms
      message: 'load-balancer-api-external: resolved host name a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:39:14Z"
    - latency: 9.593986ms
      message: 'load-balancer-api-external: tcp connection to a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:38:14Z"
    - latency: 12.203053ms
      message: 'load-balancer-api-external: resolved host name a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:38:14Z"
    - latency: 4.046452ms
      message: 'load-balancer-api-external: tcp connection to a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:37:14Z"
    - latency: 11.59111ms
      message: 'load-balancer-api-external: resolved host name a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:37:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-234-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-234.ec2.internal
      uid: b4cc2e3d-439d-4577-815e-e56ce3abec8a
    resourceVersion: "67893"
    uid: 7d97cb21-0739-413c-92cc-ecb0ccff6188
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8dssn
    targetEndpoint: a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T04:59:14Z"
      message: 'load-balancer-api-internal: tcp connection to a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.234477ms
      message: 'load-balancer-api-internal: tcp connection to a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:41:14Z"
    - latency: 10.555442ms
      message: 'load-balancer-api-internal: resolved host name a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:41:14Z"
    - latency: 4.923713ms
      message: 'load-balancer-api-internal: tcp connection to a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:40:14Z"
    - latency: 11.741531ms
      message: 'load-balancer-api-internal: resolved host name a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:40:14Z"
    - latency: 4.339549ms
      message: 'load-balancer-api-internal: tcp connection to a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:39:14Z"
    - latency: 8.800908ms
      message: 'load-balancer-api-internal: resolved host name a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:39:14Z"
    - latency: 5.904564ms
      message: 'load-balancer-api-internal: tcp connection to a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:38:14Z"
    - latency: 12.065064ms
      message: 'load-balancer-api-internal: resolved host name a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:38:14Z"
    - latency: 5.456039ms
      message: 'load-balancer-api-internal: tcp connection to a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:37:14Z"
    - latency: 11.632887ms
      message: 'load-balancer-api-internal: resolved host name a830e207cebef4fc1ac0f2e05941e639-3668e691e8e022bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:37:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-234-to-network-check-target-ip-10-0-129-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-234.ec2.internal
      uid: b4cc2e3d-439d-4577-815e-e56ce3abec8a
    resourceVersion: "68868"
    uid: 59b40bb3-0654-4789-8bd3-1fe0a941b7cb
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8dssn
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T05:00:14Z"
      message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 814.016µs
      message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:42:14Z"
    - latency: 935.924µs
      message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:41:14Z"
    - latency: 930.886µs
      message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:40:14Z"
    - latency: 1.012095ms
      message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:39:14Z"
    - latency: 930.218µs
      message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:38:14Z"
    - latency: 1.164307ms
      message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:37:14Z"
    - latency: 1.27719ms
      message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:36:14Z"
    - latency: 1.067317ms
      message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:35:14Z"
    - latency: 1.009224ms
      message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:34:14Z"
    - latency: 1.751605ms
      message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:33:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-234-to-network-check-target-ip-10-0-132-19
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-234.ec2.internal
      uid: b4cc2e3d-439d-4577-815e-e56ce3abec8a
    resourceVersion: "68869"
    uid: 2b433497-0c55-429e-912a-b1e2ae3db2e1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8dssn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T05:00:14Z"
      message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.816649ms
      message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:42:14Z"
    - latency: 1.901241ms
      message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:41:14Z"
    - latency: 1.830206ms
      message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:40:14Z"
    - latency: 1.786115ms
      message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:39:14Z"
    - latency: 1.993661ms
      message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:38:14Z"
    - latency: 2.249367ms
      message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:37:14Z"
    - latency: 2.405384ms
      message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:36:14Z"
    - latency: 2.129435ms
      message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:35:14Z"
    - latency: 2.447652ms
      message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:34:14Z"
    - latency: 2.120625ms
      message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:33:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-234-to-network-check-target-ip-10-0-140-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-234.ec2.internal
      uid: b4cc2e3d-439d-4577-815e-e56ce3abec8a
    resourceVersion: "68870"
    uid: 0b90e85f-c94c-47fe-b907-e221d489c27b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8dssn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T05:00:14Z"
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.260507ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:42:14Z"
    - latency: 2.311447ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:41:14Z"
    - latency: 2.082233ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:40:14Z"
    - latency: 2.149484ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:39:14Z"
    - latency: 2.294953ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:38:14Z"
    - latency: 2.28292ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:37:14Z"
    - latency: 2.289614ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:36:14Z"
    - latency: 2.29578ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:35:14Z"
    - latency: 2.347979ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:34:14Z"
    - latency: 2.623043ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:33:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T04:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-234-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-234.ec2.internal
      uid: b4cc2e3d-439d-4577-815e-e56ce3abec8a
    resourceVersion: "67892"
    uid: 8ab3d12d-6740-4eb3-85cd-26779ed59ca8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8dssn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T04:59:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.215358ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:41:14Z"
    - latency: 2.133087ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:41:14Z"
    - latency: 1.044133ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:40:14Z"
    - latency: 1.985935ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:40:14Z"
    - latency: 887.192µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:39:14Z"
    - latency: 1.650471ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:39:14Z"
    - latency: 911.306µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:38:14Z"
    - latency: 1.76403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:38:14Z"
    - latency: 1.1627ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T05:37:14Z"
    - latency: 1.889299ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T05:37:14Z"
kind: List
metadata:
  resourceVersion: ""