The information that writing can convey is not limited to an equation where the words used exist on one side and the meaning of the sentence on the other.
I hate to explain something someone else wrote, but the messy, tangential writing is mirroring the uncertainty that the author calls out in the dictionary definitions that they love. Their intent is to convey the joy that these words have for them when seen through the lens of Webster’s 1913. Joy is not constrained to declarative statements marching in lock step to the beat of logical coherence. To remove the “over wordiness” and “needless punctuation” is to lose the human aspect of the post.
Sometimes conveying information is a secondary or tertiary purpose to a piece of prose.
Also, not everyone is Raymond Carver. Some people are Henry James.
Helm is great right up until you run into a chart that doesn’t support what you need, i.e. if you want to run on tainted nodes, it needs to support tolerations. Want to add a sidecar to a pod? No.
It also lies about the actual status of the installation. A deployment that applies successfully but has issues with the new pods coming up can still show successful.
The larger charts are a nightmare which isn’t helm’s fault but it doesn’t make things appreciably easier either.
Kustomize has a lot of warts too. If the type definition in k8s source doesn’t have a merge key defined, it’s going to overwrite the entire section of the resource. You can use JsonPatches to get around that problem but that is super gross too.
The entire ecosystem is trying to solve the same problem and no one has come up with the definitive way of doing it (because it’s a HARD problem) It seems like Helm templating and then passing to kustomize to add in the one-off changes is the direction a lot of people are heading but it’s more of a least-bad solution than a good one.
I will say, if you’re using helm templates for your own stuff, you very likely going to be happy with it.
Yes, sarcasm but, much like jumping off bridges recreationally, naming programming things after existing words is an old practice. Lisp is 60 years old. Complaining about Celery and Centrifuge seems as disingenuous as sarcasm. We can agree on Go though. Some words are simply too common.
https://www.npr.org/2011/10/25/141672992/native-foster-care-...
https://theintercept.com/2019/06/17/indian-child-welfare-act...