Helm takes beautiful simple yaml config and obfuscates it. I'm convinced it was created by people who can't let go of the puppet/chef mentality. Kustomize won this battle, it's built into kubectl and keeps your yaml clean and elegant. Helm is dying, but it needs to die faster.
K8s took a few months to learn well enough to migrate my companies production services, and most of that was Istio. K8s simplifies things and makes life easier. It's just different from traditional Sysadmin methods. Drupal's Organic Groups by itself is way more complex than K8s. I've played guitar for 35 years and really am not very good. Maybe you should pick up a hobby that is actually difficult to "re-calibrate" your scale.
There are two different types of patches in Kustomize. It does take a bit to get used to it as it's different. jid (Interactive jq) makes the process a lot easier. It's actually pretty easy to make changes like this.
Helm is so bad it raises my blood pressure just hearing the name. Helm tries to apply the old way of doing things (like as you said Puppet) and makes it worse than ever. K8s yaml config is simple and elegant, don't try hiding it under templates. Kustomize is the proper way of working with K8s yaml. Helm fights against it.
I previously managed my companies Kubernetes clusters using Kops on AWS. My company switched to Google, so I had to move everything to GKE. I miss Kops, it gave me more control and made life easier. I don't want to use the old crappy deprecated DNS server, but with GKE that's what you get. I don't get to control what goes on the masters on my clusters because they're not mine anymore. Having GKE do the masters means more headaches and complexity because I no longer have control. I love K8s, but GKE does a pretty poor job implementing it. It boggles my mind that the main company behind K8s is so incompetent in implementing it.
I agree that ArgoCD is amazing. What's so beautiful is how well it integrates into K8s. Every element of ArgoCD is a CRD (custom resource definition). It's less of a piece of software (other than the interface) and more of an extension to K8s to provide Continuous Delivery. Saying ArgoCD does not require K8s is like saying you don't need Photoshop to run a Photoshop plugin.
I've used Puppet, Chef, and Ansible in production over the last decade. For me, Ansible replaced Puppet and Chef five or six years ago. For the last two years the only thing I have used Ansible for is to manage desktops and Android boxes AT HOME. Configuration Management systems like Ansible are fun and cool, but have been mostly obsoleted by the combo of Terraform and K8s. If you're on AWS, Kops can replace a lot of what Terraform does.
Kubernetes makes running services easier and more reliable. I've spent more time learning Istio that K8s itself. The learning curve of K8s is minimal compared to Drupal.
> Telling someone they shouldn’t use proprietary crap when they need it is not going to change anything. It just exposes to the world what a dick you are.
Nope, not dick, just someone with decades of wisdom. If you tell someone not to put Gorilla Glue in their hair does that make you a dick?
Thank you for writing this article. I'm a DevOps Engineer and spend most of my time with Terraform and Kubernetes. K8s yaml is simple clean config, and Helm turns it into an obfuscated monkey pile. If I need to use a Helm chart, I use helm template which outputs the yaml to a file. Typically I do this in a Makefile. Then I use Kustomize to modify it for my application. Kustomize has lowered my stress level from when I used Helm substantially. Helm might be fine if you don't know [and don't want to know] K8s and use it as a package manager, but the second you want to modify the config with something that isn't in the chart, like adding taints and tolerations, pod disruption budgets, pod priorities, etc, you have a nightmare. Helm literally turns something simple into something complicated. It's like trying to code with a welding helmet on.
Jenkins was great 10 years ago. Even 4 years ago it was OK. Now in K8s land ArgoCD is amazing. Please at least look at ArgoCD before thinking of using Jenkins.
This is exactly what I did. Snap's are basically docker gone wrong. Snaps are sandboxed, blocking access to NFS shares which I use extensively. Under Ubuntu, Chromium is usually broke (apt-get installs a deb that then installs a snap); You have to install either a debian .deb or use a PPA to make it work. I love that Ubuntu is directly including ZFS, but the distro has gotten so bad that I don't want to go near it anymore. Arch works, and works well.
I had a 3 year HostGator plan. I moved off it to Linode before the three years was up. After 3 years they billed my debit card again for another 3 years, and would not refund the money nor would my bank as it was debit charge, so basically they scammed me out of $300. Please use anyone but HostGator. Linode has always been great, and SSD Nodes is even cheaper with great service.
This was true three years ago. Plenty of 3D printers are now using ARM. The Monoprice MP Mini Delta has been out about two years now with a price of $175 US. Marlin 2.0 has support for ARM, I think it would be accurate to say "Almost every consumer 3D printer out there runs on top of Marlin", although there are a few alternatives like Smoothie.
Ubuntu/Snap simply does not work anymore. The sandboxing blocks all access to remote shares. I run a ZFS NFS file server for my data, and snap is blocking this. I'm in the process of switching all my Linux machines over to Arch. Also on one of my Ubuntu machines Chrome, which is a snap, seqfaults on startup. To me, Ubuntu is dead/dying other than in a docker container.
While people are commenting that $30 in materials is not very realistic, I find that's nothing compared to stating that 2 people can build this in 4 hours. I don't think it could be built in that amount of time if you used a large cnc router and had all the G-code already prepared. Looks to me like a week of work. I love the animations. Also the chain drive going around the bicycle rim is downright silly, you would have to weld gear teeth on the rim which would be extremely difficult.
It absolutely wasn't my choice to go to a Microsoft product. The engineering manager has some issues with the way Gitlab does PR merge diffs or something like that. I've been pretty impressed with Gitlab. Having a deb package that runs Chef is pretty unique. While Chef is my least favorite configuration manager, it's always worked perfect when doing apt upgrades on Gitlab and it is 100% behind the scenes.
At Linux World Atlanta 1999 there was a booth that had snap bracelets. I was looking at them in frustration and stated "I think you need a PhD to figure this out". The guy standing next to me responded "I have a PhD" and stormed off. The guy working the booth then enthusiastically proclaimed "Do you know who that was? That guy is a Demigod, that was Dennis Ritchie".
While this is awesome, it's trained on MUSDB18-HQ which as far as I can tell is proprietary. zenodo.org claims it is available, however I have filled out their "request access" page a half-dozen times. Does anyone know of a training data-set that's possible to obtain?
Here is the zenodo response:
Your access request has been rejected by the record owner.
The decision to reject the request is solely under the responsibility of the record owner. Hence, please note that Zenodo staff are not involved in this decision.
What worked for me is ditching the pillow to sleep when I'm on my back. I keep the pillow in the vicinity and use it if I switch to my side. People used to comment how bad my posture was, I don't get that anymore.
Kustomize already won this battle, it's now built into kubectl (-k flag instead of -f). Kustomize is a joy to use, as compared to helm makes me want to smash things.
Same here. I immediately ditched Solaris (hated it) for Linux when KQ Infotech ported ZFS over about a decade ago, but after a few years switched all my file servers to FreeBSD. ZFS > Linux. Did I mention I love Linux?
Helm is horrible, it makes simple elegant yaml files complex and makes the changes you actually need harder. Kustomize is the correct way to do things.