• 1 Post
  • 5 Comments
Joined 1Y ago
cake
Cake day: Jun 09, 2023

help-circle
rss

For development, I have a single image per project tagged “dev” running locally in WSL that I overwrite over and over again.

For real builds, I use pipelines on my Azure DevOps server to build the image on an agent using a remote buildkit container and push it in my internal repository. All 3 components hosted in the same kubernetes cluster.


Why does most (Kubeadm on-premise) Kubernetes tutorials advocates for bad practices or feels untested
Hello everyone, Recently I have returned to managing a kubernetes cluster in my homelab with Ansible on RHEL distros. Since I haven't touched to the installation stages since quite a long time I started to look for tutorials from the base installation to the cni configuration, MetalLB setup and metrics server installation. In every single tutorial, I have seen major issues that made me pull my hair: - First and the worst, most tutorials obviously have the firewall disabled or tells you to deactivate it. **Just**. **No**. I know deactivating it makes everything much easier and many issues disappear as soon as you run a `systemctl stop firewalld`. But if you want to teach correcty, you wouldn't recommend something that would make you fired on the spot. - CNI installations are straight forward but miss important information for troubleshooting. Stuff like putting flannel interfaces in the internal zone or adding some direct forwarding rules to firewalld can be necessary but again, everyone and their mothers have their firewall off so they never talk about it. - In MetalLB, the configMap used by the speakers is not created automatically by the official manifest. Missing it is impossible as the speaker straight up do not start and the logs are straightforward. Yet I have never seen one tutorial mention it. - Again in metalLB, if the controller is on a worker node, webhooks are not accessible and you cannot configure the load balancer. It's rare-ish and easy to fix but again, never seen any mention of that - While Flannel, MetalLB, Weave, ... clearly state which ports you need to open for their solutions, tutorials never do (firewall? Someone?) - The metrics server has some ... Particularities (like the need to modify the startup arguments or the dnsPolicy). Those are easily found in the github issues due to how frequent they're but I can never seem to find a tutorial mentionning those extra configuration to do. - Various basic stuff like a worker node + a cni being needed for coreDNS and the master node to become ready. Or how to verify your deployment of ingress/cni/metalLB is working correctly. If you are familiar with Kubernetes, it's not too hard to find the solution to those but when most of your audience, it should be explicit to at least share a random nginx manifest to test if everything is good. This is mainly a rant because it is crazy to see that a tutorial that is supposed to explain the documentation but faster is utterly useless because of course, you won't get any forwarding issues between interfaces if your device is an open bar. And that most of them are like this. So to everyone who also tried to follow tutorials for the set up of their clusterw what was your experience with them? Were they also useless or did you find a gem that didn't simply copy pasted the documentation and took screenshots of an working cluster setup without trying their guide?
fedilink



How is that a rip off? You pay 20€ once and get the ability to sideload any UWP app and develop for the console.

Compare it to both Nintendo and Sony where:

  • You have to pay multiple times the price of the console for the dev kit
  • You don’t own said dev kit
  • Their SDKs are not publicly accessible
  • You have to sign multiple NDAs on top of all those issues
  • Assuming you have no problem with all this, you can be rejected as a developer for any reason

Considering how locked consoles were and still are (Except for the PS3 “other OS”) period. Being able to get a decent current gen console, that doubles as an emulator, with development capabilities for an additional 20 euros is a gift, not a rip-off.


It’s more that UBI is just not financially possible for any country.

I live in a country with the highest tax rate on the continent and with just 20% of our population as pensioners, the situation is just getting worse and worse even though 49% of the population has a tax rate between 25 and 50% (+13% from welfare taxes). Just with this small percentage, we are spending 20% of our budget in pensions. More than any other area by at least 5% of our national budget.

If the state now had to pay an UBI to 69% of our population on top of this, the very minimum to pay off the UBI without going bankrupt would be to sell off the free healthcare and public transport in their entirety. And I’m assuming a small UBI of 500€/month (Not even enough to rent a 1 room appartement with utilities in some areas).

UBI would destroy any country’s budget for what? Landlord increasing rent to match the UBI, corporations increasing prices to match the inflation and people wasting that money when it could have been put to use to increase renewable energy production, improve education, …

UBI is only a good idea in paper and you only need to look at the public expenses of most European countries + have a basic understanding of capitalist greed to see it.