Earlier quoted context omitted.
Highly recommend trying Jsonnet (via https://github.com/bitnami/kubecfg and https://github.com/bitnami-labs/kube-libsonnet ) as an alternative. It makes writing Kubernetes manifests much more expressive and integrates better with Git/VCS based workflows. Another language like Dhall or CUE might also work, but I'm not aware of a kubecfg equivalent for them. Jsonnet in general is a pretty damn good configuration langua…
Funny, I thought jsonnet was an even worse experience than templating yaml
How we use HashiCorp Nomad
71–80 of 166 posts
Re: How we use HashiCorp Nomad
#72Earlier quoted context omitted.
Ive found the whole k14s eco system is pretty great to (ytt + kbld + kapp).
ytt is even more templating-yaml-with-yaml, so it all ends up being a bargain bin Helm. There's no reason to do this over just serializing plain structures into YAML/JSON/...
Also you can actually write pure code libraries in starlark (basically a subset of Python)
Re: How we use HashiCorp Nomad
#73Earlier quoted context omitted.
> How are they making a profit They aren't. In Q1 they made a loss of $33M on $91M in revenue.
Oh wow. In fact it seems they have been loosing more and more money over the years. https://finance.yahoo.com/quote/NET/financials/ What are they counting on happening here? Obviously free customers won't switch to paid plans.
Re: How we use HashiCorp Nomad
#74Earlier quoted context omitted.
Helm, however, is objectively terrible with its yaml-based templating language and zero practical modularity.
Sometimes I even wish they could embed a JavaScript interpreter... After all, YAML is almost equivalent to JSON, which the perfect templating language for JSON is -- JavaScript tbh. Or people have to keep inventing half baked things.
Re: How we use HashiCorp Nomad
#75Earlier quoted context omitted.
> How are they making a profit They aren't. In Q1 they made a loss of $33M on $91M in revenue.
Oh wow. In fact it seems they have been loosing more and more money over the years. https://finance.yahoo.com/quote/NET/financials/ What are they counting on happening here? Obviously free customers won't switch to paid plans.
Re: How we use HashiCorp Nomad
#76Earlier quoted context omitted.
That's a fair point, I guess it depends on your use case. The risk, however, is that the powers that be at HashiCorp one day decide to abandon Nomad once they realize it will never be a profit centre for them.
Nomad is open source (or, at least, a significant subset of it is). Anyone is able to continue to improve it, even if Hashicorp is no longer paying people to work on it.
Re: How we use HashiCorp Nomad
#77Earlier quoted context omitted.
Any chance you plan to integrate with Google's Config Connector? It's very similar to crossplane (but gcp specific). https://cloud.google.com/config-connector/docs/overview
I think that'd be a bit challenging because Config Connector is highly opinionated, for example, Kubernetes Namespace corresponds to GCP project. Though it might be enabled to be used as part of a Composition when we support namespaced CRs to be used as composition member.
Re: How we use HashiCorp Nomad
#78I'm surprised Hashicorp hasn't repositioned this product. Terraform was a huge breath of fresh air after Cloudformation. If you ask me, deploying apps via k8s is even better. Everyone wants a free lunch and for me, momentum + cloud vendor support + ultimately the Nomad Enterprise features that come free with K8s made the choice easy.
Re: How we use HashiCorp Nomad
#79"... here is the CPU usage over a day in one of our data centers where each time series represents one machine and the different colors represent different generations of hardware. Unimog keeps all machines processing traffic and at roughly the same CPU utilization." Still a mystery to me why "balancing" has SO MUCH mindshare. This is almost certainly not the optimal strategy for user experience. It is going to be mu…
I'm an engineer at Cloudflare, and I work on Unimog (the system in question). You are right that even balancing of utilization across servers with different hardware is not necessarily the optimal strategy. But keeping faster machines busy while slower machines are idle would not be better. This is because the time to service a request is only partly determined by the time it takes while being processed on a CPU some…
I'm sure your system has its benefits, I just get triggered by "load balancing" since it is so pervasive while also being a highly misleading and defective metaphor.