apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:06:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: 0f2f86fa-4334-4266-a0b7-1612aae5d911
    resourceVersion: "54599"
    uid: 1873ab42-a113-4640-a5e0-10051f55be1e
  spec:
    sourcePod: network-check-source-685456655f-c6cvr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T21:13:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.10493ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:34:16Z"
    - latency: 1.348421ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:33:16Z"
    - latency: 940.846µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:32:16Z"
    - latency: 878.311µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:31:16Z"
    - latency: 1.015091ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:30:16Z"
    - latency: 1.049006ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:29:16Z"
    - latency: 1.070391ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:28:16Z"
    - latency: 1.317372ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:27:16Z"
    - latency: 1.198445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:26:16Z"
    - latency: 1.111003ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:06:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: 0f2f86fa-4334-4266-a0b7-1612aae5d911
    resourceVersion: "56298"
    uid: 123a2fd0-7ea8-4566-8e5c-6ddb5f909327
  spec:
    sourcePod: network-check-source-685456655f-c6cvr
    targetEndpoint: a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T21:12:16Z"
      message: 'load-balancer-api-external: tcp connection to a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.983369ms
      message: 'load-balancer-api-external: tcp connection to a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:36:16Z"
    - latency: 7.651612ms
      message: 'load-balancer-api-external: resolved host name a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:36:16Z"
    - latency: 7.70378ms
      message: 'load-balancer-api-external: tcp connection to a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:35:16Z"
    - latency: 8.249528ms
      message: 'load-balancer-api-external: resolved host name a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:35:16Z"
    - latency: 3.428617ms
      message: 'load-balancer-api-external: tcp connection to a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:34:16Z"
    - latency: 8.528314ms
      message: 'load-balancer-api-external: resolved host name a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:34:16Z"
    - latency: 3.28172ms
      message: 'load-balancer-api-external: tcp connection to a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:33:16Z"
    - latency: 8.599067ms
      message: 'load-balancer-api-external: resolved host name a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:33:16Z"
    - latency: 4.965101ms
      message: 'load-balancer-api-external: tcp connection to a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:32:16Z"
    - latency: 8.359594ms
      message: 'load-balancer-api-external: resolved host name a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:32:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:06:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: 0f2f86fa-4334-4266-a0b7-1612aae5d911
    resourceVersion: "56299"
    uid: 4688c147-dea0-4f45-9513-5440dbb2c4f7
  spec:
    sourcePod: network-check-source-685456655f-c6cvr
    targetEndpoint: a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T21:12:16Z"
      message: 'load-balancer-api-internal: tcp connection to a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.678865ms
      message: 'load-balancer-api-internal: tcp connection to a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:36:16Z"
    - latency: 7.673275ms
      message: 'load-balancer-api-internal: resolved host name a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:36:16Z"
    - latency: 5.344851ms
      message: 'load-balancer-api-internal: tcp connection to a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:35:16Z"
    - latency: 8.275492ms
      message: 'load-balancer-api-internal: resolved host name a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:35:16Z"
    - latency: 3.396382ms
      message: 'load-balancer-api-internal: tcp connection to a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:34:16Z"
    - latency: 8.562987ms
      message: 'load-balancer-api-internal: resolved host name a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:34:16Z"
    - latency: 3.323631ms
      message: 'load-balancer-api-internal: tcp connection to a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:33:16Z"
    - latency: 8.662425ms
      message: 'load-balancer-api-internal: resolved host name a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:33:16Z"
    - latency: 5.00208ms
      message: 'load-balancer-api-internal: tcp connection to a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:32:16Z"
    - latency: 8.406128ms
      message: 'load-balancer-api-internal: resolved host name a7a3d4ac02d00499a8168c621f4ac68a-1f3da447290f2f68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:32:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:06:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-network-check-target-ip-10-0-128-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: 0f2f86fa-4334-4266-a0b7-1612aae5d911
    resourceVersion: "54596"
    uid: da28fa4b-f75a-47ec-946a-84550334fe36
  spec:
    sourcePod: network-check-source-685456655f-c6cvr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T21:13:16Z"
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.080395ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:34:16Z"
    - latency: 1.977505ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:33:16Z"
    - latency: 1.950963ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:32:16Z"
    - latency: 1.799796ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:31:16Z"
    - latency: 2.496088ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:30:16Z"
    - latency: 1.807054ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:29:16Z"
    - latency: 2.049192ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:28:16Z"
    - latency: 2.213868ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:27:16Z"
    - latency: 1.927939ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:26:16Z"
    - latency: 1.95964ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:06:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-network-check-target-ip-10-0-136-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: 0f2f86fa-4334-4266-a0b7-1612aae5d911
    resourceVersion: "54595"
    uid: b2e91599-4a23-49a7-936a-9cfb341773bc
  spec:
    sourcePod: network-check-source-685456655f-c6cvr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T21:13:16Z"
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.352865ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:34:16Z"
    - latency: 942.706µs
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:33:16Z"
    - latency: 823.71µs
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:32:16Z"
    - latency: 934.949µs
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:31:16Z"
    - latency: 1.47845ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:30:16Z"
    - latency: 895.366µs
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:29:16Z"
    - latency: 1.55714ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:28:16Z"
    - latency: 948.399µs
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:27:16Z"
    - latency: 936.79µs
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:26:16Z"
    - latency: 945.572µs
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:06:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-network-check-target-ip-10-0-143-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: 0f2f86fa-4334-4266-a0b7-1612aae5d911
    resourceVersion: "54598"
    uid: c2f15e48-5730-4443-8240-9644194d5ed8
  spec:
    sourcePod: network-check-source-685456655f-c6cvr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T21:13:16Z"
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.685782ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:34:16Z"
    - latency: 3.05216ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:33:16Z"
    - latency: 2.52657ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:32:16Z"
    - latency: 2.344631ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:31:16Z"
    - latency: 2.511863ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:30:16Z"
    - latency: 2.114098ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:29:16Z"
    - latency: 2.382191ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:28:16Z"
    - latency: 2.515196ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:27:16Z"
    - latency: 2.534173ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:26:16Z"
    - latency: 2.195363ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:06:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: 0f2f86fa-4334-4266-a0b7-1612aae5d911
    resourceVersion: "56297"
    uid: eae822f3-1da7-4083-9134-7c56c5ec9c46
  spec:
    sourcePod: network-check-source-685456655f-c6cvr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T21:12:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.33055ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:36:16Z"
    - latency: 1.934946ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:36:16Z"
    - latency: 863.91µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:35:16Z"
    - latency: 1.815911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:35:16Z"
    - latency: 1.161454ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:34:16Z"
    - latency: 1.714973ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:34:16Z"
    - latency: 795.946µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:33:16Z"
    - latency: 1.770879ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:33:16Z"
    - latency: 839.988µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:32:16Z"
    - latency: 1.815789ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:32:16Z"
kind: List
metadata:
  resourceVersion: ""