helm VS speedtest

Applying Kubernetes manifests individually is problematic because files can get overlooked. Packaging your applications as Helm charts lets you version your manifests and easily repeat deployments into different environments. Helm tracks the state of each deployment as a "release" in your cluster.

helm

Explanation here: https://github.com/helm/helm/issues/12681#issuecomment-19593...

Looks like it's a bug in Helm, but actually isn't Helm's fault, the issue was introduced by Fedora Linux.

Helm (Get from here https://helm.sh/)

It’s also well understood that having a k8s cluster is not enough to make developers able to host their services - you need a devops team to work with them, using tools like delivery pipelines, Helm, kustomize, infra as code, service mesh, ingress, secrets management, key management - the list goes on! Developer Portals like Backstage, Port and Cortex have started to emerge to help manage some of this complexity.

Kubernetes orchestrates deployments and manages resources through yaml configuration files. While Kubernetes supports a wide array of resources and configurations, our aim in this tutorial is to maintain simplicity. For the sake of clarity and ease of understanding, we will use yaml configurations with hardcoded values. This method simplifies the learning process but isn’t ideal for production environments due to the need for manual updates with each new deployment. Although there are methods to streamline and automate this process, such as using Helm charts or bash scripts, we’ll not delve into those techniques to keep the tutorial manageable and avoid fatigue — you might be quite tired by that point!

Helm is a package manager that automates Kubernetes applications' creation, packaging, configuration, and deployment by combining your configuration files into a single reusable package. This eliminates the requirement to create the mentioned Kubernetes resources by ourselves since they have been implemented within the Helm chart. All we need to do is configure it as needed to match our requirements. From the public Helm chart repository, we can get the charts for common software packages like Consul, Jenkins SonarQube, etc. We can also create our own Helm charts for our custom applications so that we don’t need to repeat ourselves and simplify deployments.

We can search for charts https://helm.sh/ . Charts can be pulled(downloaded) and optionally unpacked(untar).

Generally I felt as if I was diving in the deepest of waters without the correct equipement and that was horrifying. Unfortunately to me, I had to dive even deeper before getting equiped with tools like ArgoCD, and k8slens. I had to start working with... HELM.

Within the architecture of Cyclops, a central component is the Helm engine. Helm is very popular within the Kubernetes community; chances are you have already run into it. The popularity of Helm plays to Cyclops's strength because of its straightforward integration.

I recently installed OpenWRT on a TP-Link TL-WDR4300, and put the router of my ISP in bridge mode. Now I noticed that the wireless speeds are significantly slower (40mbps vs 3mbps via librespeed.org), after using OpenWRT.

LebreSpeed

Try hosting a DIY speed test on a cloud server (like Google colab or the free oracle instances or whatever):

https://github.com/librespeed/speedtest

here's the top two results if you search for "open speed test nginx reverse proxy": https://github.com/librespeed/speedtest/wiki/Reverse-proxy-with-Nginx https://github.com/henrywhitaker3/Speedtest-Tracker/issues/924

Or https://librespeed.org/

Fast.com is giving me ~ 250Mbps https://librespeed.org is giving me ~ 112Mbps the one constant between all the tests seems to be the 52Mb upload

It should be DIA. They provide the internet connection to the company since 2 decades and it's a very small ISP, so it's very vague in terms of contract. Iperf was giving me very terrible results with TCP, UDP was giving me a couple of Gbit/s throughput, definitely a wrong result. We are using this self hosted speedtest. All my results above are based on this software: https://github.com/librespeed/speedtest

Put a copy of Librespeed on a web server that's accessible through the VPN and told them to use that. For (our) convenience, it's logged into a database that's correlated with the VPN login/logout times so the users don't even need to log in to use it, but we still know whose test result it is.